AWS Snowball Edge is no longer available to new customers. New customers should explore [AWS DataSync](https://aws.amazon.com/datasync/) for online transfers, [AWS Data Transfer Terminal](https://aws.amazon.com/data-transfer-terminal/) for secure physical transfers, or AWS Partner solutions. For edge computing, explore [AWS Outposts](https://aws.amazon.com/outposts/). # Getting started with Snowball Edge With an AWS Snowball Edge device, you can access the storage and compute power of the AWS Cloud locally and cost effectively in places where connecting to the internet might not be an option. You can also transfer hundreds of terabytes or petabytes of data between your on-premises data centers and Amazon Simple Storage Service (Amazon S3). Following, you can find general instructions for creating and completing your first AWS Snowball Edge device job in the AWS Snow Family Management Console. The console presents the most common workflows, separated into job types. You can find more information about specific components of the AWS Snowball Edge device in this documentation. For an overview of the service as a whole, see [How AWS Snowball Edge works](how-it-works.md). It may take up to 4 weeks to provision and prepare the Snowball Edge for your job before it is shipped. This timeline should be factored into your project plan to ensure a seamless transition. Before you can get started, you must create an AWS account and an administrator user in AWS Identity and Access Management (IAM). For information, see [Prerequisites for using Snowball Edge](snowball-prereqs.md). **Topics** + [ # Creating a job to order a Snowball Edge device ](create-job-common.md) + [ # Cancelling a job to order a Snowball Edge ](cancel-job-order.md) + [ # Cloning a job to order a Snowball Edge in the AWS Snow Family Management Console ](clonejob.md) + [ # Receiving the Snowball Edge ](receive-device.md) + [ ## Connecting a Snowball Edge to your local network ](#getting-started-connect) + [ ## Getting credentials to access a Snowball Edge ](#get-credentials) + [ # Unlocking the Snowball Edge ](unlockdevice.md) + [ ## Setting up local users on a Snowball Edge ](#setup-local-iam) + [ # Rebooting the Snowball Edge device ](reboot.md) + [ # Powering off the Snowball Edge ](turnitoff.md) + [ # Returning the Snowball Edge device ](return-device.md) + [ # Return shipping for Snowball Edge ](mailing-storage.md) + [ # Monitoring the import status from the Snowball Edge ](monitor-status.md) + [ # Getting your data transfer job completion report and logs ](report.md) # Creating a job to order a Snowball Edge device To order a Snowball Edge device, you create a job to order a Snowball Edge device in the AWS Snow Family Management Console. A *job* is a term that AWS uses to describe the lifecycle of the use of a Snowball Edge device by a customer. A job begins when you order a device, continues when AWS prepares the device and ships it to you and you use it, and completes after AWS receives and processes the device after you return it. Jobs are categorized by type: export, import, and local compute and storage. For more information, see [Understanding AWS Snowball Edge jobs](https://docs.aws.amazon.com/snowball/latest/developer-guide/jobs.html). After you create the job to order a device, you can use the AWS Snow Family Management Console to view the job status and monitor the progress of the device you ordered as AWS prepares the device to ship to you and after it is returned. For more information, see [Job Statuses](https://docs.aws.amazon.com/snowball/latest/developer-guide/jobstatuses.html). After the device is returned and processed by AWS, you can access a job completion report and logs through the AWS Snow Family Management Console. For more information, see [Getting your job completion report and logs on the console](https://docs.aws.amazon.com/snowball/latest/developer-guide/report.html). You can also create and manage jobs using the job management API. For more information, see the [AWS Snowball Edge API Reference](https://docs.aws.amazon.com/snowball/latest/api-reference/api-reference.html). **Topics** + [ ## Choosing a job type ](#plan-job) + [ ## Choosing your compute and storage options ](#compute-storage) + [ ## Choosing your features and options ](#import-job-details) + [ ## Choosing security, shipping, and notification preferences ](#security-shipping-notification) + [ ## Reviewing the job summary and create your job ](#review-job) ## Choosing a job type The first step in creating a job is to determine the type of job that you need and to start planning it using the AWS Snow Family Management Console. **To choose your job type** 1. Sign in to the AWS Management Console, and open the [AWS Snow Family Management Console](https://console.aws.amazon.com/snowfamily/home). If this is your first time creating a job in this AWS Region, you will see the **AWS Snowball Edge** page. Otherwise you will see the list of existing jobs. 1. If this is your first job to order a device, choose **Order an AWS Snowball Edge device**. If you're expecting multiple jobs to migrate over 500 TB of data, choose **Create your large data migration plan greater than 500 TB**. Otherwise, choose **Create Job** in the left navigation bar. Choose **Next step** to open the **Plan your job** page. 1. In the **Job name** section, provide a name for your job in the **Job name** box. 1. Depending on your need, choose one of the following job types: + **Import into Amazon S3** – Choose this option to have AWS ship an empty Snowball Edge device to you. You connect the device to your local network and run the Snowball Edge client. You copy data onto the device using NFS share or the S3 adapter, ship it back to AWS, and your data is uploaded to AWS. + **Export from Amazon S3** – Choose this option to export data from your Amazon S3 bucket to your device. AWS loads your data on the device and ships it to you. You connect the device to your local network and run the Snowball Edge client. You copy data from your device to your servers. When you are done, ship the device to AWS, and your data is erased from the device. + **Local compute and storage only** – Perform compute and storage workloads on the device without transferring data. ![\[Choose job type panel showing Import into Amazon S3 job type selected.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/choose-job-type-console.png) 1. Choose **Next** to continue. ## Choosing your compute and storage options Choose the hardware specifications for your Snowball Edge device, which of your Amazon EC2-compatible instances to include on it, how data will be stored, and pricing. **To choose your device's compute and storage options** 1. In the **Snow devices** section, choose the Snowball Edge device to order. **Note** Some Snowball Edge might not be available depending on the AWS Region you are ordering from and the job type you chose. 1. In the **Choose your pricing option** section, from the **Choose your pricing option** menu, choose the type of pricing to apply to this job. If you choose 1 year or 3 year commit upfront pricing, in **Auto-renew**, choose **On** to automatically renew the pricing when the current period ends or **Off** to not automatically renew the pricing when the current period ends. For more information about long-term pricing options for Snowball Edge devices, see [Long-term pricing for Snowball Edge devices](https://docs.aws.amazon.com/snowball/latest/developer-guide/pricing.html) in this guide. For device pricing for your AWS Region, see [AWS Snowball Edge Pricing](https://aws.amazon.com/snowball/pricing). 1. In the **Select the storage type** section, make a choice according to your need: + **S3 Adapter**: Use the S3 adapter to transfer data programmatically to and from Snowball Edge using Amazon S3 REST API actions. + **Amazon S3 compatible storage**: Use Amazon S3 compatible storage to deploy S3 compatible durable, scalable object storage on single Snowball Edge device or in a multi-device cluster. + **NFS based data transfer**: Use Network File System (NFS) based data transfer to drag and drop files from your computer into Amazon S3 buckets on Snowball Edge. **Warning** NFS based data transfer doesn't support the S3 adapter. If you proceed with NFS based data transfer, you must mount the NFS share to transfer objects. Using the AWS CLI to transfer objects will fail. See [Using NFS for Offline Data Transfer](https://docs.aws.amazon.com/snowball/latest/developer-guide/shared-using-nfs.html) in the AWS Snowball Edge Edge Developer Guide for more information. **Note** Storage type options available depend on the job type and Snow device you chose. 1. If you selected *S3 Adapter* as the storage type or if you selected a device that supports block storage, do the following to select one or more S3 buckets to include on the device: 1. In the **Select your S3 buckets** section, do one or more of the following to select one or more S3 buckets: 1. Choose the S3 bucket that you want to use in the **S3 bucket name** list. 1. In the **Search for an item** field, enter all or part a bucket name to filter the list of available buckets on your entry, then choose the bucket. 1. Choose the **Create a new S3 bucket** to create a new S3 bucket. The new bucket name appears in the **Bucket name** list. Choose it. You can include one or more S3 buckets. These buckets appear on your device as local S3 buckets. ![\[Select your S3 buckets panel showing Create a new S3 bucket button, search filed, and S3 bucket names.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/select-s3-buckets-console.png) 1. If you selected *Amazon S3 compatible storage* as the storage type, in the **S3 storage capacity** section, do the following: 1. Select to use Amazon S3 compatible storage on Snowball Edge on a single device or a cluster of devices. See [Using a AWS Snowball Edge cluster](https://docs.aws.amazon.com/snowball/latest/developer-guide/UsingCluster.html) in this guide. 1. Select the amount of device storage to use for Amazon S3 compatible storage on Snowball Edge. **Note** When using Amazon S3 compatible storage on Snowball Edge, you can manage and create Amazon S3 buckets after you receive the device, so you don't need to choose them while ordering. See [Amazon S3 compatible storage on Snowball Edge](https://docs.aws.amazon.com/snowball/latest/developer-guide/s3compatible-on-snow.html) in this guide. ![\[S3 storage capacity panel showing single device selected as the device type and storage amount.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/S3-storage-capacity-console.png) 1. If you selected *NFS based data transfer* as the storage type, in the **Select your S3 buckets** section, do one or more of the following to select one or more S3 buckets: 1. Choose the S3 bucket that you want to use in the **S3 bucket name** list. 1. In the **Search for an item** field, enter all or part a bucket name to filter the list of available buckets on your entry, then choose the bucket. 1. Choose the **Create a new S3 bucket** to create a new S3 bucket. The new bucket name appears in the **Bucket name** list. Choose it. 1. After choosing S3 buckets to use with NFS data transfer, also choose an S3 bucket to use as block storage for AMIs. See the steps to choose an [S3](#s3-adapter) bucket. You can include one or more S3 buckets. These buckets appear on your device as local S3 buckets. ![\[Choose your NFS storage panel showing Create a new S3 bucket button, search filed, and S3 bucket names.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/choose-nfs-storage-console.png) 1. In the **Compute using EC2-compatible instances - *optional*** section, choose Amazon EC2-compatible AMIs from your account to include on the device. Or, in the search field, enter all or part the name of an AMI to filter the list of available AMIs on your entry, then choose the AMI. To learn about configuring an AMI for secure shell (SSH), see [Configuring an AMI for a Snowball Edge and SSH](https://docs.aws.amazon.com//snowball/latest/developer-guide/ssh-ec2-edge.html) For more information, see [Adding an AMI When Ordering Your Device](https://docs.aws.amazon.com//snowball/latest/developer-guide/using-ami.html#add-ami-order) in this guide. This feature incurs additional charges. For more information, see [AWS Snowball Edge Pricing.](https://aws.amazon.com/snowball/pricing/) 1. Choose the **Next** button. ## Choosing your features and options Choose the features and options to include in your AWS Snowball Edge device job, including Amazon EKS Anywhere for Snow, an AWS IoT Greengrass instance, and remote device management capability. **To choose your features and options** 1. In the **Amazon EKS Anywhere on AWS Snow** section, to include Amazon EKS Anywhere on AWS Snow, select **Include Amazon EKS Anywhere on Snow** and then do the following. **Note** We recommend that you create your Kubernetes cluster with the latest available Kubernetes version supported by Amazon EKS Anywhere. For more information, see [Amazon EKS-Anywhere Versioning](https://anywhere.eks.amazonaws.com/docs/concepts/support-versions/). If your application requires a specific version of Kubernetes, use any version of Kubernetes offered in standard or extended support by Amazon EKS. Consider the release and support dates of Kubernetes versions when planning the lifecycle of your deployment. This will help you avoid the potential loss of support for the version of Kubernetes you intend to use. For more information, see [Amazon EKS Kubernetes release calendar](https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html#kubernetes-release-calendar). 1. In the **Build your own AMI** section, choose the AMIs you have built for Amazon EKS Anywhere. See [Actions to complete before ordering a Snowball Edge device for Amazon EKS Anywhere on AWS Snow](eksa-gettingstarted.md). 1. In the **High availability** section, to operate Amazon EKS Anywhere clusters across multiple Snowball Edge devices, choose the number of devices to include in your order. 1. In the **AWS IoT Greengrass on Snow** section, to include a validated AMI for IoT workloads, select **Install AWS IoT Greengrass validated AMI on my Snow device**. 1. To enable remote management of your Snowball Edge device by AWS OpsHub or Snowball Edge Client, select **Manage your Snow device remotely with AWS OpsHub or Snowball Edge Client**. 1. Select the **Next** button. ## Choosing security, shipping, and notification preferences **Topics** + [ ### Choose security preferences for the Snowball Edge ](#set-security) + [ ### Choose your shipping preferences for receiving and returning the Snowball Edge ](#shipping-preferences) + [ ### Choose preferences for notifications about the Snowball Edge job ](#setup-notifications) ### Choose security preferences for the Snowball Edge Setting security adds the permissions and encryption settings for your AWS Snowball Edge job to help protect your data while in transit. **Topics** **To set security for your job** 1. In the **Encryption** section, choose the **KMS key** that you want to use. + If you want to use the default AWS Key Management Service (AWS KMS) key, choose **AWS/importexport (default)**. This is the default key that protects your import and export jobs when no other key is defined. + If you want to provide your own AWS KMS key, choose **Enter a key ARN**, provide the Amazon Resource Name (ARN) in the **key ARN** box, and choose **Use this KMS key**. The key ARN will be added to the list. 1. In the **Choose service access type** section, do one of the following: + Choose **Snow console will create and use a service-linked role to access AWS resources on your behalf.** to grant AWS Snowball Edge permissions to use Amazon S3 and Amazon Simple Notification Service (Amazon SNS) on your behalf. The role grants AWS Security Token Service (AWS STS) AssumeRole trust to the Snow service + Choose **Add an existing service role to use**, to specify the **Role ARN** that you want, or you can use the default role. 1. Choose **Next**. ### Choose your shipping preferences for receiving and returning the Snowball Edge Receiving and returning a Snowball Edge device involves shipping the device back and forth, so it's important that you provide accurate shipping information. **To provide shipping details** 1. In the **Shipping Address** section, choose an existing address or add a new address. + If you choose **Use recent address**, the addresses on file are displayed. Carefully choose the address that you want from the list. + If you choose **Add a new address**, provide the requested address information. The AWS Snow Family Management Console saves your new shipping information. **Note** The country that you provide in the address must match the destination country for the device and must be valid for that country. 1. In the **Shipping speed** section, choose a shipping speed for the job. The shipping speed doesn’t indicate how soon you can expect to receive the device from the day you created the job. Rather, it indicates the time that the device is in transit between AWS and your shipping address. It may take up to 4 weeks to provision and prepare the device for your job before it is shipped. This timeline should be factored into your project plan to ensure a seamless transition. The shipping speeds you can choose are: + **One-Day Shipping (1 business day)** + **Two-Day Shipping (2 business days)** ### Choose preferences for notifications about the Snowball Edge job Notifications update you on the latest status of your AWS Snowball Edge jobs. You create an SNS topic and receive emails from Amazon Simple Notification Service (Amazon SNS) as your job status changes. **To set up notifications** + In the **Set notifications** section, do one of the following: + If you want to use an existing SNS topic, choose **Use an existing SNS topic**, and choose the topic Amazon Resource Name (ARN) from the list. + If you want to create a new SNS topic, choose **Create a new SNS topic**. Enter a name for your topic and provide an email address. **Note** Jobs to order Snow devices created in the US West (N. California) and US West (Oregon) regions are routed through US East (N. Virginia) region. Because of this, service calls like Amazon SNS are also directed through US East (N. Virginia). We recommend creating any new SNS topics in the US East (N. Virginia) region for the best experience. Notifications will be about one of the following states of your job: + Job created + Preparing device + Preparing shipment + In transit to you + Delivered to you + In transit to AWS + At sorting facility + At AWS + Importing + Completed + Canceled For more information about job status change notifications and encrypted SNS topics, see [Notifications for Snowball Edge](https://docs.aws.amazon.com/snowball/latest/developer-guide/notifications.html) in this guide. Select the **Next**. ## Reviewing the job summary and create your job After you provide all the necessary information for your AWS Snowball Edge job, review the job and create it. After you create the job, AWS will begin preparing the Snowball Edge for shipment to you. Jobs are subject to export control laws in specific countries and might require an export license. US export and re-export laws also apply. Diversion from the country and US laws and regulations is prohibited. **** 1. In the **Job summary** page, review all the sections before you create the job. If you want to make changes, choose **Edit** for the appropriate section, and edit the information. 1. When you are done reviewing and editing, choose **Create job**. **Note** After you create a job to order a Snowball Edge device, you can cancel it while it is in the *Job created* state without incurring any charges. For more information, see [Cancelling a job through the AWS Snow Family Management Console](https://docs.aws.amazon.com/snowball/latest/developer-guide/cancel-job-order.html). After your job is created, you can see the status of the job in the **Job status** section. For detailed information about job statuses, see [Job Statuses](https://docs.aws.amazon.com/snowball/latest/developer-guide/jobstatuses.html). # Cancelling a job to order a Snowball Edge After creating a job to order a Snowball Edge device, you can cancel the job through the AWS Snow Family Management Console. If you cancel the job, you won't receive the device you ordered. You can only cancel the job while the job status is *Job created*. After the job progresses past this status, you cannot cancel the job. For more information, see [Job Statuses](https://docs.aws.amazon.com/snowball/latest/developer-guide/jobstatuses.html). When you cancel a job while it's in the *Job created* status, you will not be charged for the Snowball Edge device. Billing only begins after the device has been prepared and shipped to you. 1. Log in to the [AWS Snow Family Management Console](https://console.aws.amazon.com/snowfamily/home). 1. Choose the job to cancel. 1. Choose **Actions**. From the menu that appears, choose **Cancel job**. ![\[AWS Snow Family Management Console with job selected and Actions menu showing Cancel job.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/cancel-job-console.png) 1. The **Cancel job** window appears. To confirm cancelling the job, enter the **job name** and choose **Cancel job**. In the list of jobs, **Cancelled** appears in the **Status** column. ![\[Cancel job window.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/cancel-job-window-console.png) # Cloning a job to order a Snowball Edge in the AWS Snow Family Management Console When you first create an import job or a local compute and storage job, you might discover that you need more than one AWS Snowball Edge device. Because import jobs and local compute and storage jobs are associated with a single device, requiring more than one device means that you need to create more than one job. When creating additional jobs, you can go through the job creation wizard again in the console, or you can clone an existing job. **Note** Cloning a job is a shortcut available in the console to make creating additional jobs easier. If you're creating jobs with the job management API, you can simply run the job creation command again. Cloning a job means re-creating it exactly, except for an automatically modified name. Cloning is a simple process. **To clone a job in the console** 1. In the AWS Snow Family Management Console, choose your job from the table. 1. For **Actions**, choose **Clone job**. The **Create job** wizard opens to the last page, **Step 6: Review**. 1. Review the information and make any changes you want by choosing the appropriate **Edit** button. 1. To create your cloned job, choose **Create job**. Cloned jobs are named in the format ***Job Name*-clone-*number***. The number is automatically added to the job name and represents the number of times you've cloned this job after the first time you clone it. For example, **AprilFinanceReports-clone** represents the first cloned job of **AprilFinanceReports** job, and **DataCenterMigration-clone-42** represents the forty-second clone of the **DataCenterMigration** job. # Receiving the Snowball Edge When you receive the AWS Snowball Edge device, you might notice that it doesn't come in a box. The device is its own physically rugged shipping container. When the device first arrives, inspect it for damage or obvious tampering. If you notice anything that looks suspicious about the device, don't connect it to your internal network. Instead, contact [AWS Support](https://aws.amazon.com/premiumsupport/) and inform them of the issue so that a new device can be shipped to you. **Important** The AWS Snowball Edge device is the property of AWS. Tampering with an AWS Snowball Edge device is a violation of the AWS Acceptable Use Policy. For more information, see [AWS Acceptable Use Policy](http://aws.amazon.com/aup/). The device looks like the following image. ![\[Device with front and top covers closed. Case of device is gray and handles on top are orange. E Ink display visble on top.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/SnowballEdgeAppliance.png) If you're ready to connect the device to your internal network, see the next section. **Next:** [Connecting a Snowball Edge to your local network](getting-started.md#getting-started-connect) **Topics** ## Connecting a Snowball Edge to your local network Using the following procedure, you connect the AWS Snowball Edge device to your local network. The device doesn't need to be connected to the internet. The device has three doors: a front, a back, and a top. **To connect the device to your network** 1. Open the front and back doors, sliding them inside the device door slots. Doing this gives you access to the touch screen on the LCD display embedded in the front of the device, and the power and network ports in the back. **Note** Don't close the front and back doors while you're using the Snowball Edge device. The open doors allow air to cool the device. Closing the doors while using the device may cause the device to shut down to prevent overheating. 1. Open the top door and remove the provided power cable from the cable nook, and plug the device into power. 1. Choose one of your RJ45, SFP\$1, or QSFP\$1 network cables, and plug the device into your network. The network ports are on the back of the device. 1. Power on the AWS Snowball Edge device by pressing the power button above the LCD display. 1. When the device is ready, the LCD display shows a short video while the device is getting ready to start. After about 10 minutes, the device is ready to be unlocked. 1. (Optional) Change the default network settings through the LCD display by choosing **CONNECTION**. You can change your IP address to a different static address, which you provide by using the following procedure. To troubleshoot boot-up problems, see [Troubleshooting boot‐up problems with Snowball Edge](boot-troubleshoot.md). **To change the IP address of an AWS Snowball Edge device** 1. On the LCD display, choose **CONNECTION**. A screen appears that shows you the current network settings for the AWS Snowball Edge device. The IP address below the drop-down box is automatically updated to reflect the DHCP address that the AWS Snowball Edge device requested. 1. (Optional) Change the IP address to a static IP address. You can also keep it as is. The device is now connected to your network. **Important** To prevent corrupting your data, don't disconnect the AWS Snowball Edge device or change its connection settings while it's in use. **Next:** [Getting credentials to access a Snowball Edge](#get-credentials) ## Getting credentials to access a Snowball Edge Each job has a set of credentials that you must get from the AWS Snow Family Management Console or the job management API to authenticate your access to the Snowball Edge. These credentials are an encrypted manifest file and an associated unlock code. The manifest file contains important information about the job and permissions associated with it. **Note** You get your credentials after the device is in transit to you. You can see the status of your job in the AWS Snow Family Management Console. For more information, see [Statuses of Snowball Edge jobs](jobstatuses.md). **To get your credentials using the console** 1. Sign in to the AWS Management Console and open the [AWS Snow Family Management Console](https://console.aws.amazon.com/snowfamily/home). 1. On the console, search the table for the specific job to download the job manifest for, and then choose that job. 1. Expand that **Job status** pane, and choose **View job details**. 1. In the details pane that appears, expand **Credentials** and then do the following: + Make a note of the unlock code (including the hyphens), because you need to provide all 29 characters to unlock the device. + In the dialog box, choose **Download manifest**, and follow the instructions to download the job manifest file to your computer. The name of your manifest file includes your **Job ID**. **Note** We recommend that you don't save a copy of the unlock code in the same location in the computer as the manifest for that job. For more information, see [Best practices for using a Snowball Edge device](BestPractices.md). Now that you have your credentials, the next step is to download the Snowball Edge client, which is used to unlock the AWS Snowball Edge device. **Next:** [Downloading and installing the Snowball Edge Client](using-client-commands.md#download-the-client) # Unlocking the Snowball Edge This section describes unlocking the Snowball Edge device using the Snowball Edge Client. To unlock the device using AWS OpsHub, a graphical user interface (GUI) tool for Snowball Edge, see [Unlock a device](https://docs.aws.amazon.com/snowball/latest/developer-guide/connect-unlock-device.html). Before using a Snowball Edge device to transfer data or perform edge compute tasks, you need to unlock the device. When unlocking the device, you authenticate your ability to access it by providing two forms of credentials: a 29-digit unlock code and a manifest file. After you unlock the device, you can further configure the device, move data to or from it, set up and use Amazon EC2-compatible instances, and more. Before unlocking a device, the device must be plugged in to power and network, turned on, and an IP address assigned. See [Connecting a Snowball Edge to your local network](getting-started.md#getting-started-connect). You will need the following information about the Snowball Edge device: + Download and install the Snowball Edge client. For more information, see [Downloading and installing the Snowball Edge Client](using-client-commands.md#download-the-client). + Get the credentials from the AWS Snow Family Management Console. For one or more standalone devices, the unlock codes and manifest file for each Snowball Edge. For a cluster of Snowball Edge devices, the one unlock code and one manifest file for the cluster. For more information on downloading credentials, see [Getting credentials to access a Snowball Edge](getting-started.md#get-credentials). + Power on each device and connect it to your network. For more information, see [Connecting a Snowball Edge to your local network](getting-started.md#getting-started-connect). **To unlock a standalone device with the Snowball Edge Client** 1. Find the IP address for the AWS Snowball Edge device on the LCD display of the AWS Snowball Edge device, under the **Connections** tab. Make a note of that IP address. 1. Use the `unlock-device` command to authenticate your access to the Snowball Edge with the IP address of the Snowball Edge and your credentials, as follows. ``` snowballEdge unlock-device --endpoint https://ip-address-of-device --manifest-file /Path/to/manifest/file.bin --unlock-code 29-character-unlock-code ``` The device indicates it was unlocked successfully with the following message. ``` Your Snowball Edge device is unlocking. You may determine the unlock state of your device using the describe-device command. Your Snowball Edge device will be available for use when it is in the UNLOCKED state. ``` If the command returns `connection refused`, see [Troubleshooting unlocking a Snowball Edge](#troubleshooting-unlocking). **Example of `unlock-device` command** In this example, the IP address for the device is `192.0.2.0`, the manifest file name is `JID2EXAMPLE-0c40-49a7-9f53-916aEXAMPLE81-manifest.bin`, and the 29-character unlock code is `12345-abcde-12345-ABCDE-12345`. ``` snowballEdge unlock-device --endpoint https://192.0.2.0 --manifest-file /Downloads/JID2EXAMPLE-0c40-49a7-9f53-916aEXAMPLE81-manifest.bin / --unlock-code 12345-abcde-12345-ABCDE-12345 ``` **To unlock a cluster of Snowball Edge devices with the Snowball Edge client** 1. Find the IP address of each of the devices in the cluster on the LCD display of each AWS Snowball Edge device, under the **Connections** tab. Make a note of the IP addresses. 1. Use the `snowballEdge unlock-cluster` command to authenticate your access to the cluster of AWS Snowball Edge device devices with the IP address of one of the devices in the cluster, your credentials, and the IP addresses of all devices in the cluster as follows. ``` snowballEdge unlock-cluster --endpoint https://ip-address-of-device --manifest-file Path/to/manifest/file.bin --unlock-code 29-character-unlock-code --device-ip-addresses ip-address-of-cluster-device-1 ip-address-of-cluster-device-2 ip-address-of-cluster-device-3 ``` The cluster of devices indicates it was unlocked successfully with the following message. ``` Your Snowball Edge Cluster is unlocking. You may determine the unlock state of your cluster using the describe-cluster command. Your Snowball Edge Cluster will be available for use when your Snowball Edge devices are in the UNLOCKED state. ``` If the command returns `connection refused`, see [Troubleshooting unlocking a Snowball Edge](#troubleshooting-unlocking). **Example of `unlock-cluster` command** In this example for a cluster of five devices, the IP address for one of the devices in the cluster is `192.0.2.0`, the manifest file name is `JID2EXAMPLE-0c40-49a7-9f53-916aEXAMPLE81-manifest.bin`, and the 29-character unlock code is `12345-abcde-12345-ABCDE-12345`. ``` snowballEdge unlock-cluster --endpoint https://192.0.2.0 --manifest-file /Downloads/JID2EXAMPLE-0c40-49a7-9f53-916aEXAMPLE81-manifest.bin / --unlock-code 12345-abcde-12345-ABCDE-12345 --device-ip-addresses 192.0.2.0 192.0.2.1 192.0.2.2 192.0.2.3 192.0.2.4 ``` ## Troubleshooting unlocking a Snowball Edge If the `unlock-device` command returns `connection refused`, you may have mistyped the command syntax or the configuration of your computer or network may be preventing the command from reaching the Snow device. Take these actions to resolve the situation: 1. Ensure the command was entered correctly. 1. Use the LCD screen on the device to verify the IP addressed used in the command is correct. 1. Ensure that the path to the manifest file used in the command is correct, including the file name. 1. Use the [AWS Snowball Edge Management Console](https://console.aws.amazon.com/importexport/home?region=us-west-2) to verify the unlock code used in the command is correct. 1. Ensure the computer you are using is on the same network and subnet as the Snow device. 1. Ensure the computer you are using and the network are configured to allow access to the Snow device. Use the `ping` command for your operating system to determine if the computer can reach the Snow device over the network. Check the configurations of antivirus software, firewall configuration, virtual private network (VPN), or other configurations of your computer and network. Now you can begin using the Snowball Edge. **Next:** [Setting up local users on a Snowball Edge](getting-started.md#setup-local-iam) ## Setting up local users on a Snowball Edge Following are steps to set up a local administrator on your AWS Snowball Edge device. 1. **Retrieve your root user credentials** Use the `snowballEdge list-access-keys` and `snowballEdge get-secret-access-key` to get your local credentials. For more information, see [Getting credentials for a Snowball Edge](using-client-commands.md#client-credentials). 1. **Configure the root user credential using `aws configure`** Supply the `AWS Access Key ID`, `AWS Secret Access Key`, and `Default region name`. The region name must be `snow`. Optionally supply a `Default output format`. For more information about configuring the AWS CLI, see [Configuring the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html) in the *AWS Command Line Interface User Guide*. 1. **Create one or more local users on your device** Use the `create-user` command to add users to your device. ``` aws iam create-user --endpoint endpointIPaddress:6078 --region snow --user-name UserName --profile ProfileID ``` After you add users according to your business needs, you can store your AWS root credentials in a safe location and only use them for account and service management tasks. For more information about creating IAM users, see [Creating an IAM user in your AWS account](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_create.html) in the *IAM User Guide*. 1. **Create an access key for your user** **Warning** This scenario requires IAM users with programmatic access and long-term credentials, which presents a security risk. To help mitigate this risk, we recommend that you provide these users with only the permissions they require to perform the task and that you remove these users when they are no longer needed. Access keys can be updated if necessary. For more information, see [Update access keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/id-credentials-access-keys-update.html) in the *IAM User Guide*. Use the `create-access-key` command to create an access key for your user. ``` aws iam create-access-key --endpoint endpointIPaddress:6078 --region snow --user-name UserName --profile ProfileID ``` Save the access key information to a file and distribute to your users. 1. **Create an access policy** You might want different users to have different levels of access to functionality on your device. The following example creates a policy document named `s3-only-policy` and attaches it to a user. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "s3:*", "Resource": "*" } ] } ``` ------ ``` aws iam create-policy --endpoint endpointIPaddress:6078 --region snow --policy-name s3-only-policy --policy-document file://s3-only-policy --profile ProfileID ``` 1. **Attach the policy to your user** Use the `attach-user-policy` to attach the s3-only-policy to a user. ``` aws iam attach-user-policy --endpoint endpointIPaddress:6078 --region snow --user-name UserName --policy-arn arn:aws:iam::AccountID:policy/POLICYNAME --profile ProfileID ``` For more information about using IAM locally, see [Using IAM locally on a Snowball Edge](using-local-iam.md). # Rebooting the Snowball Edge device Before you reboot a Snowball Edge device, make sure that all data transfer to the device has stopped. **To reboot the device using the power button:** 1. When all communication with the device has ended, turn it off by pressing the power button located above the LCD screen. It takes about 20 seconds for the device to shut down. While the device is shutting down, the LCD screen displays a message indicating the device is shutting down. ![\[Shutdown message on LCD screen.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/shutdown-screen.png) **Note** If the LCD screen is displaying the shutdown message when the device is not actually being shut down, press the **Restart display** button on the screen to return the screen to normal operation. ![\[Shutdown message on LCD screen with Restart display button near bottom center.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/shutdown-screen-restart.png) 1. Press the power button. When the device is ready, the LCD display shows a short video while the device is getting ready to start. After about 10 minutes, the device is ready to be unlocked. 1. Unlock the device. See [Unlocking the Snowball Edge](unlockdevice.md). **To reboot the device using the Snowball Edge client:** 1. When all communication with the device has ended, use the `reboot-device` command to reboot it. When the device is ready, the LCD display shows a short video while the device is getting ready to start. After about 10 minutes, the device is ready to be unlocked. ``` snowballEdge reboot-device --profile profile-name ``` 1. Unlock the device. See [Unlocking the Snowball Edge](unlockdevice.md). # Powering off the Snowball Edge When you've finished transferring data on to the AWS Snowball Edge device, prepare it for its return trip to AWS. Before you continue, make sure that all data transfer to the device has stopped. If you were using the NFS interface to transfer data, disable it before you power off the device. For more information, see [Managing the NFS interface](https://docs.aws.amazon.com/snowball/latest/developer-guide/shared-using-nfs.html). When all communication with the device has ended, turn it off by pressing the power button located above the LCD screen. It takes about 20 seconds for the device to shut down. While the device is shutting down, the LCD screen displays a message indicating the device is shutting down. ![\[Shutdown message on LCD screen.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/shutdown-screen.png) **Note** If the LCD screen is displaying the shutdown message when the device is not actually being shut down, press the **Restart display** button on the screen to return the screen to normal operation. ![\[Shutdown message on LCD screen with Restart display button near bottom center.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/shutdown-screen-restart.png) After the device shuts down, the shipping information appears on the E Ink display. If return shipping information does not appear on the E Ink display, contact Support. **Next:** [Returning the Snowball Edge device](return-device.md) # Returning the Snowball Edge device After you are finished using the Snowball Edge and have powered it off, a shipping carrier will return it to AWS. The carrier automatically provides a tracking number for the shipment of the device. The tracking number appears in the AWS Snow Family Management Console. You can access the tracking number and a link to the carrier's tracking website by viewing the job's status details in the console. For more information, see [Return shipping for Snowball Edge devices](https://docs.aws.amazon.com/snowball/latest/developer-guide/mailing-storage.html). The carrier delivers the device to an AWS sorting facility and the device is forwarded to the AWS data center. At the data center, AWS will ensure the device has not been tampered with during shipping and that the device is healthy. If the device contains data to import into Amazon S3, AWS will begin importing it. Otherwise, the data on the device will be securely erased. You can track the status changes as AWS processes the device in the AWS Snow Family Management Console. You will receive Amazon SNS notifications of status changes if you selected that option when you created the job to order the device. For more information, see [Monitoring the Import Status](https://docs.aws.amazon.com/snowball/latest/developer-guide/monitor-status.html). The final status values include when the AWS Snowball Edge device has been received by AWS, when data import begins, and when the job is completed. **Note** If the device contains data you intended to import into Amazon S3 and you do not want the data on the device to be imported, contact Support to request to cancel the Snow job. If you cancel the job, we will skip the data transfer and securely erase the device following the established processes. We are not able to hold a device containing your data at our facilities due to our strict chain of custody and operating procedures. **To prepare an AWS Snowball Edge device for return shipping** 1. Power off the device. For more information, see [Powering off the Snowball Edge](turnitoff.md). 1. Disconnect any network cables connected to the device. 1. Disconnect the power cable. Stow it in the cable nook on top of the AWS Snowball Edge device. 1. Close the doors on the back, top, and front of the AWS Snowball Edge device. Press each door in until you hear and feel a click. **Next:** [Return shipping for Snowball Edge](mailing-storage.md) # Return shipping for Snowball Edge The AWS Snowball Edge device is shipped from and delivered to an AWS data center. The prepaid shipping information on the E Ink screen on the device includes the address to return the AWS Snowball Edge device. The shipping speed for the return matches the original shipping speed when you received the device. You can track status changes using the AWS Snow Family Management Console, and track the package's progress through your region's carrier. For more information about how to return your AWS Snowball Edge device, see [Shipping carriers for Snowball Edge](#carriers). **Important** Unless instructed otherwise by AWS, never affix a separate shipping label to the AWS Snowball Edge device. Always use the shipping information that's displayed on the AWS Snowball Edge device E Ink display. ## Shipping carriers for Snowball Edge When you create a job to order a Snowball Edge device, you provide the address to ship the AWS Snowball Edge device to. The carrier that supports your region handles the shipping of devices from AWS to you, and from you back to AWS. You can see the outbound shipping information when your job reaches the **Preparing shipment** status. There's a tracking number for every AWS Snowball Edge device that's shipped. You can find the tracking number and a link to the tracking website using the [AWS Snow Family Management Console](https://console.aws.amazon.com/snowfamily/home) job dashboard or the job management API. These carriers are supported for AWS Snowball Edge devices: + For India, Blue Dart is the carrier. + For Korea, Japan, Australia, and Indonesia, Kuehne \$1 Nagel, is the carrier. + For China and Hong Kong, S.F. Express is the carrier. + For all other regions, [UPS](https://www.ups.com/) is the carrier. **Topics** + [ ### Snowball Edge UPS pickups in the EU, US, UK, South Africa, and Canada ](#standard-pickup) + [ ### Snowball Edge pickups in UK ](#uk) + [ ### Snowball Edge pickups in Brazil ](#Brazil-pickup) + [ ### Snowball Edge pickups in Australia ](#Australia-pickup) + [ ### Snowball Edge pickups in India ](#India-pickup) + [ ### Snowball Edge pickups in Korea ](#Korea-pickup) + [ ### Snowball Edge pickups in Hong Kong ](#hkg-pickup) + [ ### Snowball Edge pickups in Singapore, Japan, and Indonesia ](#Indonesia-pickup) + [ ### Snowball Edge receiving and returning in Dubai, United Arab Emirates ](#dbx-pickup) + [ ### Shipping speeds for Snowball Edge ](#shippingspeeds) ### Snowball Edge UPS pickups in the EU, US, UK, South Africa, and Canada UPS can often pick up your device in the EU, US, UK, South Africa, and Canada. Here are some helpful guidelines: + Schedule a pickup with UPS directly, or take the AWS Snowball Edge device to a UPS package drop-off facility to be shipped to AWS. + The prepaid UPS shipping label on the E Ink display contains the return address for the AWS Snowball Edge device. + The AWS Snowball Edge device is delivered to an AWS sorting facility and forwarded to a AWS data center. UPS provides you with a tracking number. **Important** Unless instructed otherwise by AWS, never affix a separate shipping label to the AWS Snowball Edge device. Always use the shipping information that is displayed on the device's E Ink display. UPS ships Snowball Edge devices to the following EU member countries: Austria, Belgium, Bulgaria, Croatia, Republic of Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Italy, Ireland, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, and Sweden. **Note** Orders between the United Kingdom and European Union countries are now considered to be international, and require approval through a special international process. If you need to ship your device between the UK and the EU, email us at snowball-shipping@amazon.com to request a commercial invoice prior to arranging pick up or drop off with UPS. UPS services for Snowball Edge of products are domestic only within a country. ### Snowball Edge pickups in UK In the United Kingdom, keep the following information in mind for UPS to pick up a Snowball Edge: + You arrange for UPS to pick up the AWS Snowball Edge device by scheduling a pickup with UPS directly, or take the AWS Snowball Edge device to a UPS package drop-off facility to be shipped to AWS. + The prepaid UPS shipping label on the E Ink display contains the correct address to return the AWS Snowball Edge device. + The AWS Snowball Edge device is delivered to an AWS sorting facility and forwarded to the AWS data center. UPS automatically reports back a tracking number for your job. **Important** Unless personally instructed otherwise by AWS, never affix a separate shipping label to the AWS Snowball Edge device. Always use the shipping information that is displayed on the device's E Ink display. UPS services for Snowball Edge of products is domestic only within a country. **Note** Since January 2021, UK is no longer a part of EU. Orders between UK and other EU countries are international orders, a non-general Availability process only approved through a special international process. If a customer has been approved and is returning a device from an EU-country back to LHR or from UK back to an EU-country, they must first request a return to snowball-shipping@amazon.com so a Commercial Invoice can be provided prior to arranging pick up/drop off with UPS. ### Snowball Edge pickups in Brazil Here are some guidelines for UPS to pick up a Snowball Edge device in Brazil: + When you're ready to return a Snowball Edge device, call 0800-770-9035 to schedule a pickup with UPS. + Snowball Edge Edge is available domestically within Brazil, which includes 26 states and the Distrito Federal. + If you have a Cadastro Nacional de Pessoa Juridica (CNPJ) tax ID, be sure that you know this ID before you create your job. + You should issue the appropriate document to return the Snowball Edge device. Confirm with your tax department which of the following documents is required in your state, according to your Imposto sobre Circulação de Mercadorias e Serviços (ICMS) registration: + **Within São Paulo –** A non-ICMS declaration and an Electronic Tax Invoice (NF-e) are usually required. + **Outside São Paulo** – The following are usually required: + A non-ICMS declaration + A nota fiscal avulsa + An Electronic Tax Invoice (NF-e) **Note** For non-ICMS taxpayer declaration, we recommend that you generate four copies of the declaration: one for your records, and the other three for transport. ### Snowball Edge pickups in Australia In Australia, if you're shipping an AWS Snowball Edge device back to AWS, place the return transport label (found in the pouch containing these instructions) over the E Ink label on the Snow device. ![\[Transport Label to Consignee\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/PlaceTransportLabel2Consignee.png) **Note** If you didn't receive a return label with your device, email knau.snowball\$1return@kuehne-nagel.com with your device serial number or your reference number. To arrange the return of the Snowball Edge, scan the QR code on the return instructions with your mobile device. On your device, a hyperlink to an email message appears. The message contains information such as email address, subject, and control number or consignment number. Fill in the pickup date, name, and contact details, or provide a new pickup address if there are any changes. ![\[Example QR Code\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/AUS_QR.png) ### Snowball Edge pickups in India In India, Blue Dart picks up the Snowballdevice. When you are ready to return your Snowball device, turn it off and prepare it for return shipping. To schedule pickup, email [snowball-pickup@amazon.com](mailto:snowball-pickup@amazon.com) with **Snowball Pickup Request** in the subject line. In the email, include the following information: + **Job ID** – The job ID associated with the Snowball that you want returned to AWS. + **AWS account ID** – The ID for the AWS account that created the job. + **Date Requested** – The day you would like the Snowball device picked up. + **Earliest Pickup Time** (your local time) – The earliest time of day that you want the Snowball picked up. + **Latest Pickup Time** (your local time) – The latest time of day that you want the Snowball picked up. + **Special Instructions** (optional) – Any special instructions for picking up the Snowball, including contact details for coordinating pickup. The Snowball Edge team arranges the pickup with Blue Dart and sends you a confirmation email. Blue Dart provides you with a paper shipping label and picks up the Snowball Edge device. **Important** When using a Snowball in India, remember to file all relevant tax paperwork with your state. AWS requires at least 72 hours notice to process return shipping requests in India. AWS cannot reimburse any per-day fees for return shipment requests recieved less than 72 hours in advance. ### Snowball Edge pickups in Korea In Korea, Kuehne \$1 Nagel handles your pickups. When you are ready to return your device, send an email to snowball-shipping@amazon.com with *Snowball Pickup Request* in the subject line so we can schedule the pickup for you. In the body of the email, include the following information: + **Job ID** – The job ID associated with the Snowball that you want returned to AWS. + **Pickup Address** -The address where the device is picked up. + **Pickup Date** - The earliest day you would like the device picked up. + **Point of contact details** – The name, email address, and local phone number that Kuehne \$1 Nagel can use to get in touch with you if needed. Soon, you will get a follow-up email from the Snowball team with information regarding the pickup at the address your device you provided. Power cycle the device and be ready for pickup usually between 1300 and 1500. ### Snowball Edge pickups in Hong Kong In Hong Kong, S.F. Express handles your pickups. When you are ready to return your device, send an email to snowball-shipping-ap-east-1@amazon.com with *Snowball Pickup Request* in the subject line so we can schedule the pickup for you. In the body of the email, include the following information: + Job ID + AWS account ID + Contact name + Contact phone number + Contact email address + The day you want the device(s) picked up + Earliest pickup time + Latest pickup time + Pickup address Once you arrange a pickup date with S.F. Express, it can't be rescheduled. The device will be delivered to AWS by S.F. Express. The S.F. Express tracking number for the return shipment tells you when it was delivered. ### Snowball Edge pickups in Singapore, Japan, and Indonesia In Singapore, Japan, and Indonesia, when you are ready to return your device, scan the QR code displayed on the return E Ink label with your mobile phone. This will take you directly onto an email template. Please fill in pick up date/time and contact details. ![\[Snowball Pickup Request\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/SnowballPickupRequest.png) **Note** If your pickup address is different from the address where the device was delivered, please add the new address in the email body so the appointed carrier can be informed. **Note** In Japan, the shipping company charges a shipping fee of \$1120.00. The description of the fee indicates Snowball Edge, but the fee applies to shipping all Snowball Edge. ### Snowball Edge receiving and returning in Dubai, United Arab Emirates Here are some guidelines that you must follow when receiving or returning an AWS Snowball Edge device in Dubai. #### Receiving a Snowball Edge device When receiving a Snowball Edge device in a free zone, when you are notified by UPS that the package is ready for delivery, apply for, obtain, and share the gate pass for your free zone. If you are in a free zone or in the Mainland, sign the proof of delivery (POD) when you receive the device. #### Returning a Snowball Edge device When returning a Snowball Edge device, arrange for UPS to pick up the device by scheduling a pickup with UPS directly on 600 544 743 or via the UPS website. Ensure the return shipping information is displayed on the E Ink display before the device is picked up. See [Returning the Snowball Edge device](return-device.md). In a free zone, when you are notified that a UPS driver is assigned for pickup of the device, apply for, obtain, and share the Gate Pass for your free zone. The prepaid UPS shipping information on the E Ink display contains the correct address to return the Snowball Edge device. The Snowball Edge device is delivered to an AWS sorting facility and forwarded to the AWS data center. UPS automatically provides a tracking number for your job. **Important** Unless personally instructed otherwise by AWS, never affix a separate shipping label to the Snowball Edge device. Always use the shipping label that is displayed on the device's E Ink display. UPS services for Snowball Edge of products is domestic only within a country. ### Shipping speeds for Snowball Edge Each country has different shipping speeds available. These shipping speeds are based on the country in which you're shipping an AWS Snowball Edge device. Shipping speeds are as follows: + **Australia, Japan, Singapore, Indonesia, S.Korea ** – When shipping within these countries, you have access to the standard shipping speed of 1 – 3 days. + **Brazil** – When shipping within Brazil, you have access to UPS Domestic Express Saver shipping, which delivers within two business days during commercial hours. Shipping speeds might be affected by interstate border delays. + **European Union (EU)** – When shipping to any of the countries within the EU, you have access to express shipping. Typically, AWS Snowball Edge devices shipped express are delivered in about a day. In addition, most countries in the EU have access to standard shipping, which typically takes less than a week, one way. + **Hong Kong** – When shipping within Hong Kong, you have access to express shipping. + **India** – When shipping within India, Snowball Edge devices are sent out within 7 working days of AWS receiving all related tax documents. + **Dubai, United Arab Emirates** - You have access to Courier Express Saver shipping. + **United Kingdom (UK)** – When shipping within the UK, you have access to express shipping. Typically, Snowball Edge devices shipped express are delivered in about a day. In addition, you have access to standard shipping, which typically takes less than a week, one way. + **United States of America (US) and Canada** – When shipping in the US or in Canada, you have access to one-day shipping and two-day shipping. # Monitoring the import status from the Snowball Edge To monitor the status of your import job in the console, sign in to the [AWS Snow Family Management Console](https://console.aws.amazon.com/snowfamily/home) in the AWS Region where the job was created. Choose the job you want to track from the table, or search for it by your chosen parameters in the search bar above the table. After you select the job, detailed information appears for that job within the table, including a bar that shows real-time status of your job. **Note** If we are unable to import data to our data centers from the Snow device due to any issue with access permissions you have configured, we will attempt to notify you and you will have 30 days from the date we provide the notification to resolve the issue. If the issue is not resolved, we may cancel your Snowball Edge job and delete data from the device. After your device arrives at AWS, your job status changes from **In transit to AWS** to **At AWS**. On average, it takes a day for your data import into Amazon S3 to begin. When it does, the status of your job changes to **Importing**. It will take approximately the same amount of time for AWS to import your data from the Snowball Edge as it did for you to move it to the Snowball Edge. After your data is imported, the job status changes to **Completed** status. Now your first data import job into Amazon S3 using AWS Snowball Edge is complete. You can get a report about the data transfer from the console. To access this report from the console, select the job from the table, and expand it to reveal the job's detailed information. Choose **Get report** to download your job completion report as a PDF file. For more information, see [Getting your data transfer job completion report and logs](report.md). **Next:** [Getting your data transfer job completion report and logs](report.md) # Getting your data transfer job completion report and logs When you use a Snowball Edge to import data to or export data from Amazon S3, you get a downloadable PDF job report. For import jobs, this report becomes available at the very end of the import process. For export jobs, your job report typically becomes available for you while the AWS Snowball Edge device for your job part is being delivered to you. Job completion reports are not available for local compute and storage only jobs. The job report provides you insight into the state of your Amazon S3 data transfer. The report includes details about your job or job part for your records. The job report also includes a table that provides a high-level overview of the total number of objects and bytes transferred between the device and Amazon S3. For deeper visibility into the status of your transferred objects, you can look at the two associated logs: a success log and a failure log. The logs are saved in comma-separated value (CSV) format, and the name of each log includes the ID of the job or job part that the log describes. You can download the report and the logs from the AWS Snow Family Management Console. Below is a sample report. ![\[Sample job completion report including job ID, job type, device type, job state, and data transfer details.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/job-complete-report.png) **To get your job report and logs** 1. Sign in to the AWS Management Console and open the [AWS Snow Family Management Console](https://console.aws.amazon.com/snowfamily/home). 1. Choose your job or job part from the table and expand the status pane. Three options appear for getting your job report and logs: **Get job report**, **Download success log**, and **Download failure log**. 1. Choose the log you want to download. The following list describes the possible values for the report: + **Completed** – The transfer was completed successfully. You can find more detailed information in the success log. + **Completed with errors** – Some or all of your data was not transferred. You can find more detailed information in the failure log.