AWS Compute Blog

Tag: contributed

Developing a serverless Slack app using AWS Step Functions and AWS Lambda

This blog was written by Sam Wilson, Cloud Application Architect and John Lopez, Cloud Application Architect. Slack, as an enterprise collaboration and communication service, presents opportunities for builders to improve efficiency through implementing custom-written Slack Applications (apps). One such opportunity is to expose existing AWS resources to your organization without your employees needing AWS Management […]

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 […]

Monitor Amazon SNS-based applications end-to-end with AWS X-Ray active tracing

This post is written by Daniel Lorch, Senior Consultant and David Mbonu, Senior Solutions Architect. Amazon Simple Notification Service (Amazon SNS), a messaging service that provides high-throughput, push-based, many-to-many messaging between distributed systems, microservices, and event-driven serverless applications, now supports active tracing with AWS X-Ray. With AWS X-Ray active tracing enabled for SNS, you can […]

Debugging SnapStart-enabled Lambda functions made easy with AWS X-Ray

This post is written by Rahul Popat (Senior Solutions Architect) and Aneel Murari (Senior Solutions Architect)  Today, AWS X-Ray is announcing support for SnapStart-enabled AWS Lambda functions. Lambda SnapStart is a performance optimization that significantly improves the cold startup times for your functions. Announced at AWS re:Invent 2022, this feature delivers up to 10 times faster function startup times for […]

Implementing cross-account CI/CD with AWS SAM for container-based Lambda functions

Containerized applications often have several distinct environments and accounts, such as dev, test, and prod. An application has to go through a process of deployment and testing in these environments. One common pattern for deploying containerized applications is to have a central AWS create a single container image, and carry out deployment across other AWS accounts. To achieve automated deployment of the application across different environments, customers use CI/CD pipelines with familiar container tooling. This blog post explores how to use AWS Serverless Application Model (AWS SAM) Pipelines to create a CI/CD deployment pipeline and deploy a container-based Lambda function across multiple accounts.

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.

Implementing error handling for AWS Lambda asynchronous invocations

This blog is written by Poornima Chand, Senior Solutions Architect, Strategic Accounts and Giedrius Praspaliauskas, Senior Solutions Architect, Serverless. AWS Lambda functions allow both synchronous and asynchronous invocations, which both have different function behaviors and error handling: When you invoke a function synchronously, Lambda returns any unhandled errors in the function code back to the […]