For one-off tasks, AWS Lambda really can be incredibly easy. You write a few lines of code, deploy it, and you have a function running in the cloud ready to respond to events, scale automatically, and that only costs you pennies. But as your application grows, so does some necessary complexity. When a few one-off functions become a full serverless backend architecture made up of interconnected services, you’ll need to pay careful attention to best practices to ensure that your application is easy to debug, maintain, and scale. That’s where AWS Powertools for Lambda fits in. It’s a suite of reusable utilities designed to simplify bringing best practices around things like logging, tracing, metrics, idempotency and more to your Lambda functions with minimal effort. This demo session will dive into some of the functionality provided by the AWS Powertools (TypeScript) core libraries, such as encapsulating best practices into reusable libraries for structured logging, metrics collection, idempotency, and more; leveraging Middy middleware to integrate common cross-cutting concerns, such as injecting Lambda context or automatically flushing metric; enabling local testing with LocalStack, allowing you to deploy and debug Lambda functions with structured logs, trace data, and embedded metrics; and providing modular examples that can be deployed to AWS or LocalStack with ease, enabling developers to explore libraries.
LocalStack Applications in Developer Hub provides sample templates to help LocalStack users adopt real-world scenarios to rapidly and conveniently create, configure, and deploy applications locally.
Getting started with Step-up-authentication demo
In this demo, we will setup a step-up authentication workflow for a higher level of security, deployed using Cloud Development Kit on LocalStack
Running your Spring Boot app on AWS for production is common, but testing there can be slow and costly. In this video, we’ll show you how to speed up development using LocalStack. By provisioning your infrastructure with Terraform, you can easily switch to local testing in just three steps: configure your dev environment variables, start LocalStack in Docker, and run your IaC files. Get faster feedback and reduce costs by testing locally with LocalStack!
