AWS transfer documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' throughout the documentation for consistency
Security assessment
The changes are purely branding/terminology updates (removing redundant 'AWS' from CloudFormation references). No security vulnerabilities, mitigations, or security features were added/modified. The password example 'MySuperSecretPassword' remains unchanged but was not part of the actual diff modifications.
Diff
diff --git a/transfer/latest/userguide/custom-lambda-idp.md b/transfer/latest/userguide/custom-lambda-idp.md index 34e56115e..17cc97478 100644 --- a//transfer/latest/userguide/custom-lambda-idp.md +++ b//transfer/latest/userguide/custom-lambda-idp.md @@ -351 +351 @@ Console - 3. Enter the text for **Username** and **Password** that you set when you deployed the AWS CloudFormation stack. If you kept the default options, the username is `myuser` and the password is `MySuperSecretPassword`. + 3. Enter the text for **Username** and **Password** that you set when you deployed the CloudFormation stack. If you kept the default options, the username is `myuser` and the password is `MySuperSecretPassword`. @@ -353 +353 @@ Console - 4. Choose the **Server protocol** and enter the IP address for **Source IP** , if you set them when you deployed the AWS CloudFormation stack. + 4. Choose the **Server protocol** and enter the IP address for **Source IP** , if you set them when you deployed the CloudFormation stack. @@ -369 +369 @@ CLI - 3. Enter the username and password that you set when you deployed the AWS CloudFormation stack. If you kept the default options, the username is `myuser` and the password is `MySuperSecretPassword`. + 3. Enter the username and password that you set when you deployed the CloudFormation stack. If you kept the default options, the username is `myuser` and the password is `MySuperSecretPassword`. @@ -371 +371 @@ CLI - 4. Enter the server protocol and source IP address, if you set them when you deployed the AWS CloudFormation stack. + 4. Enter the server protocol and source IP address, if you set them when you deployed the CloudFormation stack. @@ -391 +391 @@ In the response example below, the `Response` field is a JSON object that has be -You can deploy an AWS CloudFormation stack that uses a Lambda function for authentication. We provide several templates that authenticate and authorize your users using sign-in credentials. You can modify these templates or AWS Lambda code to further customize user access. +You can deploy an CloudFormation stack that uses a Lambda function for authentication. We provide several templates that authenticate and authorize your users using sign-in credentials. You can modify these templates or AWS Lambda code to further customize user access. @@ -395 +395 @@ You can deploy an AWS CloudFormation stack that uses a Lambda function for authe -You can create a FIPS-enabled AWS Transfer Family server through AWS CloudFormation by specifying a FIPS-enabled security policy in your template. Available security policies are described in [Security policies for AWS Transfer Family servers](./security-policies.html) +You can create a FIPS-enabled AWS Transfer Family server through CloudFormation by specifying a FIPS-enabled security policy in your template. Available security policies are described in [Security policies for AWS Transfer Family servers](./security-policies.html) @@ -397 +397 @@ You can create a FIPS-enabled AWS Transfer Family server through AWS CloudFormat -###### To create an AWS CloudFormation stack to use for authentication +###### To create an CloudFormation stack to use for authentication @@ -399 +399 @@ You can create a FIPS-enabled AWS Transfer Family server through AWS CloudFormat - 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/). @@ -401 +401 @@ You can create a FIPS-enabled AWS Transfer Family server through AWS CloudFormat - 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_.