AWS snowball documentation change
Summary
Multiple corrections to service name references from 'AWS Snowball Edge' to 'AWS Snowball Edge Edge' and related terminology updates throughout the document. Updated links and terminology related to IAM policies and encryption support.
Security assessment
Changes primarily involve service name standardization (adding extra 'Edge' in some cases) and terminology updates. No new security vulnerabilities or mitigations are introduced. Existing security-related content (encryption details, IAM policies) remains unchanged except for service name references.
Diff
diff --git a/snowball/latest/developer-guide/snowball-prereqs.md b/snowball/latest/developer-guide/snowball-prereqs.md index ffe1b1067..fdfd3a945 100644 --- a/snowball/latest/developer-guide/snowball-prereqs.md +++ b/snowball/latest/developer-guide/snowball-prereqs.md @@ -11 +11 @@ Before you get started with a Snowball Edge, you need to sign up for an AWS acco -AWS Snowball Edge is a region-specific service. So before you plan your job, be sure that the service is available in your AWS Region. Ensure that your location and Amazon S3 bucket are within the same AWS Region or the same country because it will impact your ability to order the device. +AWS Snowball Edge Edge is a region-specific service. So before you plan your job, be sure that the service is available in your AWS Region. Ensure that your location and Amazon S3 bucket are within the same AWS Region or the same country because it will impact your ability to order the device. @@ -122 +122 @@ Understanding your dataset and how the local environment is set up will help you -Transferring a large number of small files does not work well with AWS Snowball Edge. This is because Snowball Edge encrypts each individual object. Small files include files under 1 MB in size. We recommend that you zip them up before transferring them onto the AWS Snowball Edge device. We also recommend that you have no more than 500,000 files or directories within each directory. +Transferring a large number of small files does not work well with AWS Snowball Edge Edge. This is because Snowball Edge Edge encrypts each individual object. Small files include files under 1 MB in size. We recommend that you zip them up before transferring them onto the AWS Snowball Edge Edge device. We also recommend that you have no more than 500,000 files or directories within each directory. @@ -129 +129 @@ It is important to have a static dataset, (that is, no users or systems are acce -To prevent corrupting your data, don't disconnect an AWS Snowball Edge device or change its network settings while transferring data. Files should be in a static state while being written to the device. Files that are modified while they are being written to the device can result in read/write conflicts. +To prevent corrupting your data, don't disconnect an AWS Snowball Edge Edge device or change its network settings while transferring data. Files should be in a static state while being written to the device. Files that are modified while they are being written to the device can result in read/write conflicts. @@ -131 +131 @@ To prevent corrupting your data, don't disconnect an AWS Snowball Edge device or -**Will the network support AWS Snowball data transfer?** +**Will the network support AWS Snowball Edge data transfer?** @@ -173 +173 @@ It's important to note that if the names of your objects contain special charact -If your files have one or more of these characters in object names, rename the objects before you copy them to the AWS Snowball Edge device. Windows users who have spaces in their file names should be careful when copying individual objects or running a recursive command. In commands, surround the names of objects that include spaces in the names with quotation marks. The following are examples of such files. +If your files have one or more of these characters in object names, rename the objects before you copy them to the AWS Snowball Edge Edge device. Windows users who have spaces in their file names should be careful when copying individual objects or running a recursive command. In commands, surround the names of objects that include spaces in the names with quotation marks. The following are examples of such files. @@ -298 +298 @@ After this policy has been added to the AWS KMS customer managed key, it is also -For more information, see [Using Identity-Based Policies (IAM Policies) for AWS Snowball](./access-control-managing-permissions.html). +For more information, see [Using Identity-Based Policies (IAM Policies) for AWS Snowball Edge](./access-control-managing-permissions.html). @@ -344 +344 @@ After this policy has been added to the AWS KMS customer managed key, it is also -AWS Snowball supports server-side encryption with Amazon S3 managed encryption keys (SSE-S3). Server-side encryption is about protecting data at rest, and SSE-S3 has strong, multifactor encryption to protect your data at rest in Amazon S3. For more information about SSE-S3, see [Protecting Data Using Server-Side Encryption with Amazon S3-Managed Encryption Keys (SSE-S3)](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html) in the _Amazon Simple Storage Service User Guide_. +AWS Snowball Edge supports server-side encryption with Amazon S3 managed encryption keys (SSE-S3). Server-side encryption is about protecting data at rest, and SSE-S3 has strong, multifactor encryption to protect your data at rest in Amazon S3. For more information about SSE-S3, see [Protecting Data Using Server-Side Encryption with Amazon S3-Managed Encryption Keys (SSE-S3)](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html) in the _Amazon Simple Storage Service User Guide_. @@ -348 +348 @@ AWS Snowball supports server-side encryption with Amazon S3 managed encryption k -Currently, AWS Snowball doesn't support server-side encryption with customer-provided keys (SSE-C). However, you might want to use that SSE type to protect data that has been imported, or you might already use it on data you want to export. In these cases, keep the following in mind: +Currently, AWS Snowball Edge doesn't support server-side encryption with customer-provided keys (SSE-C). However, you might want to use that SSE type to protect data that has been imported, or you might already use it on data you want to export. In these cases, keep the following in mind: @@ -400 +400 @@ When ordering a Snow device for local compute and storage with Amazon S3 compati -You can run Amazon EC2-compatible compute instances hosted on an AWS Snowball Edge with the `sbe1`, `sbe-c`, and `sbe-g` instance types: +You can run Amazon EC2-compatible compute instances hosted on an AWS Snowball Edge Edge with the `sbe1`, `sbe-c`, and `sbe-g` instance types: @@ -402 +402 @@ You can run Amazon EC2-compatible compute instances hosted on an AWS Snowball Ed - * The `sbe1` instance type works on devices with the Snowball Edge Storage Optimized option. + * The `sbe1` instance type works on devices with the Snowball Edge Edge Storage Optimized option. @@ -404 +404 @@ You can run Amazon EC2-compatible compute instances hosted on an AWS Snowball Ed - * The `sbe-c` instance type works on devices with the Snowball Edge Compute Optimized option. + * The `sbe-c` instance type works on devices with the Snowball Edge Edge Compute Optimized option. @@ -409 +409 @@ You can run Amazon EC2-compatible compute instances hosted on an AWS Snowball Ed -All the compute instance types supported on Snowball Edge device options are unique to AWS Snowball Edge devices. Like their cloud-based counterparts, these instances require Amazon Machine Images (AMIs) to launch. You choose the AMI for an instance before you create your Snowball Edge job. +All the compute instance types supported on Snowball Edge Edge device options are unique to AWS Snowball Edge Edge devices. Like their cloud-based counterparts, these instances require Amazon Machine Images (AMIs) to launch. You choose the AMI for an instance before you create your Snowball Edge Edge job. @@ -411 +411 @@ All the compute instance types supported on Snowball Edge device options are uni -To use a compute instance on a Snowball Edge, create a job to order a Snowball Edge device and specify your AMIs. You can do this using the AWS Snowball Management Console, the AWS Command Line Interface (AWS CLI), or one of the AWS SDKs. Typically, to use your instances, there are some housekeeping prerequisites that you must perform before creating your job. +To use a compute instance on a Snowball Edge Edge, create a job to order a Snowball Edge device and specify your AMIs. You can do this using the AWS Snowball Edge Management Console, the AWS Command Line Interface (AWS CLI), or one of the AWS SDKs. Typically, to use your instances, there are some housekeeping prerequisites that you must perform before creating your job.