AWS transfer documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' throughout the document, including section headers and console references. Mentioned stack templates now use BASE64-encoded passwords.
Security assessment
The changes are primarily branding/naming convention updates (removing redundant 'AWS' prefix from CloudFormation references). While the document mentions BASE64-encoded passwords in templates, this appears to be existing security documentation rather than a new addition. There's no evidence of addressing a specific security vulnerability or adding new security features.
Diff
diff --git a/transfer/latest/userguide/authentication-api-gateway.md b/transfer/latest/userguide/authentication-api-gateway.md index 4b0c8b288..96c278053 100644 --- a//transfer/latest/userguide/authentication-api-gateway.md +++ b//transfer/latest/userguide/authentication-api-gateway.md @@ -5 +5 @@ -Authenticating using an API Gateway methodImplementing your API Gateway methodDefault Lambda functionLambda function for use with AWS Secrets ManagerImprovements to the AWS CloudFormation templates +Authenticating using an API Gateway methodImplementing your API Gateway methodDefault Lambda functionLambda function for use with AWS Secrets ManagerImprovements to the CloudFormation templates @@ -51 +51 @@ Do not enable caching for your API Gateway method when using it as a custom iden - 1. Create an AWS CloudFormation stack. To do this: + 1. Create an CloudFormation stack. To do this: @@ -55 +55 @@ Do not enable caching for your API Gateway method when using it as a custom iden -The stack templates have been updated to use BASE64-encoded passwords: for details, see Improvements to the AWS CloudFormation templates. +The stack templates have been updated to use BASE64-encoded passwords: for details, see Improvements to the CloudFormation templates. @@ -57 +57 @@ The stack templates have been updated to use BASE64-encoded passwords: for detai - 1. Open the AWS CloudFormation console at [https://console.aws.amazon.com/cloudformation](https://console.aws.amazon.com/cloudformation/). + 1. Open the CloudFormation console at [https://console.aws.amazon.com/cloudformation](https://console.aws.amazon.com/cloudformation/). @@ -59 +59 @@ The stack templates have been updated to use BASE64-encoded passwords: for detai - 2. Follow the instructions for deploying an AWS CloudFormation stack from an existing template in [Selecting a stack template](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-using-console-create-stack-template.html) in the _AWS CloudFormation User Guide_. + 2. Follow the instructions for deploying an CloudFormation stack from an existing template in [Selecting a stack template](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-using-console-create-stack-template.html) in the _AWS CloudFormation User Guide_. @@ -91 +91 @@ If you are using the custom identity provider option to enable password–based - 2. Choose the **Transfer Custom Identity Provider basic template API** that the AWS CloudFormation template generated. You might need to select your region to see your gateways. + 2. Choose the **Transfer Custom Identity Provider basic template API** that the CloudFormation template generated. You might need to select your region to see your gateways. @@ -119 +119 @@ Copy the **Invoke URL** address that appears at the top of the screen. You might - 3. For **Role** , choose the IAM role that was created by the AWS CloudFormation template. This role allows Transfer Family to invoke your API gateway method. + 3. For **Role** , choose the IAM role that was created by the CloudFormation template. This role allows Transfer Family to invoke your API gateway method. @@ -121 +121 @@ Copy the **Invoke URL** address that appears at the top of the screen. You might -The invocation role contains the AWS CloudFormation stack name that you selected for the stack that you created in step 1. It has the following format: ``CloudFormation-stack-name`-TransferIdentityProviderRole-`ABC123DEF456GHI``. +The invocation role contains the CloudFormation stack name that you selected for the stack that you created in step 1. It has the following format: ``CloudFormation-stack-name`-TransferIdentityProviderRole-`ABC123DEF456GHI``. @@ -266 +266 @@ The example functions are listed in [Example Lambda functions](./custom-lambda-i -To use AWS Secrets Manager as your identity provider, you can work with the Lambda function in the sample AWS CloudFormation template. The Lambda function queries the Secrets Manager service with your credentials and, if successful, returns a designated secret. For more information about Secrets Manager, see the [AWS Secrets Manager User Guide](https://docs.aws.amazon.com/secretsmanager/latest/userguide/intro.html). +To use AWS Secrets Manager as your identity provider, you can work with the Lambda function in the sample CloudFormation template. The Lambda function queries the Secrets Manager service with your credentials and, if successful, returns a designated secret. For more information about Secrets Manager, see the [AWS Secrets Manager User Guide](https://docs.aws.amazon.com/secretsmanager/latest/userguide/intro.html). @@ -268 +268 @@ To use AWS Secrets Manager as your identity provider, you can work with the Lamb -To download a sample AWS CloudFormation template that uses this Lambda function, go to the [Amazon S3 bucket provided by AWS Transfer Family](https://s3.amazonaws.com/aws-transfer-resources/custom-idp-templates/aws-transfer-custom-idp-secrets-manager-apig.template.yml). +To download a sample CloudFormation template that uses this Lambda function, go to the [Amazon S3 bucket provided by AWS Transfer Family](https://s3.amazonaws.com/aws-transfer-resources/custom-idp-templates/aws-transfer-custom-idp-secrets-manager-apig.template.yml). @@ -270 +270 @@ To download a sample AWS CloudFormation template that uses this Lambda function, -## Improvements to the AWS CloudFormation templates +## Improvements to the CloudFormation templates @@ -300 +300 @@ The changes in the template that enable this capability are as follows: - 1. Open the AWS CloudFormation console at [https://console.aws.amazon.com/cloudformation](https://console.aws.amazon.com/cloudformation/). + 1. Open the CloudFormation console at [https://console.aws.amazon.com/cloudformation](https://console.aws.amazon.com/cloudformation/). @@ -319 +319 @@ The changes in the template that enable this capability are as follows: -If you don't see the updated lines, edit your stack. For details on how to update your AWS CloudFormation stack, see [Modifying a stack template](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-get-template.html) in the _AWS CloudFormation; User Guide_. +If you don't see the updated lines, edit your stack. For details on how to update your CloudFormation stack, see [Modifying a stack template](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-get-template.html) in the _AWS CloudFormation; User Guide_.