AWS solutions documentation change
Summary
Updated terminology from 'solution' to 'Guidance' and modified credential storage references
Security assessment
Changes focus on branding terminology updates. While credentials in Secrets Manager are mentioned, this is existing security practice documentation rather than new security content.
Diff
diff --git a/solutions/latest/data-transfer-hub/create-an-amazon-s3-transfer-task.md b/solutions/latest/data-transfer-hub/create-an-amazon-s3-transfer-task.md index c525822ba..f167d4d8d 100644 --- a//solutions/latest/data-transfer-hub/create-an-amazon-s3-transfer-task.md +++ b//solutions/latest/data-transfer-hub/create-an-amazon-s3-transfer-task.md @@ -9 +9 @@ Using the web consoleUsing the S3 pluginUsing AWS CLIHow to transfer S3 object f -The solution allows you to create an Amazon S3 transfer task in the following ways: +The Guidance allows you to create an Amazon S3 transfer task in the following ways: @@ -33 +33 @@ You can make your choice according to your needs. -You can use the web console to create an Amazon S3 transfer task. For more information about how to launch the web console, see [Deploy the solution](./deploy-the-solution.html#deployment-overview). +You can use the web console to create an Amazon S3 transfer task. For more information about how to launch the web console, see [Deploy the Guidance](./deploy-the-solution.html#deployment-overview). @@ -163 +163 @@ This tutorial provides guidance for the backend-only version. For more details, -This solution can be deployed in both public and private subnets. Using public subnets is recommended. +This Guidance can be deployed in both public and private subnets. Using public subnets is recommended. @@ -167 +167 @@ This solution can be deployed in both public and private subnets. Using public s - * If you want to create new default VPC for this solution, please go to Step 2 and make sure you have >**Create a new VPC for this cluster** selected when you create the cluster. + * If you want to create new default VPC for this Guidance, please go to Step 2 and make sure you have >**Create a new VPC for this cluster** selected when you create the cluster. @@ -174 +174 @@ This solution can be deployed in both public and private subnets. Using public s -You need to provide AccessKeyID and SecretAccessKey (namely AK/SK) to read or write bucket in S3 from or to another AWS account or other cloud storage service, and the credential will be stored in AWS Secrets Manager. You do not need to create credential for the bucket in the current account where you are deploying the solution. +You need to provide AccessKeyID and SecretAccessKey (namely AK/SK) to read or write bucket in S3 from or to another AWS account or other cloud storage service, and the credential will be stored in AWS Secrets Manager. You do not need to create credential for the bucket in the current account where you are deploying the Guidance. @@ -200 +200 @@ If the AK/SK is for source bucket, READ access to bucket is required; if it is f -Please follow below steps to deploy this solution via AWS Cloudformation. +Please follow below steps to deploy this Guidance via AWS Cloudformation.