AWS whitepapers documentation change
Summary
Updated references from 'Snowball' to 'Snowball Edge' throughout the document, including management console names, device types, client tools, and command syntax. Fixed redundant 'Edge Edge' typo in device type description.
Security assessment
Changes primarily involve product name updates from Snowball to Snowball Edge without introducing new security concepts. Existing security references to IAM roles and KMS encryption were maintained but updated to match the product name. No vulnerabilities or new security features were addressed.
Diff
diff --git a/whitepapers/latest/overview-aws-cloud-data-migration-services/use-case-1-one-time-massive-data-migration.md b/whitepapers/latest/overview-aws-cloud-data-migration-services/use-case-1-one-time-massive-data-migration.md index 95be46f13..5d1384b69 100644 --- a/whitepapers/latest/overview-aws-cloud-data-migration-services/use-case-1-one-time-massive-data-migration.md +++ b/whitepapers/latest/overview-aws-cloud-data-migration-services/use-case-1-one-time-massive-data-migration.md @@ -11 +11 @@ _Figure 2 - One-time massive data migration_ -In use case 1, a customer goes through the process of decommissioning a data center and moving the entire workload to the cloud. First, all the current corporate data needs to be migrated. To complete this migration AWS Snowball appliances are used to move the data from the customer’s existing data center to an Amazon S3 bucket in the AWS Cloud. +In use case 1, a customer goes through the process of decommissioning a data center and moving the entire workload to the cloud. First, all the current corporate data needs to be migrated. To complete this migration AWS Snowball Edge appliances are used to move the data from the customer’s existing data center to an Amazon S3 bucket in the AWS Cloud. @@ -13 +13 @@ In use case 1, a customer goes through the process of decommissioning a data cen - 1. Customer creates a new data transfer job in the AWS Snowball Management Console by providing the following information. + 1. Customer creates a new data transfer job in the AWS Snowball Edge Management Console by providing the following information. @@ -19 +19 @@ In use case 1, a customer goes through the process of decommissioning a data cen - 3. Enter job details, such as name of the job, destination AWS Region, destination Amazon S3 bucket to receive the imported data, and Snowball Edge device type. + 3. Enter job details, such as name of the job, destination AWS Region, destination Amazon S3 bucket to receive the imported data, and Snowball Edge Edge device type. @@ -21 +21 @@ In use case 1, a customer goes through the process of decommissioning a data cen - 4. Enter security settings indicating the IAM role Snowball assumes to import the data and AWS KMS key used to encrypt the data within Snowball. + 4. Enter security settings indicating the IAM role Snowball Edge assumes to import the data and AWS KMS key used to encrypt the data within Snowball Edge. @@ -27 +27 @@ In use case 1, a customer goes through the process of decommissioning a data cen - 2. After the job is created, AWS ships the Snowball Appliances to the customer data center by AWS. In this example, the customer is importing 200 TB of data into Amazon S3, they will need to create three Import jobs of 80 TB Snowball Edge Storage Optimized capacity. + 2. After the job is created, AWS ships the Snowball Edge Appliances to the customer data center by AWS. In this example, the customer is importing 200 TB of data into Amazon S3, they will need to create three Import jobs of 80 TB Snowball Edge Edge Storage Optimized capacity. @@ -29 +29 @@ In use case 1, a customer goes through the process of decommissioning a data cen - 3. After receiving the Snowball appliance, the customer performs the following tasks. + 3. After receiving the Snowball Edge appliance, the customer performs the following tasks. @@ -33 +33 @@ In use case 1, a customer goes through the process of decommissioning a data cen - 2. After the Snowball is ready, the customer uses the E-Ink display to choose the network settings and assign an IP address to the appliance. + 2. After the Snowball Edge is ready, the customer uses the E-Ink display to choose the network settings and assign an IP address to the appliance. @@ -35 +35 @@ In use case 1, a customer goes through the process of decommissioning a data cen - 4. The customer transfers the data to the Snowball appliance using the following steps. + 4. The customer transfers the data to the Snowball Edge appliance using the following steps. @@ -37 +37 @@ In use case 1, a customer goes through the process of decommissioning a data cen - 1. Download the credentials consisting of a manifest file and an unlock code for a specific Snowball job from [AWS Snow Family Management Console](https://console.aws.amazon.com/snowfamily/home). + 1. Download the credentials consisting of a manifest file and an unlock code for a specific Snowball Edge job from [AWS Snow Family Management Console](https://console.aws.amazon.com/snowfamily/home). @@ -39 +39 @@ In use case 1, a customer goes through the process of decommissioning a data cen - 2. Install the [Snowball Client](https://aws.amazon.com/snowball/resources/) on an on-premises machine to manage the flow of data from the on-premises data source to the Snowball. + 2. Install the [Snowball Edge Client](https://aws.amazon.com/snowball/resources/) on an on-premises machine to manage the flow of data from the on-premises data source to the Snowball Edge. @@ -41 +41 @@ In use case 1, a customer goes through the process of decommissioning a data cen - 3. Access the Snowball client using the terminal or command prompt on the workstation and typing the following command: + 3. Access the Snowball Edge client using the terminal or command prompt on the workstation and typing the following command: @@ -43 +43 @@ In use case 1, a customer goes through the process of decommissioning a data cen - snowballEdge unlock-device --endpoint [https://Snowball IP Address] --manifest [Path/to/manifest/file] –unlock-code [29 character unlock code] + snowballEdge unlock-device --endpoint [https://Snowball Edge IP Address] --manifest [Path/to/manifest/file] –unlock-code [29 character unlock code] @@ -45 +45 @@ In use case 1, a customer goes through the process of decommissioning a data cen - 4. Begin transferring data onto the Snowball using the following tools: + 4. Begin transferring data onto the Snowball Edge using the following tools: @@ -51 +51 @@ In use case 1, a customer goes through the process of decommissioning a data cen - 5. After the data transfer is complete, disconnect the Snowball from your network and seal the Snowball. After being properly sealed, the return shipping label appears on the E-Ink display. Arrange UPS pickup of the appliance for shipment back to AWS. + 5. After the data transfer is complete, disconnect the Snowball Edge from your network and seal the Snowball Edge. After being properly sealed, the return shipping label appears on the E-Ink display. Arrange UPS pickup of the appliance for shipment back to AWS. @@ -53 +53 @@ In use case 1, a customer goes through the process of decommissioning a data cen - 6. UPS automatically reports back a tracking number for the job to the AWS Snowball Management Console. The customer can access that tracking number, and a link to the UPS tracking website by viewing the job's status details in the console. + 6. UPS automatically reports back a tracking number for the job to the AWS Snowball Edge Management Console. The customer can access that tracking number, and a link to the UPS tracking website by viewing the job's status details in the console. @@ -55 +55 @@ In use case 1, a customer goes through the process of decommissioning a data cen - 7. After the appliance is received at the AWS Region, the job status changes from _**In transit to AWS**_ to _**At AWS**_. On average, it takes a day for data import into Amazon S3 to begin. When the import starts, the status of the job changes to **Importing**. From this point on, it takes an average of two business days for your import to reach **Completed** status. You can track status changes through the AWS Snowball Management Console or by Amazon SNS notifications. + 7. After the appliance is received at the AWS Region, the job status changes from _**In transit to AWS**_ to _**At AWS**_. On average, it takes a day for data import into Amazon S3 to begin. When the import starts, the status of the job changes to **Importing**. From this point on, it takes an average of two business days for your import to reach **Completed** status. You can track status changes through the AWS Snowball Edge Management Console or by Amazon SNS notifications.