The American robin is my worst enemy come spring time in Seattle!

📓 Read more about it: aws.amazon.com/blogs/aws/en...

🎯 Dev productivity boost:
✅Use new AppSyncJS batch utils to bulk-write to DynamoDB
✅Powertools for Lambda now ships AppSync Events helpers (TS, Python, .NET)
💡Cut boilerplate, ship in minutes—not days.

✨ Key capabilities:
✅ Direct Lambda integration with zero AppSync code
✅ Request/response mode for filtering & validation
✅ Event mode for async workflows

🔥 You can now access data sources directly from onPublish & onSubscribe handlers. Configure a direct integration to call a Lambda function. No handler code required. Use your function to process your events before broadcast or invoke it in event mode to kick off an async task.

Agreed. There’s a lot going on. A bit too much for one book.

Hey Ian, AppSync PM here 👋🏾. Sliding in here to say thanks for the feedback. I'm interested in learning more about your configuration. What does your typical ephemeral set up look like, and how many AppSync resources are you deploying? Feel free to dm. cheers.

Yeah. Fail on our part. 😩

Heyyyyy

I’ll also be talking about AWS AppSync as an AI gateway for generative AI backends powered by Amazon Bedrock. Super excited to be joined by Salman Moghal to cover real-world implementations of AI gateway patterns and Cal Rueb from Anthropic to dig into challenges of building on LLMs.

This simplifies API governance, improves security, and enables more flexible and scalable architectures for multi-account environments. Customers can optionally enable CloudTrail to capture API activities related to AWS AppSync GraphQL APIs as events for additional security and visibility. 7/7

Before today, customers had to set up additional networking infrastructure to share their private GraphQL APIs between their organization accounts. Now, customers can centralize their GraphQL API management in a dedicated account and share access to these APIs with other accounts. 6/7

Next, let's talk about resource sharing of AppSync GraphQL APIs. Our recent launch of data plane logging to AWS CloudTrail might have been a hint this was coming. A lot of customers are using AppSync's private API feature today to enable private workloads inside their VPCs. 5/7

With this new release we simplify config, monitoring and observability by introducing an Amazon Bedrock runtime data source that you can use to call the `invokeModel` and `converse` APIs. You can easily call these APIs from your JavaScript resolvers. 4/7

In some cases, customers just want to make short synchronous model invocations directly. Think about getting an embedding or summarization from a Amazon Titan model or generating an object using a Claude 3.5 Haiku model. 3/7

Customers use AppSync today to for generative AI workloads powered by Bedrock. Often, developers use an async pattern that calls a Lambda function to invoke a model, and then returns results to clients via a subscription. Great for long-running invocations and getting progressive updates. 2/7