AWS snowball documentation change
Summary
Updated product name references from 'AWS Snowball Edge' to 'AWS Snowball Edge Edge' in multiple locations, corrected resource links, and fixed S3 Glacier export documentation references
Security assessment
Changes appear to be typo corrections and branding consistency updates (duplicate 'Edge' removal). No security vulnerabilities, mitigations, or security feature enhancements are mentioned in the diff.
Diff
diff --git a/snowball/latest/developer-guide/how-it-works.md b/snowball/latest/developer-guide/how-it-works.md index f855348b6..1e9896661 100644 --- a/snowball/latest/developer-guide/how-it-works.md +++ b/snowball/latest/developer-guide/how-it-works.md @@ -7 +7 @@ How import jobs workHow export jobs workHow local compute and storage jobs workS -# How AWS Snowball Edge works +# How AWS Snowball Edge Edge works @@ -9 +9 @@ How import jobs workHow export jobs workHow local compute and storage jobs workS -AWS Snowball Edge devices are owned by AWS, and they reside at your on-premises location while they're in use. +AWS Snowball Edge Edge devices are owned by AWS, and they reside at your on-premises location while they're in use. @@ -27 +27 @@ There are three job types you can use with an AWS Snowball Edge device. Although -You can download and install the Snowball Edge client from the [AWS Snowball resources](https://aws.amazon.com/snowball/resources/) page. +You can download and install the Snowball Edge client from the [AWS Snowball Edge resources](https://aws.amazon.com/snowball/resources/) page. @@ -81 +81 @@ The import process also cannot write to your bucket in Amazon S3 if IAM policies -Each export job can use any number of AWS Snowball Edge devices. If the listing contains more data than can fit on a single device, multiple devices are provided to you. Each job part has exactly one device associated with it. After your job parts are created, your first job part enters the **Preparing Snowball** status. +Each export job can use any number of AWS Snowball Edge Edge devices. If the listing contains more data than can fit on a single device, multiple devices are provided to you. Each job part has exactly one device associated with it. After your job parts are created, your first job part enters the **Preparing Snowball** status. @@ -97 +97 @@ Before we export the objects in the S3 bucket, we scan the bucket. If the bucket -It is important to note that AWS Snowball cannot export objects that are in S3 Glacier storage class. These objects must be restored before AWS Snowball can successfully export the objects in the bucket. +It is important to note that AWS Snowball Edge cannot export objects that are in S3 Glacier storage class. These objects must be restored before AWS Snowball Edge can successfully export the objects in the bucket. @@ -118 +118 @@ Like standalone local storage and compute jobs, the data stored in a cluster can -Clusters have 3 to 16 AWS Snowball Edge devices, called _nodes_. When you receive the nodes from your regional carrier, connect all the nodes to power and your network to obtain their IP addresses. You use these IP addresses to unlock all the nodes of the cluster at once with a single unlock command, using the IP address of one of the nodes. For more information, see [Configuring and using the Snowball Edge Client](./using-client-commands.html). +Clusters have 3 to 16 AWS Snowball Edge Edge devices, called _nodes_. When you receive the nodes from your regional carrier, connect all the nodes to power and your network to obtain their IP addresses. You use these IP addresses to unlock all the nodes of the cluster at once with a single unlock command, using the IP address of one of the nodes. For more information, see [Configuring and using the Snowball Edge Client](./using-client-commands.html). @@ -128 +128 @@ When you’re done with your cluster, ship all the nodes back to AWS. When we re - * [AWS Snowball Edge Data Migration](https://d1.awsstatic.com/whitepapers/snowball-edge-data-migration-guide.pdf) + * [AWS Snowball Edge Edge Data Migration](https://d1.awsstatic.com/whitepapers/snowball-edge-data-migration-guide.pdf) @@ -134 +134 @@ When you’re done with your cluster, ship all the nodes back to AWS. When we re - * [Enable large-scale database migrations with DMS and AWS Snowball](https://aws.amazon.com/blogs/storage/enable-large-scale-database-migrations-with-aws-dms-and-aws-snowball/) + * [Enable large-scale database migrations with DMS and AWS Snowball Edge](https://aws.amazon.com/blogs/storage/enable-large-scale-database-migrations-with-aws-dms-and-aws-snowball/) @@ -138 +138 @@ When you’re done with your cluster, ship all the nodes back to AWS. When we re - * [AWS Snowball resources](https://aws.amazon.com/snowball/resources/) + * [AWS Snowball Edge resources](https://aws.amazon.com/snowball/resources/) @@ -140 +140 @@ When you’re done with your cluster, ship all the nodes back to AWS. When we re - * [Amazon S3 Compatible Storage on AWS Snowball Edge Compute Optimized Devices Now Generally Available](https://aws.amazon.com/blogs/aws/amazon-s3-compatible-storage-on-aws-snowball-edge-compute-optimized-devices-now-generally-available/) + * [Amazon S3 Compatible Storage on AWS Snowball Edge Edge Compute Optimized Devices Now Generally Available](https://aws.amazon.com/blogs/aws/amazon-s3-compatible-storage-on-aws-snowball-edge-compute-optimized-devices-now-generally-available/)