AWS solutions documentation change
Summary
Updated terminology from 'solution' to 'Guidance' throughout the FAQ document
Security assessment
Changes are purely terminological (solution -> Guidance) without altering security content. Security-related sections (encryption, authentication, TLS) maintain the same technical substance with updated branding. No new security features or vulnerabilities addressed.
Diff
diff --git a/solutions/latest/data-transfer-hub/faq.md b/solutions/latest/data-transfer-hub/faq.md index ce08cc2ef..713ef3055 100644 --- a//solutions/latest/data-transfer-hub/faq.md +++ b//solutions/latest/data-transfer-hub/faq.md @@ -9 +9 @@ DeploymentPerformanceData security and authenticationFeaturesOthers -The following are common questions you might have when deploying and using the solution. +The following are common questions you might have when deploying and using the Guidance. @@ -13 +13 @@ The following are common questions you might have when deploying and using the s -**1\. In which AWS Regions can this solution be deployed?** +**1\. In which AWS Regions can this Guidance be deployed?** @@ -19 +19 @@ For the list of supported Regions, refer to [Supported AWS Regions](./plan-your- -The transfer performance of the solution will not be affected by whether the deployment is on the data source or destination side. +The transfer performance of the Guidance will not be affected by whether the deployment is on the data source or destination side. @@ -32 +32 @@ If you need to deploy in AWS China Regions but do not have a domain name, you ca -**3\. Do I need to deploy the solution on the data source and destination side separately?** +**3\. Do I need to deploy the Guidance on the data source and destination side separately?** @@ -36 +36 @@ No. You can choose to deploy on the data source or destination side, which has n -**4\. Is it possible to deploy the solution in AWS account A and transfer Amazon S3 objects from account B to account C?** +**4\. Is it possible to deploy the Guidance in AWS account A and transfer Amazon S3 objects from account B to account C?** @@ -40 +40 @@ Yes. In this case, you need to store the[ AccessKeyID and SecretAccessKey](https -**5\. For data transfer within the production account, is it recommended to create an AWS account specifically for deploying the solution?** +**5\. For data transfer within the production account, is it recommended to create an AWS account specifically for deploying the Guidance?** @@ -42 +42 @@ Yes. In this case, you need to store the[ AccessKeyID and SecretAccessKey](https -Yes. It is recommended to create a new AWS account dedicated to deploying solutions. The account-level isolation improves the stability of the production account in the data synchronization process. +Yes. It is recommended to create a new AWS account dedicated to deploying Guidances. The account-level isolation improves the stability of the production account in the data synchronization process. @@ -82 +82 @@ The Auto Scaling group will [automatically scale up](https://docs.aws.amazon.com -**1\. How does the solution ensure data security?** +**1\. How does the Guidance ensure data security?** @@ -84 +84 @@ The Auto Scaling group will [automatically scale up](https://docs.aws.amazon.com -The solution adopts the following to ensure data security: +The Guidance adopts the following to ensure data security: @@ -95 +95 @@ The solution adopts the following to ensure data security: -**2\. How does the solution ensure the security of resources on the cloud?** +**2\. How does the Guidance ensure the security of resources on the cloud?** @@ -103 +103 @@ Yes. You can access it with a front-end console link. User authentication and mu -**4\. How does the solution achieve cross-account and cross-cloud authentication?** +**4\. How does the Guidance achieve cross-account and cross-cloud authentication?** @@ -107 +107 @@ By authentication through the Access Keyid and Access Key of the other party’s -**5\. Does the solution support SSE-S3, SSE-KMS, and SSE-CMK?** +**5\. Does the Guidance support SSE-S3, SSE-KMS, and SSE-CMK?** @@ -109 +109 @@ By authentication through the Access Keyid and Access Key of the other party’s -Yes. The solution supports the use of SSE-S3 and SSE-KMS data sources. If your source bucket has SSE-CMK enabled, refer to the [tutorial.](./create-an-amazon-s3-transfer-task.html) +Yes. The Guidance supports the use of SSE-S3 and SSE-KMS data sources. If your source bucket has SSE-CMK enabled, refer to the [tutorial.](./create-an-amazon-s3-transfer-task.html) @@ -125 +125 @@ Moreover, when the default comparison task once an hour finds a difference, it w -Based on the built-in automatic expansion function of the solution, when there is no data to be transferred, the number of transfer working nodes will be automatically reduced to the minimum value configured by the user. +Based on the built-in automatic expansion function of the Guidance, when there is no data to be transferred, the number of transfer working nodes will be automatically reduced to the minimum value configured by the user. @@ -156 +156 @@ At Task Scheduling Settings, you can make the task scheduling configuration. -Near-real-time synchronization can be achieved, only if the Data Transfer Hub is deployed in the same AWS account and the same region as the data source. If the data source and the solution are not in the same account, you can configure it manually. For more information, refer to the [tutorial](https://github.com/awslabs/data-transfer-hub/blob/v2.0.0/docs/s3-event-trigger-config.md). +Near-real-time synchronization can be achieved, only if the Data Transfer Hub is deployed in the same AWS account and the same region as the data source. If the data source and the Guidance are not in the same account, you can configure it manually. For more information, refer to the [tutorial](https://github.com/awslabs/data-transfer-hub/blob/v2.0.0/docs/s3-event-trigger-config.md). @@ -202 +202 @@ No. Currently, Payer Request data synchronization is only supported through Acce -The Auto Scaling mechanism of the solution will enable automatic restart of a new working node. +The Auto Scaling mechanism of the Guidance will enable automatic restart of a new working node. @@ -208 +208 @@ However, if a sharding task being transferred in the node is mistakenly terminat -You need to update Secrets in Secrets Manager first, and then go to the EC2 console to Terminate all EC2 instances that have been started by the task. Later, the Auto Scaling mechanism of the solution will automatically start a new working node and update Secrets to it. +You need to update Secrets in Secrets Manager first, and then go to the EC2 console to Terminate all EC2 instances that have been started by the task. Later, the Auto Scaling mechanism of the Guidance will automatically start a new working node and update Secrets to it. @@ -242 +242 @@ If you want to make customized changes to this plugin, refer to [Custom Build](h -This is because the subnet you selected when deploying this solution does not have public network access, and the EC2 cannot download the CloudWatch agent to send logs to CloudWatch. Check your VPC settings. After resolving the issue, you need to manually terminate the running EC2 instance (if any) through this solution. Later, the elastic scaling group will automatically start a new instance. +This is because the subnet you selected when deploying this Guidance does not have public network access, and the EC2 cannot download the CloudWatch agent to send logs to CloudWatch. Check your VPC settings. After resolving the issue, you need to manually terminate the running EC2 instance (if any) through this Guidance. Later, the elastic scaling group will automatically start a new instance. @@ -244 +244 @@ This is because the subnet you selected when deploying this solution does not ha -**6\. How to use TLSv1.2_2021 or later for this solution?** +**6\. How to use TLSv1.2_2021 or later for this Guidance?** @@ -246 +246 @@ This is because the subnet you selected when deploying this solution does not ha -Please go to the [CloudFront Console](https://us-east-1.console.aws.amazon.com/cloudfront/v3/home#/distributions) and configure a custom domain, which will allow you to select a Security policy for CloudFront after solution deployment. You need to prepare a domain name and a corresponding TLS certificate in order to use more secure TLS configurations. +Please go to the [CloudFront Console](https://us-east-1.console.aws.amazon.com/cloudfront/v3/home#/distributions) and configure a custom domain, which will allow you to select a Security policy for CloudFront after Guidance deployment. You need to prepare a domain name and a corresponding TLS certificate in order to use more secure TLS configurations. @@ -254 +254 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Uninstall the solution +Uninstall the Guidance