AWS Compute Blog

James Beswick

Author: James Beswick

James Beswick leads the Serverless Developer Advocacy team at AWS. He works with AWS's developer customers to understand how serverless technologies can drastically change the way they think about building and running applications at massive scale with minimal administration overhead. Visit https://serverlessland.com for more serverless content.

Go running on provided.al2

Migrating AWS Lambda functions from the Go1.x runtime to the custom runtime on Amazon Linux 2

Lambda is deprecating the go1.x runtime in line with Amazon Linux 1 end-of-life, scheduled for December 31, 2023. Customers using Go with Lambda should migrate their functions to the provided.al2 runtime. Benefits include support for AWS Graviton2 processors with better price-performance, and a streamlined invoke path with faster performance.

Three TPS examples

Understanding AWS Lambda’s invoke throttling limits

This blog explains three key throttle limits applied on Lambda invokes: the concurrency limit, TPS limit and burst limit. It outlines the relationship between these limits and how each one protects the system and your workload from noisy neighbors. Equipped with this knowledge you can better interpret any 429 throttling exceptions you may receive while scaling your applications on Lambda.

Architecture

Implementing custom domain names for Amazon API Gateway private endpoints using a reverse proxy

This blog post demonstrates a solution that allows customers to utilize their private endpoints securely with API Gateway across AWS accounts and within a VPC network by using a reverse proxy with a custom domain name. The solution offers a simplified approach to manage the mapping between private endpoints with API Gateway and custom domain names, ensuring seamless connectivity and security.

Sample architecture

Automating stopping and starting Amazon MWAA environments to reduce cost

This was written by Uma Ramadoss, Specialist Integration Services, and Chandan Rupakheti, Solutions Architect. This blog post shows how you can save cost by automating the stopping and starting of an Amazon Managed Workflows for Apache Airflow (Amazon MWAA) environment. It describes how you can retain the data stored in a metadata database and presents […]

Final architecture

Extending a serverless, event-driven architecture to existing container workloads

The blog explains a way to integrate existing container workload running on AWS Fargate with a new event-driven architecture. You use EventBridge to decouple different services from each other that are built using different compute technologies, languages, and frameworks. Using AWS CDK, you gain the modularity of building services decoupled from each other.