AWS Compute Blog

Tag: contributed

Request flow for idempotent Lambda function

Implementing idempotent AWS Lambda functions with Powertools for AWS Lambda (TypeScript)

This post is written by Alexander Schüren, Sr Specialist SA, Powertools. One of the design principles of AWS Lambda is to “develop for retries and failures”. If your function fails, the Lambda service will retry and invoke your function again with the same event payload. Therefore, when your function performs tasks such as processing orders […]

Python and Node.js Lambda Layer for Chaos Injection

Building resilient serverless applications using chaos engineering

This post is written by Suranjan Choudhury (Head of TME and ITeS SA) and Anil Sharma (Sr PSA, Migration)  Chaos engineering is the process of stressing an application in testing or production environments by creating disruptive events, such as outages, observing how the system responds, and implementing improvements. Chaos engineering helps you create the real-world […]

Solution architecture overview for sending messages

Integrating IBM MQ with Amazon SQS and Amazon SNS using Apache Camel

This post is written by Joaquin Rinaudo, Principal Security Consultant and Gezim Musliaj, DevOps Consultant. IBM MQ is a message-oriented middleware (MOM) product used by many enterprise organizations, including global banks, airlines, and healthcare and insurance companies. Customers often ask us for guidance on how they can integrate their existing on-premises MOM systems with new […]

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.