We recommend integrating and deploying changes using AWS and DevOps practices when configuring this Guidance. For example, AWS CodeBuild  and AWS CodeDeploy can be used to manage versions and deployment strategies. We also recommend using an AWS Cloud Development Kit (AWS CDK) which helps manage deployment through code in a controlled environment across accounts. This infrastructure as code approach helps with versioning, testing, and deployment automation. By leveraging AWS, DevOps tools, and CDK , you can deploy changes easily, rollback failed deployments, and provision resources reliably and repeatably across environments. This enables a robust continuous integration and continuous delivery (CI/CD) pipeline for safe, efficient updates to the architecture.

Several AWS services were used in this architecture to make sure communication and data are secure. For core communication between services, we used Amazon Cognito and AWS Identity and Access Management (IAM). This allows you to authenticate and authorize access for both people and machines. All service-to-service communication is authenticated with  Amazon Cognito and authorized using IAM roles. For storing data, we used DynamoDB , Neptune , Amazon S3 , and Lake Formation . These services encrypt data both when stored and when moved between services. By building in security with AWS from the start, you can ensure sensitive information is protected.

This Guidance follows AWS best practices for a serverless architecture. The core processing service is Lambda , provisioned using concurrency limits. To enable decoupled services, Amazon SQS and Amazon SNS are used. For observability, AWS metrics and logging services like Amazon CloudWatch , AWS X-Ray , and AWS CloudTrail are used. All backend logs and metrics from transactions and services are streamed to CloudWatch . By adhering to AWS serverless architectures, such as using Lambda for processing, and implementing AWS observability services, you can build a robust and scalable serverless system that is cost-effective, high-performing, and secure.

The AWS serverless services used throughout this Guidance scale continuously and usage is metered in milliseconds, optimizing costs. Since AWS manages the services, overall resource consumption is reduced too. The serverless architecture enables automatic scaling, resilience, cost optimization, and high performance. The on-demand nature of serverless computing allows you to only pay for exactly what you need while AWS handles provisioning and managing resources behind the scenes. This is ideal for workloads that are event-driven, inconsistent, or unpredictable.

This Guidance uses serverless services, the building blocks of AWS. Since AWS manages the infrastructure behind the services in this architecture, you avoid having to setup and maintain servers yourselves. This saves you money on operations and administration. You only pay for what you use. There are no charges when the services are idle. Using these ready-to-go components, optimized for fast processing and sharing, means your costs stay low and your productivity stays high.