AWS Security ChangesHomeSearch

AWS prescriptive-guidance documentation change

Service: prescriptive-guidance · 2025-05-01 · Documentation low

File: prescriptive-guidance/latest/patterns/schedule-jobs-for-amazon-rds-for-postgresql-and-aurora-postgresql-by-using-lambda-and-secrets-manager.md

Summary

Updated Lambda documentation references to use short form 'Lambda' instead of 'AWS Lambda' and made minor text adjustments

Security assessment

Changes focus on terminology consistency (e.g., 'AWS Lambda' → 'Lambda') and minor text formatting. While the document discusses security-related features like Secrets Manager credential management, these edits do not introduce new security content or address specific vulnerabilities. The security implications of using Secrets Manager were already present in the original text.

Diff

diff --git a/prescriptive-guidance/latest/patterns/schedule-jobs-for-amazon-rds-for-postgresql-and-aurora-postgresql-by-using-lambda-and-secrets-manager.md b/prescriptive-guidance/latest/patterns/schedule-jobs-for-amazon-rds-for-postgresql-and-aurora-postgresql-by-using-lambda-and-secrets-manager.md
index 8388d84f9..dc5071751 100644
--- a//prescriptive-guidance/latest/patterns/schedule-jobs-for-amazon-rds-for-postgresql-and-aurora-postgresql-by-using-lambda-and-secrets-manager.md
+++ b//prescriptive-guidance/latest/patterns/schedule-jobs-for-amazon-rds-for-postgresql-and-aurora-postgresql-by-using-lambda-and-secrets-manager.md
@@ -55,2 +54,0 @@ This stack has a Lambda function that uses the credentials stored in Secrets Man
-  * [AWS Lambda](https://docs.aws.amazon.com/lambda/latest/dg/welcome.html) is a compute service that lets you run code without provisioning or managing servers. AWS Lambda runs your code only when needed and scales automatically, from a few requests per day to thousands per second. You pay only for the compute time you consume; there is no charge when your code is not running. With AWS Lambda, you can run code for virtually any type of application or backend service with zero administration. AWS Lambda runs your code on a high-availability compute infrastructure and manages all the compute resources, including server and operating system maintenance, capacity provisioning and automatic scaling, code monitoring, and logging. All you need to do is provide your code in one of the [languages that AWS Lambda supports](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html).
-
@@ -59 +57,3 @@ This stack has a Lambda function that uses the credentials stored in Secrets Man
-  * [AWS Secrets Manager](https://docs.aws.amazon.com/secretsmanager/latest/userguide/intro.html) helps you protect secrets for accessing your applications, services, and IT resources. You can easily rotate, manage, and retrieve database credentials, API keys, and other secrets throughout their lifecycle. Users and applications retrieve secrets by calling Secrets Manager APIs, which eliminates the need to hard-code sensitive information in plain text. Secrets Manager offers secret rotation with built-in integration for Amazon RDS, Amazon Redshift, and Amazon DocumentDB. The service is extensible to other types of secrets, including API keys and OAuth tokens. Secrets Manager enables you to control access to secrets using fine-grained permissions and to audit secret rotation centrally for resources in the AWS Cloud, third-party services, and on-premises.
+  * [AWS Lambda](https://docs.aws.amazon.com/lambda/latest/dg/welcome.html) is a compute service that lets you run code without provisioning or managing servers. Lambda runs your code only when needed and scales automatically, from a few requests per day to thousands per second. You pay only for the compute time you consume; there is no charge when your code is not running. With Lambda, you can run code for virtually any type of application or backend service with zero administration. Lambda runs your code on a high-availability compute infrastructure and manages all the compute resources, including server and operating system maintenance, capacity provisioning and automatic scaling, code monitoring, and logging. All you need to do is provide your code in one of the [languages that Lambda supports](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html).
+
+  * [AWS Secrets Manager](https://docs.aws.amazon.com/secretsmanager/latest/userguide/intro.html) helps you protect secrets for accessing your applications, services, and IT resources. You can easily rotate, manage, and retrieve database credentials, API keys, and other secrets throughout their lifecycle. Users and applications retrieve secrets by calling Secrets Manager APIs, which eliminates the need to hard-code sensitive information in plain text. Secrets Manager offers secret rotation with built-in integration for Amazon RDS, Amazon Redshift, and Amazon DocumentDB. The service is extensible to other types of secrets, including API keys and OAuth tokens. Secrets Manager enables you to control access to secrets using fine-grained permissions and to audit secret rotation centrally for resources in the AWS Cloud, third-party services, and on premises.
@@ -73 +73 @@ Task| Description| Skills required
-Choose a programming language supported by AWS Lambda.| For a list of supported languages, see [Lambda runtimes](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html) (Lambda documentation).| Developer  
+Choose a programming language supported by Lambda.| For a list of supported languages, see [Lambda runtimes](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html) (Lambda documentation).| Developer  
@@ -75 +75 @@ Write the logic to fetch the database credentials from Secrets Manager.| For sam
-Write the logic to perform the scheduled database activity.| Migrate your existing code for the scheduling job that you're using on premises to the AWS Lambda function. For more information, see [Deploying Lambda functions](https://docs.aws.amazon.com/lambda/latest/dg/lambda-deploy-functions.html) (Lambda documentation).| Developer  
+Write the logic to perform the scheduled database activity.| Migrate your existing code for the scheduling job that you're using on premises to the Lambda function. For more information, see [Deploying Lambda functions](https://docs.aws.amazon.com/lambda/latest/dg/lambda-deploy-functions.html) (Lambda documentation).| Developer  
@@ -80 +80 @@ Create the Lambda function deployment package.| This package contains the code a
-Create the Lambda function.| In the AWS Lambda console, choose **Create function** , enter a function name, choose the runtime environment, and then choose **Create function**.| DevOps  
+Create the Lambda function.| In the Lambda console, choose **Create function** , enter a function name, choose the runtime environment, and then choose **Create function**.| DevOps  
@@ -84 +84 @@ Set permissions for the Lambda function role to access Secrets Manager.| For ins
-Test the Lambda function.| Initiate the function manually to make sure it works as expected.| DevOps  
+Test the Lambda function.| Initiate the Lambda function manually to make sure it works as expected.| DevOps