AWS prescriptive-guidance documentation change
Summary
Updated documentation with minor editorial changes, including correcting service names (e.g., 'S3 bucket' to 'Amazon S3 bucket'), fixing punctuation, and adding a sentence about customer challenges and best practices. Also updated section headers for clarity.
Security assessment
The changes are purely editorial and grammatical. They focus on improving clarity and consistency in describing testing challenges for serverless applications. There is no mention of vulnerabilities, security incidents, patches, or new security features. The content discusses general testing limitations (like IAM permissions) but does not introduce or highlight new security information.
Diff
diff --git a/prescriptive-guidance/latest/serverless-application-testing/challenges.md b/prescriptive-guidance/latest/serverless-application-testing/challenges.md index ab47ab442..e2fd55cc4 100644 --- a//prescriptive-guidance/latest/serverless-application-testing/challenges.md +++ b//prescriptive-guidance/latest/serverless-application-testing/challenges.md @@ -5 +5 @@ -Example: A Lambda function that creates an S3 bucketExample: A Lambda function that processes messages from Amazon SQS queue +Example: A Lambda function that creates an Amazon S3 bucketExample: A Lambda function that processes messages from Amazon SQS @@ -9 +9 @@ Example: A Lambda function that creates an S3 bucketExample: A Lambda function t -When you use emulators and mocked calls to test your serverless application on your local desktop, you might experience testing inconsistencies as your code progresses from environment to environment in your CI/CD pipeline. The unit tests you create on your desktop to validate your application’s business logic might not include or accurately represent critical aspects of cloud services. Complete tests can’t be performed locally in isolation. They require verifying the permissions and configurations among multiple services. +When you use emulators and mocked calls to test your serverless application on your local desktop, you might experience testing inconsistencies as your code progresses from environment to environment in your CI/CD pipeline. The unit tests you create on your desktop to validate your application's business logic might not include or accurately represent critical aspects of cloud services. Complete tests can't be performed locally in isolation. They require verifying the permissions and configurations among multiple services. @@ -11 +11 @@ When you use emulators and mocked calls to test your serverless application on y -The following sections outline the challenges you might experience when implementing a cloud testing strategy. +The following sections outline the challenges you might experience when implementing a cloud testing strategy. The following sections outline the challenges customers experience when trying to implement a cloud testing strategy, and our guidance on best practices to achieve effective test coverage. @@ -13 +13 @@ The following sections outline the challenges you might experience when implemen -## Example: A Lambda function that creates an S3 bucket +## Example: A Lambda function that creates an Amazon S3 bucket @@ -15 +15 @@ The following sections outline the challenges you might experience when implemen -If a Lambda function’s logic depends on creating an S3 bucket, a complete test should confirm that Amazon S3 was successfully called and the bucket was successfully created. In a mock testing setup, you might mock a success response and potentially add a test case to handle a failure response. In an emulation testing scenario, the **CreateBucket** API might be called, but the identity that makes the call will not originate from the Lambda service assuming a role, and a placeholder authentication will be used instead—this is often your more permissive role or user identity. +If a Lambda function's logic depends on creating an Amazon S3 bucket, a complete test should confirm that Amazon S3 was successfully called and the bucket was successfully created. In a mock testing setup, you might mock a success response and potentially add a test case to handle a failure response. In an emulation testing scenario, the `CreateBucket` API might be called, but the identity that makes the call will not originate from the Lambda service assuming a role, and a placeholder authentication will be used instead―this is often your more permissive role or user identity. @@ -17 +17 @@ If a Lambda function’s logic depends on creating an S3 bucket, a complete test -The mock and emulation setups discussed previously will most likely test _what the Lambda function will do_ if it successfully (or unsuccessfully) calls Amazon S3. However, those tests will fail to capture _whether the Lambda function is capable_ of successfully creating the bucket, given the function’s configuration. This configuration is likely represented by infrastructure as code (IaC) for products and services such as AWS CloudFormation, AWS SAM, or HashiCorp Terraform. One possible issue is that the role that is assigned to the function doesn’t have an attached policy that allows for the `s3:CreateBucket` action, and the function will therefore always fail when it is deployed to a cloud environment. +The mock and emulation setups discussed previously will most likely test _what the Lambda function will do_ if it successfully (or unsuccessfully) calls Amazon S3. However, those tests will fail to capture _whether the Lambda function is capable_ of successfully creating the bucket, given the function's configuration. This configuration is likely represented by infrastructure as code (IaC) for products and services such as AWS CloudFormation, AWS SAM, or HashiCorp Terraform. One possible issue is that the role that is assigned to the function doesn't have an attached policy that allows for the `s3:CreateBucket` action, and the function will therefore always fail when it is deployed to a cloud environment. @@ -19 +19 @@ The mock and emulation setups discussed previously will most likely test _what t -## Example: A Lambda function that processes messages from Amazon SQS queue +## Example: A Lambda function that processes messages from Amazon SQS @@ -21 +21 @@ The mock and emulation setups discussed previously will most likely test _what t -If an Amazon SQS queue is the source of a Lambda function, a complete test should verify that the Lambda function is successfully invoked when a message is put in a queue. Emulation testing and mock testing are generally set up to run the Lambda function code directly, and to simulate the Amazon SQS integration by passing a JSON event payload (or a deserialized object) as the function handler’s input. +If an Amazon Simple Queue Service (Amazon SQS) queue is the source of a Lambda function, a complete test should verify that the Lambda function is successfully invoked when a message is put in a queue. Emulation testing and mock testing are generally set up to run the Lambda function code directly, and to simulate the Amazon SQS integration by passing a JSON event payload (or a deserialized object) as the function handler's input. @@ -23 +23 @@ If an Amazon SQS queue is the source of a Lambda function, a complete test shoul -Local testing that simulates the Amazon SQS integration will test _what the Lambda function will do_ when it’s called by Amazon SQS with a given payload, but it won’t ensure that _Amazon SQS will successfully invoke the Lambda function_ when it is deployed to a cloud environment. +Local testing that simulates the Amazon SQS integration will test _what the Lambda function will do_ when it's called by Amazon SQS with a given payload, but it won't ensure that _Amazon SQS will successfully invoke the Lambda function_ when it is deployed to a cloud environment. @@ -29 +29 @@ Some examples of configuration problems you might encounter with Amazon SQS and - * The Lambda function’s execution role doesn’t allow reading messages from the queue (through `sqs:ReceiveMessage`, `sqs:DeleteMessage`, or `sqs:GetQueueAttributes`). + * The Lambda function's execution role doesn't allow reading messages from the queue (through `sqs:ReceiveMessage`, `sqs:DeleteMessage`, or `sqs:GetQueueAttributes`). @@ -44 +44 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Testing techniques +Testing techniques for serverless applications @@ -46 +46 @@ Testing techniques -Best practices +Best practices for testing serverless applications