AWS lambda documentation change
Summary
Updated section headers, added multi-region deployment note, and made minor wording improvements
Security assessment
Changes focus on architectural guidance and documentation clarity. The added note about multi-region deployments improves disaster recovery guidance but doesn't address specific security vulnerabilities. Existing security recommendations about secrets management (Parameter Store/Secrets Manager) remain unchanged in substance.
Diff
diff --git a/lambda/latest/dg/concepts-application-design.md b/lambda/latest/dg/concepts-application-design.md index 2f3e4aacb..6a66d8b55 100644 --- a//lambda/latest/dg/concepts-application-design.md +++ b//lambda/latest/dg/concepts-application-design.md @@ -7 +7 @@ Use services instead of custom codeUnderstand Lambda abstraction levelsImplement -# Lambda-based application design principles +# Designing a Lambda applications @@ -61,0 +62,4 @@ Streaming data and analytics | Amazon Data Firehose +###### Note + +Many serverless services provide replication and support for multiple Regions, including DynamoDB and Amazon S3. Lambda functions can be deployed in multiple Regions as part of a deployment pipeline, and API Gateway can be configured to support this configuration. See this [ example architecture](https://d1.awsstatic.com/architecture-diagrams/ArchitectureDiagrams/serverless-architecture-for-global-applications-ra.pdf?did=wp_card&trk=wp_card) that shows how this can be achieved. + @@ -81 +85 @@ Similarly, Lambda's integrations with other services are managed by AWS, with on -This abstraction allows you to focus on the integration aspects of your application, the flow of data, and the business logic where your workload provides value to your end users. Allowing the services to manage the underlying mechanics helps you develop applications more quickly with less custom code to maintain. +This abstraction helps you focus on the integration aspects of your application, the flow of data, and the business logic where your workload provides value to your end users. Allowing the services to manage the underlying mechanics helps you develop applications more quickly with less custom code to maintain. @@ -93 +97 @@ Most architectures should prefer many, shorter functions over fewer, larger ones -Any global-scope constants that change infrequently should be implemented as environment variables to allow updates without deployments. Any secrets or sensitive information should be stored in [AWS Systems Manager Parameter Store](https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-parameter-store.html) or [AWS Secrets Manager](https://aws.amazon.com/secrets-manager/) and loaded by the function. Since these resources are account-specific, this allows you to create build pipelines across multiple accounts. The pipelines load the appropriate secrets per environment, without exposing these to developers or requiring any code changes. +Any global-scope constants that change infrequently should be implemented as environment variables to allow updates without deployments. Any secrets or sensitive information should be stored in [AWS Systems Manager Parameter Store](https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-parameter-store.html) or [AWS Secrets Manager](https://aws.amazon.com/secrets-manager/) and loaded by the function. Since these resources are account-specific, you can create build pipelines across multiple accounts. The pipelines load the appropriate secrets per environment, without exposing these to developers or requiring any code changes. @@ -113 +117 @@ Workflows that involve branching logic, different types of failure models, and r -With [AWS Step Functions](https://aws.amazon.com/step-functions/), you use state machines to manage orchestration. This extracts the error handling, routing, and branching logic from your code, replacing it with state machines declared using JSON. Apart from making workflows more robust and observable, it allows you to add versioning to workflows and make the state machine a codified resource that you can add to a code repository. +With [AWS Step Functions](https://aws.amazon.com/step-functions/), you use state machines to manage orchestration. This extracts the error handling, routing, and branching logic from your code, replacing it with state machines declared using JSON. Apart from making workflows more robust and observable, you can also add versioning to workflows and make the state machine a codified resource that you can add to a code repository. @@ -145 +149 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Event-driven architectures +Creating event-driven architectures @@ -147 +151 @@ Event-driven architectures -Frequently asked questions +Create your first function