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/). # Using AWS OpsHub to Manage Devices The Snowball Edge now offer a user-friendly tool, AWS OpsHub, that you can use to manage your devices and local AWS services. You use AWS OpsHub on a client computer to perform tasks such as unlocking and configuring single or clustered devices, transferring files, and launching and managing instances running on Snowball Edge. You can use AWS OpsHub to manage both the Storage Optimized and Compute Optimized Snow device types. The AWS OpsHub application is available at no additional cost to you. AWS OpsHub takes all the existing operations available in the Snowball API and presents them as a graphical user interface. This interface helps you quickly migrate data to the AWS Cloud and deploy edge computing applications on Snowball Edge. AWS OpsHub provides a unified view of the AWS services that are running on Snowball Edge and automates operational tasks through AWS Systems Manager. With AWS OpsHub, users with different levels of technical expertise can manage a large number of Snowball Edge. With a few clicks, you can unlock devices, transfer files, manage Amazon EC2-compatible instances, and monitor device metrics. When your Snow device arrives at your site, you download, install, and launch the AWS OpsHub application on a client machine, such as a laptop. After installation, you can unlock the device and start managing it and using supported AWS services locally. AWS OpsHub provides a dashboard that summarizes key metrics such as storage capacity and active instances on your device. It also provides a selection of AWS services that are supported on the Snowball Edge. Within minutes, you can begin transferring files to the device. This video provides an overview of AWS OpsHub functionality. [![AWS Videos](http://img.youtube.com/vi/https://www.youtube.com/embed/0Q7s7JiBCf0/0.jpg)](http://www.youtube.com/watch?v=https://www.youtube.com/embed/0Q7s7JiBCf0) **Topics** + [Downloading AWS OpsHub for Snowball Edge](download-OpsHub-for-snow-family.md) + [Unlocking a Snowball Edge device with AWS OpsHub](connect-unlock-device.md) + [Verifying the PGP signature of AWS OpsHub (optional)](verify-signature.md) + [Managing AWS services on the Snowball Edge with AWS OpsHub](manage-services.md) + [Rebooting the device with AWS OpsHub](reboot-device.md) + [Managing profiles with AWS OpsHub](#manage-profile) + [Shutting down the device with AWS OpsHub](shutdown-device.md) + [Editing the device alias with AWS OpsHub](edit-device-alias.md) + [Managing public key certificates using OpsHub](snowball-edge-certificates-opshub.md) + [Getting updates for the Snowball Edge](get-updates.md) + [Updating the AWS OpsHub application](update-opshub.md) + [Automating your management tasks with AWS OpsHub](automate-task.md) + [Setting the NTP time servers for the device with AWS OpsHub](setting-ntp.md) # Downloading AWS OpsHub for Snowball Edge **To download AWS OpsHub** 1. Navigate to the [AWS Snowball resources website](https://aws.amazon.com/snowball/resources/). ![\[AWS Snowball resources website showing AWS OpsHub downloads.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/snow-resources-webpage.png) 1. In the **AWS OpsHub** section, choose **Download** for your operating system, and follow the installation steps. # Unlocking a Snowball Edge device with AWS OpsHub When your device arrives at your site, the first step is to connect and unlock it. AWS OpsHub lets you sign in, unlock, and manage devices using the following methods: + **Locally** – To sign in to a device locally, you must power on the device and connect it to your local network. Then provide an unlock code and a manifest file. + **Remotely** – To sign in to a device remotely, you must power on the device and make sure that it can connect to `device-order-region.amazonaws.com` through your network. Then provide the AWS Identity and Access Management (IAM) credentials (access key and secret key) for the AWS account that is linked to your device. For information on enabling remote management and creating an associated account, see [Activating Snowball Edge Device Management on a Snowball Edge](aws-sdm.md#enable-sdm). **Topics** + [Unlocking a Snowball Edge device locally with AWS OpsHub](#connect-unlock-local) + [Unlocking a Snowball Edge device remotely with AWS OpsHub](#connect-unlock-remote) ## Unlocking a Snowball Edge device locally with AWS OpsHub This video shows how to unlock a Snowball Edge device locally using AWS OpsHub. [![AWS Videos](http://img.youtube.com/vi/https://www.youtube.com/embed/StMa2A7X2yA?start=36&end=70/0.jpg)](http://www.youtube.com/watch?v=https://www.youtube.com/embed/StMa2A7X2yA?start=36&end=70) **To connect and unlock your device locally** 1. Open the flap on your device, locate the power cord, and connect it to a power source. 1. Connect the device to your network using a network cable (typically an Ethernet RJ45 cable), then open the front panel and power on the device. 1. Open the AWS OpsHub application. If you are a first-time user, you are prompted to choose a language. Then choose **Next**. 1. On the **Get started with OpsHub** page, choose **Sign in to local devices**, and then choose **Sign in**. ![\[Get started with AWS OpsHub page\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-unlock-local-console.png) 1. On the **Sign in to local devices** page, choose your Snowball Edge type, and then choose **Sign in**. 1. On the **Sign in** page, enter the **Device IP address** and **Unlock code**. To select the device manifest, choose **Choose file**, and then choose **Sign in**. ![\[AWS OpsHub sign in page\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-sign-in-local-console.png) 1. (Optional) Save your device's credentials as a *profile*. Name the profile and choose **Save profile name**. For more information about profiles, see [Managing profiles with AWS OpsHub](aws-opshub.md#manage-profile). 1. On the **Local devices** tab, choose a device to see its details, such as the network interfaces and AWS services that are running on the device. You can also see details for clusters from this tab, or manage your devices just as you do with the AWS Command Line Interface (AWS CLI). For more information, see [Managing AWS services on the Snowball Edge with AWS OpsHub](manage-services.md). For devices that have AWS Snowball Edge Device Management installed, you can choose **Enable remote management** to turn on the feature. For more information, see [Using AWS Snowball Edge Device Management to manage Snowball Edge](aws-sdm.md). ## Unlocking a Snowball Edge device remotely with AWS OpsHub To unlock a Snowball Edge not **To connect and unlock your device remotely** 1. Open the flap on your device, locate the power cord, and connect it to a power source. 1. Connect the device to your network using an Ethernet cable (typically an RJ45 cable), then open the front panel and power on the device. **Note** To be unlocked remotely, your device must be able to connect to `device-order-region.amazonaws.com`. 1. Open the AWS OpsHub application. If you are a first-time user, you are prompted to choose a language. Then choose **Next**. 1. On the **Get started with OpsHub** page, choose **Sign into remote devices**, and then choose **Sign in**. ![\[Get started with AWS OpsHub page with Sign into remote devices chosen.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-unlock-remote-console.png) 1. On the **Sign in to remote devices** page, enter the AWS Identity and Access Management (IAM) credentials (access key and secret key) for the AWS account that is linked to your device, and then choose **Sign in**. ![\[Sign in to remote devices page\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-remote-unlock-console.png) 1. At the top of the **Remote devices** tab, choose the region of the Snow device to unlock remotely. ![\[Remote devices tab with region menu highlighted.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-remote-region-console.png) 1. On the **Remote devices** tab, choose your device to see its details, such as its state and network interfaces. Then choose **Unlock** to unlock the device. ![\[Device information details\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-remote-console.png) From the remote device's details page, you can also reboot your devices and manage them just as you do with the AWS Command Line Interface (AWS CLI). To view remote devices in different AWS Regions, choose the current Region on the navigation bar, and then choose the Region that you want to view. For more information, see [Managing AWS services on the Snowball Edge with AWS OpsHub](manage-services.md). # Verifying the PGP signature of AWS OpsHub (optional) The AWS OpsHub application installer package for the Linux operating system are cryptographically signed. You can use a public key to verify that the installer package is original and unmodified. If the files are damaged or altered, the verification fails. You can verify the signature of the installer package using GNU Privacy Guard (GPG). This verification is optional. If you choose to verify the signature of the application, you can do it at any time. You can download the SIGNATURE file for the Linux operating system installer from [AWS Snowball Edge Resources](https://aws.amazon.com/snowcone/resources/) or [Snowball Edge Resources](https://aws.amazon.com/snowball/resources/). **To verify the AWS OpsHub install package on for the Linux operating system** 1. Copy the following public key, save it to a file, and name the file. For example, `opshub-public-key.pgp`. ``` -----BEGIN PGP PUBLIC KEY BLOCK----- xsFNBF/hGf8BEAC9HCDV8uljDX02Jxspi6kmPu4xqf4ZZLQsSqJcHU61oL/c /zAN+mUqJT9aJ1rr0QFGVD1bMogecUPflTWlDkEEpG8ZbX5P8vR+EElO/rW/ WtqizSudy6qy59ZRK+YVSDx7DZyuJmIO7j00UADCL+95ZQN9vqwHNjBHsgfQ l/1Tqhy81ozTZXcI/+u+99YLaugJIP6ZYIeDfpxnghqyVtaappBFTAyfG67Y N/5mea1VqJzd8liFpIFQnl+X7U2x6emDbM01yJWV3aMmPwhtQ7iBdt5a4x82 EF5bZJ8HSRMvANDILD/9VTN8VfUQGKFjFY2GdX9ERwvfTb47bbv9Z28Vl284 4lw2w1Bl007FoO2v/Y0ukrN3VHCpmJQS1IiqZbYRa0DVK6UR5QNvUlj5fwWs 4qW9UDPhT/HDuaMrMFCejEn/7wvRUrGVtzCT9F56Al/dwRSxBejQQEb1AC8j uuyi7gJaPdyNntROEFTD7iO2L6X2jB4YLfvGxP7Xeq1Y37t8NKF8CYTpOry/ Wvw0iKZFbo4AkiI0aLyBCk9HBXhUKa9x06gOnhh1UFQrPGrk60RPQKqL76HA E2ewzGDa90wlRBUAt2nRQpyNYjoASBvz/cAr3e0nuWsIzopZIenrxI5ffcjY f6UWA/OK3ITHtYHewVhseDyEqTQ4MUIWQS4NAwARAQABzTlBV1MgT3BzSHVi IGZvciBTbm93IEZhbWlseSA8YXdzLW9wc2h1Yi1zaWduZXJAYW1hem9uLmNv bT7CwY0EEAEIACAFAl/hGf8GCwkHCAMCBBUICgIEFgIBAAIZAQIbAwIeAQAh CRAhgc9adPNF8RYhBDcvpelIaY930bOvqiGBz1p080XxGbcP+gPZX7LzKc1Y w9CT3UHgkAIawOSXYktujzoYVxAz8/j3jEkCY0dKnfyqvWZDiJAXnzmxWWbg cxg1g0GXNXCM4lAd68CmbAOLoLTaWSQX30ZbswzhbtX2ADAlopV8RLBik7fm bS9FyuubDRhfYRQq0fpjUGXFiEgwg6aMFxsrGLlv4QD7t+6ftFIe/mxLbjR4 iMgtr8FIPXbgn05YYY/LeF4NIgX4iLEqRbAnfWjPzqQ1spFWAotIzDmZqby+ WdWThrH4K1rwtYM8sDhqRnMnqJrGFZzk7aDhVPwF+FOVMmPeEN5JRazEeUrl VZaSw6mu0n4FMGSXuwGgdvmkqnMe6I5/xLdU4IOPNhp0UmakDWOq/a1dREDE ZLMQDMINphmeQno4inGmwbRo63gitD4ZNR5sWwfuwty25lo8Ekv7jkkp3mSv pdxn5tptttnPaSPcSIX/4EDl19Tu0i7aup+v30t7eikYDSZG6g9+jHB3Va9e /VWShFSgy8Jm2+qq/ujUQDAGTCfSuY9jg1ITsog6ayEZa/2upDJ1m+4OHK4p 8DrEzP/3jTahT8q5ofFWSRDL17d3lTSU+JBmPE3mz311FNXgiO8w+taY320z +irHtb3iSiiukbjS8s0maVgzszRqS9mhaEn4LL0zoqrUicmXgTyFB7n2LuYv O7vxMO5xxhGQwsF2BBABCAAJBQJf4RoCAhsDACEJEBFZvzT/tDi5FiEEi+O9 V+UAYN9Gnw36EVm/NP+0OLnnEQ/+J4C0Mn8j0AebXrwBiFs83sQo2q+WHL1S MRc1g5gRFDXs6h1Gv+TGXRen7j1oeaddWvgOtUBxqmCOjr+8AKH0OtiBWSuO lsS8JU5rindEsKUrKTwcG2wyZFoe1zlE8xPkLRSRN5ZbbgKsTz16l1HgCCId Do+WJdDkWGWxmtDvzjM32EI/PVBd108ga9aPwXdhLwOdKAjZ4JrJXLUQJjRI IVDSyMObEHOUM6a/+mWNZazNfo0LsGWqGVa6Xn5WJWlwR1S78vPNfO3BQYuO YRjaVQR+kPtB9aSAZNi5sWfk6NrRNd1Q78d067uhhejsjRt7Mja2fEL4Kb1X nK4U/ps7XlO3o/VjblneZOhJK6kAKU172tnPJTJ31JbOxX73wsMWDYZRZVcK 9X9+GFrpwhKHWKKPjpMOt/FRxNepvqRl72TkgBPqGH2TMOFdB1f/uQprvqge PBbS0JrmBIH9/anIqgtMdtcNQB/0erLdCDqI5afOuD1OLcLwdJwG9/bSrfwT TVEE3WbXmJ8pZgMzlHUiZE6V2DSadV/YItk50IOjjrOVHOHvlFMwGCEAIFzf 9P/pNi8hpEmlRphRiOVVcdQ30bH0M0gPHu5V9flIhyCL1zU3LjYTHkq0yJD5 YDA1xO1MYq3DcSM513OVBbLmuVS2GpcsTCYqlgQA6h/zzMwz+/7OwU0EX+EZ /wEQAOAY8ULmcJIQWIr14V0jylpJeD3qwj7wd+QsBzJ+mOpOB/3ZFAhQiNOl 9yCDlHeiZeAmWYX9OIXrNiIdcHy+WTAp4G+NaMpqE52qhbDjz+IbvLpl1yDH bYEHPjnTHXEy2lbvKAJOKkw/2RcQOi4dodGnq5icyYj+9gcuHvnVwbrQ96Ia 0D7c+b5T+bzFqk90nIcztrMRuhDLJnJpi7OjpvQwfq/TkkZA+mzupxfSkq/Y N9qXNEToT/VI2gn/LS0X4Ar1l2KxBjzNEsQkwGSiWSYtMA5J+Tj5ED0uZ/qe omNblAlD4bm7Na8NAoLxCtAiDq/f3To9Xb18lHsndOmfLCb/BVgP4edQKTIi C/OZHy9QJlfmN0aq7JVLQAuvQNEL88RKW6YZBqkPd3P6zdc7sWDLTMXMOd3I e6NUvU7pW0E9NyRfUF+oT4s9wAJhAodinAi8Zi9rEfhK1VCJ76j7bcQqYZe0 jXD3IJ7T+X2XA8M/BmypwMW0Soljzhwh044RAasr/fAzpKNPB318JwcQunIz u2N3CeJ+zrsomjcPxzehwsSVq1lzaL2ureJBLOKkBgYxUJYXpbS01ax1TsFG 09ldANOs9Ej8CND37GsNnuygjOgWXbX6MNgbvPs3H3zi/AbMunQ1VBlw07JX zdM1hBQZh6w+NeiEsK1T6wHi7IhxABEBAAHCwXYEGAEIAAkFAl/hGf8CGwwA IQkQIYHPWnTzRfEWIQQ3L6XpSGmPd9Gzr6ohgc9adPNF8TMBD/9TbU/+PVbF ywKvwi3GLOlpY7BXn8lQaHyunMGuavmO8OfaRROynkH0ZqLHCp6bIajFOfvF b7c0Jamzx8Hg+SIdl6yRpRY+fA4RQ6PNnnmT93ZgWW3EbjPyJGlm0/rt03SR +0yn4/ldlg2KfBX4pqMoPCMKUdWxGrmDETXsGihwZ0gmCZqXe8lK122PYkSN JQQ+LlfjKvCaxfPKEjXYTbIbfyyhCR6NzAOVZxCrzSz2xDrYWp/V002Klxda 0ix6r2aEHf+xYEUhOaBt8OHY5nXTuRReCVU789MUVtCMqD2u6amdo4BR0kWA QNg4yavKwV+LVtyYh2Iju9VSyv4xL1Q4xKHvcAUrSH73bHG7b7jkUJckD0f4 twhjJk/Lfwe6RdnVo2WoeTvE93w+NAq2FXmvbiG7eltl0XfQecvQU3QNbRvH U8B96W0w8UXJdvTKg4f0NbjSw7iJ3x5naixQ+rA8hLV8xOgn2LX6wvxT/SEu mn20KX+fPtJELK7v/NheFLX1jsKLXYo4jHrkfIXNsNUhg/x2E71kAjbeT3s+ t9kCtxt2iXDDZvpIbmGO4QkvLFvoROaSmN6+8fupe3e+e2yN0e6xGTuE60gX I2+X1p1g9IduDYTpoI2OXleHyyMqGEeIb4gOiiSloTp5oi3EuAYRGflXuqAT VA19bKnpkBsJ0A== =tD2T -----END PGP PUBLIC KEY BLOCK----- ``` 1. Use a cryptographic software suite such as GNU Privacy Guard to import the public key into your keyring, and note the returned key value. ``` gpg --import opshub-public-key.pgp ``` **Example output of command** ``` gpg: key 1655BBDE2B770256: public key "AWS OpsHub for Snowball Edge " imported gpg: Total number processed: 1 gpg: imported: 1 ``` 1. Verify the fingerprint. Be sure to replace *`key-value`* with the value from the preceding step. We recommend that you use GPG to verify the fingerprint. ``` gpg --fingerprint key-value ``` This command returns output similar to the following. ``` pub rsa4096 2020-12-21 [SC] 372F A5E9 4869 8F77 D1B3 AFAA 2181 CF5A 74F3 45F1 uid [ unknown] AWS OpsHub for Snowball Edge sub rsa4096 2020-12-21 [E] ``` The fingerprint should match the following: `372F A5E9 4869 8F77 D1B3 AFAA 2181 CF5A 74F3 45F1` If the fingerprint doesn't match, don't install the AWS OpsHub application. Contact Support. 1. Verify the installer package, and download the SIGNATURE file according to your instance's architecture and operating system if you haven't already done so. 1. Verify the installer package signature. Be sure to replace `signature-filename` and `OpsHub-download-filename` with the values that you specified when downloading the SIGNATURE file and AWS OpsHub application. ------ #### [ GPG ] ``` gpg --verify signature-filename OpsHub-download-filename ``` ------ This command returns output similar to the following. ------ #### [ GPG ] ``` gpg: Signature made Mon Dec 21 13:44:47 2020 PST gpg: using RSA key 1655BBDE2B770256 gpg: Good signature from "AWS OpsHub for Snowball Edge " [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 9C93 4C3B 61F8 C434 9F94 5CA0 1655 BBDE 2B77 0256 ``` ------ When using GPG, if the output includes the phrase `BAD signature`, check whether you performed the procedure correctly. If you continue to get this response, contact Support and don't install the agent. The warning message about the trust doesn't mean that the signature is not valid, only that you have not verified the public key. A key is trusted only if you or someone who you trust has signed it. # Managing AWS services on the Snowball Edge with AWS OpsHub With AWS OpsHub, you can use and manage AWS services on your Snowball Edge. Currently, AWS OpsHub supports the following resources: + Amazon Elastic Compute Cloud (Amazon EC2) instances – Use Amazon EC2-compatible instances to run software installed on a virtual server without sending it to the AWS Cloud for processing. + Network File System (NFS) – Use file shares to move data to your device. You can ship the device to AWS to transfer your data to the AWS Cloud, or use DataSync to transfer to other AWS Cloud locations. + Amazon S3 compatible storage on Snowball Edge – Delivers secure object storage with increased resiliency, scale, and an expanded Amazon S3 API feature-set to rugged, mobile edge, and disconnected environments. Using Amazon S3 compatible storage on Snowball Edge, you can store data and run highly available applications on Snowball Edge for edge computing. ![\[AWS OpsHub dashboard\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/cone-opshub-dashboard.png) **Topics** + [Launching an Amazon EC2-compatible instance on a Snowball Edge with AWS OpsHub](launch-instance.md) + [Stopping an Amazon EC2-compatible instance on a Snowball Edge with AWS OpsHub](stop-instance.md) + [Starting an Amazon EC2-compatible instance on an Snowball Edge with AWS OpsHub](start-instance.md) + [Working with key pairs for EC2-compatible instances in AWS OpsHub](working-with-key-pair.md) + [Terminating an Amazon EC2-compatible instance with AWS OpsHub](terminate-instance.md) + [Using storage volumes locally on Snowball Edge with AWS OpsHub](manage-ebs-volumes.md) + [Importing an image as an Amazon EC2-compatible AMI with AWS OpsHub](ec2-ami-import.md) + [Deleting a snapshot from a Snowball Edge with AWS OpsHub](delete-snapshot.md) + [Deregistering an AMI on a Snowball Edge with AWS OpsHub](deregister-ami.md) + [Managing an Amazon EC2 cluster on Snowball Edge with AWS OpsHub](manage-clusters.md) + [Set up Amazon S3 compatible storage on Snowball Edge with AWS OpsHub](s3-edge-snow-opshub.md) + [Managing Amazon S3 adapter storage with AWS OpsHub](manage-s3.md) + [Managing the NFS interface with AWS OpsHub](manage-nfs.md) # Launching an Amazon EC2-compatible instance on a Snowball Edge with AWS OpsHub Follow these steps to launch an Amazon EC2-compatible instance using AWS OpsHub. This video shows how to launch an Amazon EC2-compatible instance using AWS OpsHub. [![AWS Videos](http://img.youtube.com/vi/https://www.youtube.com/embed/0Q7s7JiBCf0?start=88&end=97/0.jpg)](http://www.youtube.com/watch?v=https://www.youtube.com/embed/0Q7s7JiBCf0?start=88&end=97) **To launch an Amazon EC2-compatible instance** 1. Open the AWS OpsHub application. 1. In the **Start computing** section on the dashboard, choose **Get started**. Or, choose the **Services** menu at the top, and then choose **Compute (EC2)** to open the **Compute** page. All your compute resources appear in the **Resources** section. 1. If you have Amazon EC2-compatible instances running on your device, they appear in the **Instance name** column under **Instances**. You can see details of each instance on this page. 1. Choose **Launch instance**. The launch instance wizard opens. 1. For **Device**, choose the Snow device that you want to launch the Amazon EC2-compatible. ![\[AWS OpsHub launch instance wizard\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-launch-ec2-console.png) 1. For **Image (AMI)**, choose an Amazon Machine Image (AMI) from the list. This AMI is used to launch your instance. 1. For **Instance type**, choose one from the list. 1. Choose how you want to attach an IP address to the instance. You have the following options: + **Create public IP address (VNI)** – Choose this option to create a new IP address using a physical network interface. Choose a physical network interface and IP address assignment. + **Use existing IP address (VNI)** – Choose this option to use an existing IP address and then use existing virtual network interfaces. Choose a physical network interface and a virtual network interface. + **Do not attach IP address** – Choose this option if you don't want to attach an IP address. 1. Choose how you want to attach a key pair to the instance. You have the following options: **Create key pair** – Choose this option to create a new key pair and launch the new instance with this key pair. **Use existing key pair** – Choose this option to use an existing key pair to launch the instance. **Do not attach IP address** – Choose this option if you don't want to attach a key pair. You must acknowledge that you won't able to connect to this instance unless you already know the password that is built into this AMI. For more information, see [Working with key pairs for EC2-compatible instances in AWS OpsHub](working-with-key-pair.md). 1. Choose **Launch**. You should see your instance launching in the **Compute instances** section. The **State** is **Pending** and then changes to **Running** when done. # Stopping an Amazon EC2-compatible instance on a Snowball Edge with AWS OpsHub Use the following steps to use AWS OpsHub to stop an Amazon EC2-compatible instance. **To stop an Amazon EC2-compatible instance** 1. Open the AWS OpsHub application. 1. In the **Start computing** section of the dashboard, choose **Get started**. Or, choose the **Services** menu at the top, and then choose **Compute (EC2)** to open the **Compute** page. All your compute resources appear in the **Resources** section. 1. If you have Amazon EC2-compatible instances running on your device, they appear in the **Instance name** column under **Instances**. 1. Choose the instance that you want to stop, choose the **Actions** menu, and choose **Stop**. The **State** changes to **Stopping**, and then to **Stopped** when done. ![\[Instance selection and Action menu showing Stop option\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-stop-ec2-console.png) # Starting an Amazon EC2-compatible instance on an Snowball Edge with AWS OpsHub Use these steps to start an Amazon EC2-compatible instance using AWS OpsHub. **To start an Amazon EC2-compatible instance** 1. Open the AWS OpsHub application. 1. In the **Start computing** section of the dashboard, choose **Get started**. Or, choose the **Services** menu at the top, and then choose **Compute (EC2)** to open the **Compute** page. Your compute resources appear in the **Resources** section. 1. In the **Instance name** column, under **Instances**, find the instance that you want to start. 1. Choose the instance, and then choose **Start**. The **State** changes to **Pending**, and then changes to **Running** when done. ![\[Instances tab showing an instance chosen and the Actions menu open with Start chosen.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-instance-start-console.png) # Working with key pairs for EC2-compatible instances in AWS OpsHub When you launch an Amazon EC2-compatible instance and intend to connect to it using SSH, you have to provide a key pair. You can use Amazon EC2 to create a new key pair, or you can import an existing key pair or manage your key pairs. **To create, import, or manage key pairs** 1. Open **Compute** on the AWS OpsHub dashboard. 1. In the navigation pane, choose the **Compute (EC2)** page, and then choose the **Key Pairs** tab. You are redirected to the Amazon EC2 console where you can create, import, or manage your key pairs. 1. For instructions on how to create and import key pairs, see [Amazon EC2 key pairs and Linux instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html#prepare-key-pair) in the *Amazon EC2 User Guide*. # Terminating an Amazon EC2-compatible instance with AWS OpsHub After you terminate an Amazon EC2-compatible instance, you can't restart the instance. **To terminate an Amazon EC2-compatible instance** 1. Open the AWS OpsHub application. 1. In the **Start computing** section on the dashboard, choose **Get started**. Or, choose the **Services** menu at the top, and then choose **Compute (EC2)** to open the **Compute** page. You can see all your compute resources in the **Resources** section. 1. In the **Instance name** column, under **Instances**, find the instance that you want to terminate. 1. Choose the instance, and choose the **Actions**menu. From the **Actions** menu, choose **Terminate**. ![\[Instances tab showing instance chose and Actions menu showing Terminate chosen.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-instance-terminate-console.png) 1. In the **Terminate instances window, choose **Confirm terminate****. ![\[Terminate instances window showing instance name and Confirm terminate button.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-instance-terminate-instances-console.png) **Note** After the instance is terminated, you can't restart it. The **State** changes to **Terminating**, and then to **Terminated** when done. # Using storage volumes locally on Snowball Edge with AWS OpsHub Amazon EC2-compatible instances use Amazon EBS volumes for storage. In this procedure, you create a storage volume and attach it to your instance using AWS OpsHub. **To create a storage volume** 1. Open the AWS OpsHub application. 1. In the **Start computing** section on the dashboard, choose **Get started**. Or, choose the **Services** menu at the top, and then choose **Compute (EC2)** to open the **Compute** page. 1. Choose the **Storage volumes** tab. If you have storage volumes on your device, the details about the volumes appear under **Storage volumes**. 1. Choose **Create volume** to open the **Create volume** page. ![\[Create Volume page\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-create-volume-console.png) 1. Choose the device that you want to create the volume on, enter the size (in GiBs) that you want to create, and choose the type of volume. 1. Choose **Submit**. The **State** is **Creating**, and changes to **Available** when done. You can see your volume and details about it in the **Volumes** tab. **To attach a storage volume to your instance** 1. Choose the volume that you created, and then choose **Attach volume**. ![\[Attach volume window showing Compute Instance Id and Volume Device Name\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-attach-volume-console.png) 1. For **Compute instance Id**, choose the instance you want to attach the volume to. 1. For **Volume Device Name**, enter the device name of your volume (for example, **/dev/sdh** or **xvdh**). 1. Choose **Attach**. If you no longer need the volume, you can detach it from the instance and then delete it. # Importing an image as an Amazon EC2-compatible AMI with AWS OpsHub You can import a snapshot of your image into your Snowball Edge device and register it as an Amazon EC2-compatible Amazon Machine Image (AMI). A snapshot is basically a copy of your storage volume that you can use to create an AMI or another storage volume. By doing this, you can bring your own image from an external source onto your device and launch it as an Amazon EC2-compatible instance. Follow these steps to complete the import of your image. 1. Upload your snapshot into an Amazon S3 bucket on your device. 1. Set up the required permissions to grant access to Amazon S3, Amazon EC2, and VM Import/Export, the feature that is used to import and export snapshots. 1. Import the snapshot from the S3 bucket into your device as an image. 1. Register the image as an Amazon EC2-compatible AMI. 1. Launch the AMI as an Amazon EC2-compatible instance. **Note** Be aware of the following limitations when uploading snapshots to Snowball Edge. Snowball Edge currently only support importing snapshots that are in the RAW image format. Snowball Edge currently only support importing snapshots with sizes from 1 GB to 1 TB. ## Step 1: Upload a snapshot into an S3 bucket on your device You must upload your snapshot to Amazon S3 on your device before you import it. This is because snapshots can only be imported from Amazon S3 available on your device or cluster. During the import process, you choose the S3 bucket on your device to store the image in. **To upload a snapshot to Amazon S3** + To create an S3 bucket, see [Creating Amazon S3 Storage](https://docs.aws.amazon.com/snowball/latest/developer-guide/manage-s3.html#create-s3-storage). To upload a snapshot to an S3 bucket, see [Uploading Files to Amazon S3 Storage](https://docs.aws.amazon.com/snowball/latest/developer-guide/manage-s3.html#upload-file). ## Step 2: Import the snapshot from an S3 bucket When your snapshot is uploaded to Amazon S3, you can import it to your device. All snapshots that have been imported or are in the process of being imported are shown in **Snapshots** tab. This video shows how to import and register a snapshot as an Amazon EC2-compatible AMI, including creating a policy for an IAM user. [![AWS Videos](http://img.youtube.com/vi/https://www.youtube.com/embed/GDDJgQCtPRg?start=192&end=348/0.jpg)](http://www.youtube.com/watch?v=https://www.youtube.com/embed/GDDJgQCtPRg?start=192&end=348) **To import the snapshot to your device** 1. Open the AWS OpsHub application. 1. In the **Start computing** section on the dashboard, choose **Get started**. Or, choose the **Services** menu at the top, and then choose **Compute (EC2)** to open the **Compute** page. All your compute resources appear in the **Resources** section. 1. Choose the **Snapshots** tab to see all the snapshots that have been imported to your device. The image file in Amazon S3 is a .raw file that is imported to your device as a snapshot. You can filter by snapshot ID or the state of the snapshot to find specific snapshots. You can choose a snapshot ID to see details of that snapshot. 1. Choose the snapshot that you want to import, and choose **Import snapshot** to open the **Import snapshot** page. 1. For **Device**, choose the IP address of the Snow Family device that you want to import to. 1. For **Import description** and **Snapshot description**, enter a description for each. 1. In the **Role** list, choose a role to use for the import. Snowball Edge use VM Import/Export to import snapshots. AWS assumes this role and uses it to import the snapshot on your behalf. If you don't have a role configured on your AWS Snowball Edge, open the AWS Identity and Access Management (IAM in AWS OpsHub where you can create a local IAM role. The role also needs a policy that has the required VM Import/Export permissions to perform the import. You must attach this policy to the role. For more details on this please refer to [Using IAM Locally](https://docs.aws.amazon.com/snowball/latest/developer-guide/using-local-iam.html). The following is an example of the policy. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement":[ { "Effect":"Allow", "Principal":{ "Service":"vmie.amazonaws.com" }, "Action":"sts:AssumeRole" } ] } ``` ------ Sign in to the AWS Management Console and open the IAM console at [https://console.aws.amazon.com/iam/](https://console.aws.amazon.com/iam/). The role you create should have minimum permissions to access Amazon S3 The following is example of a minimum policy. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement":[ { "Effect":"Allow", "Action":[ "s3:GetBucketLocation", "s3:GetObject", "s3:ListBucket" ], "Resource":[ "arn:aws:s3:::import-snapshot-bucket-name", "arn:aws:s3:::import-snapshot-bucket-name/*" ] } ] } ``` ------ 1. Choose **Browse S3** and choose the S3 bucket that contains the snapshot that you want to import. Choose the snapshot, and choose **Submit**. The snapshot begins to download onto your device. You can choose the snapshot ID to see the details. You can cancel the import process from this page. ## Step 3: Register the snapshot as an Amazon EC2-compatible AMI The process of creating an Amazon EC2-compatible AMI from an image imported as a snapshot is known as *registering*. Images that are imported to your device must be registered before they can be launched as Amazon EC2-compatible instances. This video shows how to register a snapshot as an Amazon EC2-compatible AMI. [![AWS Videos](http://img.youtube.com/vi/https://www.youtube.com/embed/GDDJgQCtPRg?start=222&end=255/0.jpg)](http://www.youtube.com/watch?v=https://www.youtube.com/embed/GDDJgQCtPRg?start=222&end=255) **To register an image imported as a snapshot** 1. Open the AWS OpsHub application. 1. In the **Start computing** section on the dashboard, choose **Get started**. Or, choose the **Services** menu at the top, and then choose **Compute (EC2)** to open the **Compute** page. All your compute resources appear in the **Resources** section. 1. Choose the **Images** tab. You can filter the images by name, ID, or state to find a specific image. 1. Choose the image that you want to register, and choose **Register image**. ![\[Image chosen with Register image button highlighted.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-register-image-console.png) 1. On the **Register image** page, provide a **Name** and **Description**. 1. For **Root volume**, specify the name of the root device. In the **Block device** section, you can change the size of the volume and the volume type. 1. If you want the volume to be deleted when the instance is terminated, choose **Delete on termination**. 1. If you want to add more volumes, choose **Add new volume**. 1. When you are done, choose **Submit**. ## Step 4: Launch the Amazon EC2-compatible AMI + For more information, see [Launching an Amazon EC2-compatible instance](https://docs.aws.amazon.com/snowball/latest/snowcone-guide/manage-ec2.html#launch-instance). # Deleting a snapshot from a Snowball Edge with AWS OpsHub If you no longer need a snapshot, you can delete it from your device. The image file in Amazon S3 is a .raw file that is imported to your device as a snapshot. If the snapshot that you are deleting is used by an image, it can't be deleted. After import is completed, you can also delete the .raw file that you uploaded to Amazon S3 on your device. **To delete a snapshot** 1. Open the AWS OpsHub application. 1. In the **Start computing** section on the dashboard, choose **Get started**. Or, choose the **Services** menu at the top, and then choose **Compute (EC2)** to open the **Compute** page. All your compute resources appear in the **Resources** section. 1. Choose the **Snapshot** tab to see all snapshots that have been imported. You can filter by snapshot ID or state of the snapshot to find specific snapshots. 1. Choose the snapshot that you want to delete, and choose **Delete**. You can choose multiple snapshots. ![\[Snapshots tab showing instance and Delete button\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-delete-snapshot-console.png) 1. In the **Delete snapshot confirmation** box, choose **Delete snapshot**. If your deletion is successful, the snapshot is removed from the list under the **Snapshots** tab. # Deregistering an AMI on a Snowball Edge with AWS OpsHub **To deregister an AMI** 1. Open the AWS OpsHub application. 1. In the **Start computing** section on the dashboard, choose **Get started**. Or, choose the **Services** menu at the top, and then choose **Compute (EC2)** to open the **Compute** page. All your compute resources appear in the **Resources** section. 1. Choose the **Images** tab. All your images are listed. You can filter the images by name, ID, or state to find a specific image. 1. Choose the image that you want to deregister, and choose **Deregister**. ![\[Image tab showing image chosen and Deregister image button at top right.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-image-deregister-console.png) 1. In the **Confirm deregister image** window, confirm the image ID and choose **Deregister image**. When deregistering is successful, the image is removed from the list of images. ![\[Confirm deregister image window showing image name and Deregister image button.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-confirm-deregister-image-console.png) # Managing an Amazon EC2 cluster on Snowball Edge with AWS OpsHub An Amazon EC2 *cluster* is a group of devices that provision together as a cluster of devices. To use a cluster, the AWS services on your device must be running at your default endpoint. You also must choose the specific device in the cluster that you want to talk to. You use a cluster on a per-device basis. **To create an Amazon EC2 cluster** 1. Connect and log in to your Snow device. For instructions on how to log in to your device, see [Unlocking a Snowball Edge device with AWS OpsHub](connect-unlock-device.md). 1. On the **Choose device** page, choose **Snowball Edge cluster**, and then choose **Next**. 1. On the **Connect to your device** page, provide the IP address of the device and the IP addresses of other devices in the cluster. 1. Choose **Add another** device to add more devices, and then choose **Next**. 1. On the **Provide the keys** page, enter the device client unlock code, upload the device manifest, and choose **Unlock device**. Snowball Edge devices use 256-bit encryption to help ensure both security and full chain-of-custody for your data. 1. (Optional) Enter a name to create a profile, and then choose **Save profile name**. You are directed to the dashboard, where you see all your clusters. You can now start using AWS services and managing your cluster. You manage instances in the cluster the same way you manage individual instances. For instructions, see [Managing AWS services on the Snowball Edge with AWS OpsHub](manage-services.md). # Set up Amazon S3 compatible storage on Snowball Edge with AWS OpsHub The Amazon S3 compatible storage on Snowball Edge service is not active by default. To start the service on a device or cluster, you must create two virtual network interfaces (VNICs) on each device to attach to the `s3control` and `s3api` endpoints. **Topics** + [Amazon S3 compatible storage on Snowball Edge prerequisites for AWS OpsHub](#s3-edge-snow-opshub-prereqs) + [Using the Amazon S3 compatible storage on Snowball Edge simple setup option in AWS OpsHub](#s3-edge-snow-opshub-simple-setup) + [Using the Amazon S3 compatible storage on Snowball Edge advanced setup option using AWS OpsHub](#s3-edge-snow-opshub-advanced-setup) + [Configuring Amazon S3 compatible storage on Snowball Edge to autostart using AWS OpsHub](#autostart-s3compatible) + [Creating a bucket in Amazon S3 compatible storage on Snowball Edge using AWS OpsHub](#s3compatible-create-bucket) + [Upload files and folders to Amazon S3 compatible storage on Snowball Edge buckets using AWS OpsHub](#s3compatible-upload-files) + [Remove files and folders from Amazon S3 compatible storage on Snowball Edge buckets with AWS OpsHub with AWS OpsHub](#s3compatible-remove-files) + [Delete buckets from Amazon S3 compatible storage on Snowball Edge](#s3compatible-delete-bucket) ## Amazon S3 compatible storage on Snowball Edge prerequisites for AWS OpsHub Before you can set up your device or cluster using AWS OpsHub, do the following: + Power on your Snowball Edge device and connect it to your network. + On your local machine, download and install the latest version of [AWS OpsHub](https://docs.aws.amazon.com/snowball/latest/developer-guide/download-opshub.html). Connect to the device or cluster to unlock it with a manifest file. For more information, see [unlocking a device](https://docs.aws.amazon.com/snowball/latest/developer-guide/connect-unlock-device.html). ## Using the Amazon S3 compatible storage on Snowball Edge simple setup option in AWS OpsHub Use the simple setup option if your network uses DHCP. With this option, the VNICs are created automatically on each device when you start the service. 1. Log in to AWS OpsHub, then choose **Manage Storage**. This takes you to the Amazon S3 compatible storage on Snowball Edge landing page. 1. For **Start service setup type**, choose **Simple**. 1. Choose **Start service**. **Note** This takes a few minutes to complete and depends on the number of devices you're using. After the service starts, the Service state is active, and there are endpoints. ![\[The Amazon S3 compatible storage on Snowball Edge resources screen, showing a service state of Active and its active endpoints.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/s3-snow/s3-snow-active-service.png) ## Using the Amazon S3 compatible storage on Snowball Edge advanced setup option using AWS OpsHub Use the advanced setup option if your network uses static IP addresses or if you want to reuse existing VNIs. With this option, you create VNICs for each device manually. 1. Log in to AWS OpsHub, then choose **Manage Storage**. This takes you to the Amazon S3 compatible storage on Snowball Edge landing page. 1. For **Start service setup type**, choose **Advanced**. 1. Select the devices that you need to create VNICs for. For clusters, you need a minimum quorum of devices to start the Amazon S3 compatible storage on Snowball Edge service. The quorum is two for a three-node cluster. **Note** For the initial start of the service in a cluster setup, you must have all devices in the cluster configured and available for the service to start. For subsequent starts, you can use a subset of the devices if you meet quorum, but the service will start in a degraded state. 1. For each device, choose an existing VNIC or select **Create VNI**. Each device needs a VNIC for the **S3 endpoint** for object operations and another for the **S3Control endpoint** for bucket operations. 1. If you're creating a VNIC, choose a physical network interface and enter the status IP address and subnet mask, then choose **Create virtual network interface**. 1. After you create your VNICS, choose **Start service**. **Note** This takes a few minutes to complete and depends on the number of devices you're using. After the service starts, the Service state is active, and there are endpoints. ## Configuring Amazon S3 compatible storage on Snowball Edge to autostart using AWS OpsHub 1. Log in to AWS OpsHub, then choose **Manage Storage**. This takes you to the Amazon S3 compatible storage on Snowball Edge landing page. 1. In **Amazon S3 compatible storage on Snow resources**, choose **Enable service auto-start**. The system configures the service to automatically start in the future. ![\[Amazon S3 compatible storage on Snow resources area with Enable service auto-start at top right.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-autostart-s3compatible-console.png) ## Creating a bucket in Amazon S3 compatible storage on Snowball Edge using AWS OpsHub Use the AWS OpsHub interface to create an Amazon S3 bucket on your Snowball Edge device. 1. Open AWS OpsHub. 1. In **Manage storage**, choose **Get started**. The **Amazon S3 compatible storage on Snow** page appears. 1. In **Buckets**, choose **Create bucket**. The **Create bucket** screen appears. ![\[Create bucket page.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-create-bucket-s3compatible-console.png) 1. In **Bucket name**, enter a name for the bucket. **Note** Bucket names must be unique within your Snowball device or cluster and must not contain spaces or uppercase letters. 1. Choose **Create bucket**. The system creates the bucket and it appears in **Buckets** in the **Amazon S3 compatible storage on Snow** page. ## Upload files and folders to Amazon S3 compatible storage on Snowball Edge buckets using AWS OpsHub Use the AWS OpsHub interface to upload files and folders to Amazon S3 compatible storage on Snowball Edge buckets. Files and folders may be uploaded separately or together. 1. Open AWS OpsHub 1. In **Manage storage**, in **Buckets**, choose a bucket in which to upload files. The page for that bucket appears. 1. In the bucket page, choose **Upload files**. The **Upload** page appears. ![\[Upload page with drag-and-drop area surrounded with a dashed, blue line.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-upload-s3compatible-console.png) 1. Upload files or folders by dragging them from an operating system file manager to the AWS OpsHub window or do the following: 1. Select **Add files** or **Add folders**. 1. Select one or more files or folders to upload. Select **Open**. The system uploads the selected files and folders to the bucket on the device. After the upload is complete, the names of the files and folders appear in the **Files and folders** list. ## Remove files and folders from Amazon S3 compatible storage on Snowball Edge buckets with AWS OpsHub with AWS OpsHub Use the AWS OpsHub interface to remove and permanently delete files and folders from buckets on the Snowball Edge device. 1. Open AWS OpsHub. 1. In **Manage storage**, in **Buckets**, select the name of a bucket from which to delete files and folders. The page for that bucket appears. 1. In **Files and folders** select the check boxes of the files and folders to permanently delete. 1. Select **Remove**. The system removes the files or folders from the bucket on the device. ## Delete buckets from Amazon S3 compatible storage on Snowball Edge Before you can delete a bucket from a device, the bucket must be empty. Either remove files and folders from the bucket or use the empty bucket tool. To remove files and folders, see [Remove files and folders from Amazon S3 compatible storage on Snowball Edge buckets with AWS OpsHub with AWS OpsHub](#s3compatible-remove-files). **To use the empty bucket tool** 1. Open AWS OpsHub. 1. In **Manage storage**, in **Buckets**, select the radio button of the bucket to empty. 1. Select **Empty**. The **Empty bucket** page appears. ![\[Empty bucket page with warning that emptying a bucket cannot be undone.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-empty-bucket-s3compatible-console.png) 1. In the text box in the **Empty bucket** page, type **permanently delete**. 1. Select **Empty**. The system empties the bucket. **To delete an empty bucket** 1. In **Manage storage**, in **Buckets**, select the radio button of the bucket to delete. 1. Select **Delete**. The **Delete bucket** page appears. ![\[Delete bucket page showing text box for bucket name and delete button.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-delete-bucket-s3compatible-console.png) 1. In the text box in the **Delete bucket** page, type the name of the bucket. 1. Select **Delete**. The system deletes the bucket from the device. # Managing Amazon S3 adapter storage with AWS OpsHub You can use AWS OpsHub to create and manage Amazon Simple Storage Service (Amazon S3) storage on your Snowball Edge using the S3 adapter for import and export jobs. **Topics** + [Accessing Amazon S3 storage with AWS OpsHub](#create-s3-storage) + [Uploading files to Amazon S3 storage with AWS OpsHub](#upload-file) + [Downloading files from Amazon S3 storage with AWS OpsHub](#download-file) + [Deleting files from Amazon S3 storage with AWS OpsHub](#delete-file) ## Accessing Amazon S3 storage with AWS OpsHub You can upload files to your device and access the files locally. You can physically move them to another location on the device, or import them back to the AWS Cloud when the device is returned. Snowball Edge use Amazon S3 buckets to store and manage files on your device. **To access an S3 bucket** 1. Open the AWS OpsHub application. 1. In the **Manage file storage** section of the dashboard, choose **Get started**. If your device has been ordered with the Amazon S3 transfer mechanism, they appear in the **Buckets** section of the **File & object storage** page. On the **File & object storage** page, you can see details of each bucket. **Note** If the device was ordered with the NFS transfer mechanism, the bucket name will appear under the mount points section after NFS service is configure and activated. For more information on using the NFS interface, see [Managing the NFS interface with AWS OpsHub](manage-nfs.md). ![\[File and object storage page showing Amazon S3 buckets on the Snowball Edge device\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-access-s3-console.png) ## Uploading files to Amazon S3 storage with AWS OpsHub This video shows how to upload files to Amazon S3 storage using AWS OpsHub. [![AWS Videos](http://img.youtube.com/vi/https://www.youtube.com/embed/Bw8rzQhT1nM?start=472/0.jpg)](http://www.youtube.com/watch?v=https://www.youtube.com/embed/Bw8rzQhT1nM?start=472) **To upload a file** 1. In the **Manage file storage** section on the dashboard, choose **Get started**. If you have Amazon S3 buckets on your device, they appear in the **Buckets** section on the **File storage** page. You can see details of each bucket on the page. 1. Choose the bucket that you want to upload files into. 1. Choose **Upload** then **Upload files** or drag and drop the files in the bucket, and choose **OK**. ![\[Amazon S3 bucket with Upload files chosen from the Upload menu\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-upload-s3-console.png) **Note** To upload larger files, you can use the multipart upload feature in Amazon S3 using the AWS CLI. For more information about configuring S3 CLI settings, see [CLI S3 Configuration](https://docs.aws.amazon.com/cli/latest/topic/s3-config.html). For more information on multipart upload, see [Multipart Upload Overview](https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html) in the Amazon Simple Storage Service User Guide Uploading a folder from a local machine to Snowball Edge using the AWS OpsHub is supported. If the folder size is very large, it takes some time for OpsHub to read the file/folder selection. While OpsHub is reading the files and folders, it does not display a progress tracker. However, it does display a progress tracker is displayed once the upload process begins. ## Downloading files from Amazon S3 storage with AWS OpsHub **To download a file** 1. In the **Manage file storage** section of the dashboard, choose **Get started**. If you have S3 buckets on your device, they appear in the **Buckets** section on the **File storage** page. You can see details of each bucket on the page. 1. Choose the bucket that you want to download files from and navigate to the file that you want to download. Choose one or more files. ![\[File and object storage page showing one file selected and the actions menu open showing Download file option.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-download-file-console.png) 1. In the **Actions** menu, choose **Download**. 1. Choose a location to download the file to, and choose **OK**. ## Deleting files from Amazon S3 storage with AWS OpsHub If you no longer need a file, you can delete it from your Amazon S3 bucket. **To delete a file** 1. In the **Manage file storage** section of the dashboard, choose **Get started**. If you have Amazon S3 buckets on your device, they appear in the **Buckets** section on the **File storage** page. You can see details of each bucket on the page. 1. Choose the bucket you want to delete files from, and navigate to the file that you want to delete. 1. On the **Actions** menu, choose **Delete**. 1. In the dialog box that appears, choose **Confirm delete**. # Managing the NFS interface with AWS OpsHub Use the Network File System (NFS) interface to upload files to the Snowball Edge as if the device is local storage to your operating system. This allows for a more user-friendly approach to transferring data because you can use features of your operating system, like copying files, dragging and dropping them, or other graphical user interface features. Each S3 bucket on the device is available as an NFS interface endpoint and can be mounted to copy data to. The NFS interface is available for import jobs. You can use the NFS interface if the Snowball Edge device was configured to include it when the job to order the device was created. If the device is not configured to include the NFS interface, use the S3 adapter or Amazon S3 compatible storage on Snowball Edge to transfer data. For more information about the S3 adapter, see [Managing Amazon S3 adapter storage with AWS OpsHub](manage-s3.md). For more information about Amazon S3 compatible storage on Snowball Edge, see [Set up Amazon S3 compatible storage on Snowball Edge with AWS OpsHub](s3-edge-snow-opshub.md). When started, the NFS interface uses 1 GB of memory and 1 CPU. This may limit the number of other services running on the Snowball Edge or the number of EC2-compatible instances that can run. Data transferred through the NFS interface is not encrypted in transit. When configuring the NFS interface, you can provide CIDR blocks and the Snowball Edge will restrict access to the NFS interface from client computers with addresses in those blocks. Files on the device will be transferred to Amazon S3 when it is returned to AWS. For more information, see [Importing Jobs into Amazon S3](https://docs.aws.amazon.com/snowball/latest/developer-guide/importtype.html). For more information about using NFS with your computer operating system, see the documentation for your operating system. Keep the following details in mind when using the NFS interface. + The NFS interface provides a local bucket for data storage on the device. For import jobs, no data from the local bucket will be imported to Amazon S3. + File names are object keys in your local S3 bucket on the Snowball Edge. The key name is a sequence of Unicode characters whose UTF-8 encoding is at most 1,024 bytes long. We recommend using NFSv4.1 where possible and encode file names with Unicode UTF-8 to ensure a successful data import. File names that are not encoded with UTF-8 might not be uploaded to S3 or might be uploaded to S3 with a different file name depending on the NFS encoding you use. + Ensure that the maximum length of your file path is less than 1024 characters. Snowball Edge do not support file paths that are greater that 1024 characters. Exceeding this file path length will result in file import errors. + For more information, see [Object keys](https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingMetadata.html) in the Amazon Simple Storage Service User Guide. + For NFS based transfers, standard POSIX style metadata will be added to your objects as they get imported to Amazon S3 from Snowball Edge. In addition, you will see meta-data "x-amz-meta-user-agent aws-datasync" as we currently use AWS DataSync as part of the internal import mechanism to Amazon S3 for Snowball Edge import with NFS option. + You can transfer up to 40M files using a single Snowball Edge device. If you require to transfer more than 40M files in a single job, please batch the files in order to reduce the file numbers per each transfer. Individual files can be of any size with a maximum file size of 5 TB for Snowball Edge devices with the enhanced NFS interface or the S3 interface. You can also configure and manage the NFS interface with the Snowball Edge client, a command line interface (CLI) tool. For more information, see [Managing the NFS interface](https://docs.aws.amazon.com/snowball/latest/snowcone-guide/shared-using-nfs.html). **Topics** + [Starting the NFS service on a Windows operating system](#mount-nfs-on-window-client) + [Configuring the NFS interface automatically with AWS OpsHub](#auto-configure-nfs) + [Configuring the NFS interface manually with AWS OpsHub](#configure-with-snowcone) + [Managing NFS endpoints on the Snowball Edge with AWS OpsHub](#managing-nfs-endpoint) + [Mounting NFS endpoints on client computers](#mounting-nfs-endpoint) + [Stopping the NFS interface with AWS OpsHub](#stop-nfs) ## Starting the NFS service on a Windows operating system If your client computer is using the Windows 10 Enterprise or Windows 7 Enterprise operating system, start the NFS service on the client computer before configuring NFS in the AWS OpsHub application. 1. On your client computer, open **Start**, choose **Control Panel** and choose **Programs**. 1. Choose **Turn Windows features on or off**. **Note** To turn Windows features on, you may need to provide an admin user name and password for your computer. 1. Under **Services for NFS**, choose **Client for NFS** and choose **OK**. ## Configuring the NFS interface automatically with AWS OpsHub The NFS interface is not running on the Snowball Edge device by default, so you need to start it to enable data transfer on the device. With a few clicks, your Snowball Edge can quickly and automatically configure the NFS interface for you. You can also configure the NFS interface yourself. For more information, see [Configuring the NFS interface manually with AWS OpsHub](#configure-with-snowcone). 1. In the **Transfer data** section on the dashboard, choose **Enable & start**. This could take a minute or two to complete. ![\[File storage dashboard showing Enable and start button.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub_enable_start_nfs_console.png) 1. When the NFS service is started, the IP address of the NFS interface is shown on the dashboard and the **Transfer data** section indicates that the service is active. 1. Choose **Open in Explorer** (if using a Windows or a Linux operating system) to open the file share in your operating system's file browser and start transferring files to the Snowball Edge. You can copy and paste or drag and drop files from your client computer into the file share. In Windows operating system, your file share looks like the following `buckets(\\12.123.45.679)(Z:)`. **Note** In Linux operating systems, mounting NFS endpoints requires root permissions. ## Configuring the NFS interface manually with AWS OpsHub The NFS interface is not running on the Snowball Edge device by default, so you need to start it to enable data transfer on the device. You can manually configure the NFS interface by providing the IP address of a Virtual Network Interface (VNI) running on the Snowball Edge device and restricting access to your file share, if required. Before configuring the NFS interface manually, set up a virtual network interface (VNI) on your Snowball Edge device. For more information, see [Network Configuration for Compute Instances](https://docs.aws.amazon.com/snowball/latest/developer-guide/network-config-ec2.html). You can also have the Snowball Edge device configure the NFS interface automatically. For more information, see [Configuring the NFS interface automatically with AWS OpsHub](#auto-configure-nfs). 1. At the bottom of **Transfer data** section, on the dashboard, choose **Configure manually**. [![AWS Videos](http://img.youtube.com/vi/https://www.youtube.com/embed/StMa2A7X2yA?start=78&end=119/0.jpg)](http://www.youtube.com/watch?v=https://www.youtube.com/embed/StMa2A7X2yA?start=78&end=119) 1. Choose **Enable & start** to open the **Start NFS** wizard. The **Physical network interface** field is populated. ![\[The Start NFS wizard\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-nfs-console.png) 1. Choose **Create IP address (VNI)** or choose **Use existing IP address**. 1. If you choose **Create IP address (VNI)**, then choose **DHCP** or **Static IP** in the **IP Address assignment** list box. **Important** If you use a DHCP network, it is possible that the NFS interface's IP address could be reassigned by the DCHP server. This can happen after the device has been disconnected and the IP addresses are recycled. If you set an allowed host range and the address of the client changes, another client can pick up that address. In this case, the new client will have access to the share. To prevent this, use DHCP reservations or static IP addresses. If you choose **Use existing IP address**, then choose a virtual network interface from the **Virtual network interface** list box. 1. Choose to restrict access to the NFS interface and provide a block of allowed network addresses, or allow any devices on the network to access the NFS interface on the Snowball Edge. + To restrict access to the NFS interface on the Snowball Edge, choose **Restrict NFS to allowed hosts**. In **Allowed hosts** enter a set of CIDR blocks. If you want to allow access to more than one CIDR block, enter another set of blocks. To remove a set of blocks, choose **X** next to the field containing the blocks. Choose **Add allowed hosts**. **Note** If you choose **Restrict NFS to allowed hosts** and do not provide allowed CIDR blocks, the Snowball Edge will deny all requests to mount the NFS interface. + To allow any device on the network to access the NFS interface, choose **Allow all hosts**. 1. To allow EC2-compatible instances running on the Snowball Edge to access the NFS adapter, choose **Enable**. 1. Choose **Start NFS**. It could take about a minute or two to start. **Important** Don't turn off the Snowball Edge while the NFS interface is starting. From the **Network File System (NFS) Resources** section, the **State** of the NFS interface shows as **Active**. You will need the IP address listed to mount the interface as local storage on client computers. ## Managing NFS endpoints on the Snowball Edge with AWS OpsHub Each S3 bucket on the Snowball Edge is represented as an endpoint and listed in **Mount paths**. After the NFS interface is started, mount an endpoint to transfer files to or from that endpoint. Only one endpoint can be mounted at a time. To mount a different endpoint, unmount the current endpoint first. **To mount an endpoint** 1. In the **Mount paths** section, do one of the following to select an endpoint: + In the **Filter endpoints** field, enter all or part a bucket name to filter the list of available endpoints on your entry, then choose the endpoint. + Choose the endpoint to mount in the **Mount paths** list. 1. Choose **Mount NFS endpoint**. The Snowball Edge mounts the endpoint for use. **To unmount an endpoint** 1. In the **Mount paths** section, choose the endpoint to unmount. 1. Choose **Unmount endpoint**. The Snowball Edge unmounts the endpoint and it is no longer available for use. **Note** Before unmounting an endpoint, ensure no data is being copied from or to it. ## Mounting NFS endpoints on client computers After the NFS interface is started and an endpoint mounted, mount the endpoint as local storage on client computers. 1. In **Mount paths**, choose the copy icon of the endpoint to mount. Paste it in your operating system when mounting the endpoint. 1. The following are the default mount commands for Windows, Linux, and macOS operating systems. + Windows: ``` mount -o nolock rsize=128 wsize=128 mtype=hard nfs-interface-ip-address:/buckets/BucketName * ``` + Linux: ``` mount -t nfs nfs-interface-ip-address:/buckets/BucketName mount_point ``` + macOS: ``` mount -t nfs -o vers=3,rsize=131072,wsize=131072,nolocks,hard,retrans=2 nfs-interface-ip-address:/buckets/$bucketname mount_point ``` ## Stopping the NFS interface with AWS OpsHub Stop the NFS interface on the Snowball Edge device when you are done transferring files to or from it. 1. From the dashboard, choose **Services** and then choose **File Storage**. 1. On the **File Storage** page, choose **Disable data transfer**. It usually takes up to 2 minutes for the NFS endpoints to disappear from the dashboard. # Rebooting the device with AWS OpsHub Follow these steps to use AWS OpsHub to reboot your Snow device. **Important** We highly recommend that you suspend all activities on the device before you reboot the device. Rebooting a device stops running instances and interrupts any writing to Amazon S3 buckets on the device. **To reboot a device** 1. On the AWS OpsHub dashboard, find your device under **Devices**. Then choose the device to open the device details page. 1. Choose the **Device Power** menu, then choose **Reboot**. A dialog box appears. ![\[Device details page showing Device Power menu open with Reboot chosen.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-device-reboot-console.png) 1. In the dialog box, choose **Reboot**. Your device starts to reboot. ![\[Reboot device window showing Reboot button at lower right.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-reboot-window-console.png) While the device shuts 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) ## Managing profiles with AWS OpsHub You can create a *profile* for persistent storage of your credentials on your local file system. Using AWS OpsHub, you have the option to create a new profile any time you unlock the device using the device IP address, unlock code, and manifest file. You can also use the Snowball Edge Client to create a profile at any time. See [Configuring a profile for the Snowball Edge Client](https://docs.aws.amazon.com/snowball/latest/developer-guide/using-client-commands.html#client-configuration). **To create a profile** 1. Unlock your device locally and sign in according to the instructions in [Unlocking a Snowball Edge device with AWS OpsHub](connect-unlock-device.md). 1. Name the profile and choose **Save profile name**. # Shutting down the device with AWS OpsHub Follow these steps to use AWS OpsHub to shut down your Snow device. **Important** We highly recommend that you suspend all activities on the device before you shut down the device. Shutting down a device stops running instances and interrupts any writing to Amazon S3 buckets on the device. **To shut down a device** 1. On the AWS OpsHub dashboard, find your device under **Devices**. Then choose the device to open the device details page. 1. Choose the **Device Power** menu, then choose **Shutdown**. A dialog box appears. ![\[Device details page showing Device Power menu open with Shutdown chosen.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-device-shutdown-console.png) 1. In the dialog box, choose **Shutdown**. Your device starts to shut down. ![\[Shutdown device window showing Shutdown button at lower right.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-shutdown-window-console.png) While the device shuts 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) # Editing the device alias with AWS OpsHub Use these steps to edit your device alias using AWS OpsHub. **To edit your device's alias** 1. On the AWS OpsHub dashboard, find your device under **Devices**. Choose the device to open the device details page. 1. Choose the **Edit device alias** tab. ![\[Device details page showing Edit device alias tab at top right.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-edit-device-alias-button-console.png) 1. For **Device alias**, enter a new name, and choose **Save alias**. ![\[Edit device alias window showing Save alias button at lower right.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-edit-device-alias-window-console.png) # Managing public key certificates using OpsHub You can securely interact with AWS services running on a Snowball Edge device or a cluster of Snowball Edge devices through the HTTPS protocol by providing a public key certificate. You can use the HTTPS protocol to interact with AWS services such as IAM, Amazon EC2, S3 adapter, Amazon S3 compatible storage on Snowball Edge, Amazon EC2 Systems Manager, and AWS STS on Snowball Edge devices. In the case of a cluster of devices, a single certificate is required and can be generated by any device in the cluster. Once a Snowball Edge device generates the certificate and you unlock the device, you can use Snowball Edge client commands to list, get, and delete the certificate. A Snowball Edge device generates a certificate when the following events occur: + The Snowball Edge device or cluster is unlocked for the first time. + The Snowball Edge device or cluster is unlocked after deleting the certificate (using the `delete-certificate` command or **Renew certificate** in AWS OpsHub). + The Snowball Edge device or cluster is rebooted and unlocked after the certificate expires. Whenever a new certificate is generated, the old certificate is no longer valid. A certificate is valid for a period of one year from the day it was generated. You can also use the Snowball Edge client to manage public key certificates. For more information, see [Managing public key certificates](https://docs.aws.amazon.com/snowball/latest/developer-guide/snowball-edge-certificates-cli.html). **Topics** + [Download the public key certificate using OpsHub](#download-public-key-certificate-opshub) + [Renewing the public key certificate using OpsHub](#renew-public-key-certificate-opshub) ## Download the public key certificate using OpsHub You can download the active public key certificate to your computer. 1. On the AWS OpsHub dashboard, find your device under **Devices**. Choose the device to open the device details page. 1. In the device details page, choose the **Manage certificate** menu. From the menu, choose **Download certificate**. 1. A window appears in which you can name the certificate file to download and choose the location on your computer where it will be downloaded. Choose **Save**. ## Renewing the public key certificate using OpsHub Before renewing the public key certificate, stop all data transfers to or from the Snowball Edge device and stop any EC2-compatible that are running. For more information, see [Stopping an Amazon EC2-compatible instance](https://docs.aws.amazon.com/snowball/latest/developer-guide/manage-ec2.html#stop-instance) in this guide. 1. On the AWS OpsHub dashboard, find your device under **Devices**. Choose the device to open the device details page. 1. In the device details page, choose the **Manage certificate** menu. From the menu, choose **Renew certificate**. 1. In the **Renew certificate** window, enter **Renew** in the field and choose **Renew**. The Snowball Edge device deletes the existing public key certificate and reboots the device or cluster. ![\[Renew certificate window with field at bottom of window and Renew button at bottom right.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/renew-certificate-opshub.png) # Getting updates for the Snowball Edge You can check for updates for your device and install them. version. **Updating the device** Follow these steps to use AWS OpsHub to update your Snow device. **To update the device** 1. On the AWS OpsHub dashboard, find your device under **Devices**. Choose the device to open the device details page. 1. Choose the **Check for updates** tab. The **Check for updates** page displays the current software version on your device and the latest software version, if there is one. ![\[Check for updates page\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-check-updates-console.png) 1. If there is an update, choose **Download update**. Otherwise, choose **Close**. # Updating the AWS OpsHub application **To verify that automatic updates are enabled for AWS OpsHub** 1. On the AWS OpsHub dashboard, choose** Preferences**. 1. Open the **Updates** tab. 1. Verify that **Automatic updates enabled** is selected. Automatic update is enabled by default. ![\[Updates tab showing automatic updates enabled\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-auto-update-console.png) If **Automatic updates enabled** is not selected, you will not get the latest version of the AWS OpsHub application. # Automating your management tasks with AWS OpsHub You can use AWS OpsHub to automate operational tasks that you perform frequently on your Snowball Edge. You can create a task for reoccurring actions that you might want to perform on resources, such as restarting virtual servers, stopping Amazon EC2-compatible instances, and so on. You provide an automation document that safely performs operational tasks and runs the operation on AWS resources in bulk. You can also schedule common IT workflows. **Note** Automating tasks is not supported on clusters. To use tasks, the Amazon EC2 Systems Manager service must be started first. For more information, see [Activating Snowball Edge Device Management on a Snowball Edge](https://docs.aws.amazon.com/snowball/latest/developer-guide/aws-sdm.html#enable-sdm). **Topics** + [Creating and starting a task with AWS OpsHub](#create-task) + [Viewing details of a task in AWS OpsHub](#view-task) + [Deleting a task in AWS OpsHub](#delete-task) ## Creating and starting a task with AWS OpsHub When you create a task, you specify the types of resources that the task should run on, and then provide a task document that contains the instructions that run the task. The task document is either in YAML or JSON format. You then provide the required parameters for the task and start the task. **To create a task** 1. In the **Launch tasks** section of the dashboard, choose **Get started** to open the **Tasks** page. If you have created tasks, they appear under **Tasks**. 1. Choose **Create task** and provide details for the task. 1. For **Name**, enter a unique name for the task. **Tip** The name must be between 3 and 128 characters. Valid characters are `a-z`, `A-Z`, `0-9`, `.`, `_`, and `-`. 1. Optionally, you can choose a target type from the **Target type-optional** list. This is the type of resource that you want the task to run on. For example, you can specify **/AWS::EC2::Instance** for the tasks to run on an Amazon EC2-compatible instance or **/** to run on all resource types. 1. In the **Content** section, choose **YAML** or **JSON**, and provide the script that performs the task. You have two options, YAML or JSON format. For examples, see [Task examples in AWS OpsHub](#task-examples). 1. Choose **Create**. The task that you created then appears on the **Tasks** page. **To start a task** 1. In the **Launch tasks** section of the dashboard, choose **Get started** to open the **Tasks** page. Your tasks appear under **Tasks**. 1. Choose your task to open the **Start task** page. 1. Choose **Simple execution** to run on targets. Choose **Rate control** to run safely on multiple targets and define concurrency and error thresholds. For this option, you provide the additional target and error threshold information in the **Rate control** section. 1. Provide the required input parameters, and choose **Start task**. The status of the task is **Pending**, and changes to **Success** when the task has run successfully. ### Task examples in AWS OpsHub The following example restarts an Amazon EC2-compatible instance. It requires two input parameters: `endpoint` and `instance ID`. *YAML example* ``` description: Restart EC2 instance schemaVersion: '0.3' parameters: Endpoint: type: String description: (Required) EC2 Service Endpoint URL Id: type: String description: (Required) Instance Id mainSteps: - name: restartInstance action: aws:executeScript description: Restart EC2 instance step inputs: Runtime: python3.7 Handler: restart_instance InputPayload: Endpoint: "{{ Endpoint }}" Id: "{{ Id }}" TimeoutSeconds: 30 Script: |- import boto3 import time def restart_instance(payload, context): ec2_endpoint = payload['Endpoint'] instance_id = payload['Id'] ec2 = boto3.resource('ec2', endpoint_url=ec2_endpoint) instance = ec2.Instance(instance_id) if instance.state['Name'] != 'stopped': instance.stop() instance.wait_until_stopped() instance.start() instance.wait_until_running() return {'InstanceState': instance.state} ``` *JSON example* ``` { "description" : "Restart EC2 instance", "schemaVersion" : "0.3", "parameters" : { "Endpoint" : { "type" : "String", "description" : "(Required) EC2 Service Endpoint URL" }, "Id" : { "type" : "String", "description" : "(Required) Instance Id" } }, "mainSteps" : [ { "name" : "restartInstance", "action" : "aws:executeScript", "description" : "Restart EC2 instance step", "inputs" : { "Runtime" : "python3.7", "Handler" : "restart_instance", "InputPayload" : { "Endpoint" : "{{ Endpoint }}", "Id" : "{{ Id }}" }, "TimeoutSeconds" : 30, "Script" : "import boto3\nimport time\ndef restart_instance(payload, context):\n ec2_endpoint = payload['Endpoint']\n instance_id = payload['Id']\n ec2 = boto3.resource('ec2', endpoint_url=ec2_endpoint)\n instance = ec2.Instance(instance_id)\n if instance.state['Name'] != 'stopped':\n instance.stop()\n instance.wait_until_stopped()\n instance.start()\n instance.wait_until_running()\n return {'InstanceState': instance.state}" } } ] } ``` ## Viewing details of a task in AWS OpsHub You can view details of a management task, such as the description and the parameters that are required to run the task. **To view details of a task** 1. In the **Launch tasks** section of the dashboard, choose **Get started** to open the **Tasks** page. 1. On the **Tasks** page, locate and choose the task that you want to see details of. 1. Choose **View details**, and choose one of the tabs to see the details. For example, the **Parameters** tab shows you the input parameters in the script. ## Deleting a task in AWS OpsHub Follow these steps to delete a management task. **To delete a task** 1. In the **Launch tasks** section of the dashboard, choose** Get started** to open the **Tasks** page. 1. Locate the task that you want to delete. Choose the task, and then choose **Delete**. # Setting the NTP time servers for the device with AWS OpsHub Follow these steps to view and update which time servers your device must synchronize time with. **To check time sources** 1. On the AWS OpsHub dashboard, find your device under **Devices**. Choose the device to open the device details page. 1. You will see a list of time sources that your device is synchronizing time with in the **Time sources** table. The **Time sources** table has four columns: + **Address**: The DNS name / IP address of the time source + **State**: The current connection status between the device and that time source, there are 5 possible states: + **CURRENT**: Time source is currently being used to synchronize time + **COMBINED**: Time source is combined with the current source + **EXCLUDED**: Time source is excluded by the combining algorithm + **LOST**: Connection with the time source has been lost + **UNAVAILABILITY**: An invalid time source where the combining algorithm has deemed to be either a falseticker or has too much variability + **Type**: Network Time Protocol (NTP) sources can be a server or peer. A server can be set by the user using the **update-time-server** command, whereas a peer can only be set up using other Snowball Edge devices in the cluster and are automatically set up when the cluster is associated. + **Stratum**: The stratum of the source. **Stratum 1** indicates a source with a locally attached reference clock. A source that is synchronized to a Stratum 1 source is set at **Stratum 2**. A source that is synchronized to a stratum 2 source is set at **Stratum 3**, and so on. **To update the time servers** 1. On the AWS OpsHub dashboard, find your device under **Devices**. Choose the device to open the device details page. 1. You will see a list of time sources that your device is synchronizing time with in the **Time sources** table. 1. Choose **Update time servers** on the **Time sources** table. 1. Provide the DNS name or the IP address of the time servers you would like your device to synchronize time with, and choose **Update**. ![\[Update time servers showing NTP time server IP address field and Update button.\]](http://docs.aws.amazon.com/snowball/latest/developer-guide/images/opshub-update-time-console.png) **Supported NTP device types and software versions** NTP isn't available on any version 2 storage and compute device types. Snowball Edge version 3 storage and compute device types with software version 77 or later support NTP, however. To check if NTP is enabled, use the Snowball Edge CLI command `describe-time-sources`.