How do I troubleshoot stuck data transfers from my Snowball Edge device to Amazon S3?

Short description

Data transfers from your Snowball Edge device to your S3 bucket might be stuck for the following reasons:

• You didn't complete required actions.
• You encrypted your S3 bucket with AWS Key Management Service (AWS KMS) server-side encryption (SSE-KMS), but you don't have the required permissions to use the key.

Resolution

Complete required actions

Take the following actions:

• Check your AWS account's primary contact email for actionable notifications, and then complete the actions.
  Note: To update your contact information, see Update the primary contact for your AWS account.
• Check the AWS Support Center for active cases, and complete requested actions from AWS Support.
• Update the software on your Snowball Edge device.

You don't have AWS KMS permissions

To grant AWS KMS permissions to your AWS Identity and Access Management (IAM) role, update the permissions policy for your Snow import IAM role.

If you don't have a permissions policy for your IAM role, then complete the following steps to create one:

1. Open the IAM console.

2. In the navigation pane, choose Roles.

3. In the search box, enter Snow, and then choose the Snow import IAM role.

4. Choose the Permissions tab.

5. Choose the Add permissions dropdown list.

6. Choose Create inline policy.

7. Choose the JSON tab, and then enter the following policy:

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Effect": "Allow",
               "Action": [
                   "kms:Decrypt",
                   "kms:GenerateDataKey"
               ],
               "Resource": "arn:aws:kms:region:account-id:key/key-id"
           }
       ]
   }

   Note: Replace region, account-id, and key-id with your values.

8. Choose Review policy.

9. Enter a name for the policy.

10. Choose Create policy.

After you add the required permissions, the data import automatically resumes. If there's no increase in the import percentage and no active cases from AWS, then contact AWS Support.