Troubleshooting Compute Instances on Snowcone Devices - Amazon Snowcone User Guide
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Troubleshooting Compute Instances on Snowcone Devices

Following, you can find troubleshooting tips for Snowcone jobs with compute instances.

Virtual Network Interface Has an IP Address of

This issue can occur if the physical network interface (NIC) you associated with your virtual network interface (VNIC) also has an IP address of This effect can happen if the NIC wasn't configured with an IP address (for instance, if you've just powered on the device). It can also happen if you're using the wrong RJ45 interface. The Snowcone has two RJ45 interfaces, you may be specifying the wrong physical interface

Action to Take

If this occurs, you can do the following:

Snowcone Hangs When Launching a Large Compute Instance

It can appear that your Snowcone has stopped launching an instance. This is generally not the case. However, it can take an hour or more for the largest compute instances to launch. You can check the status of your instances using the Amazon CLI command aws ec2 describe-instances run against the HTTP or HTTPS Amazon EC2 endpoint on the Snowcone.

My Instance Has One Root Volume

Instances have one root volume by design. All sbe instances have a single root volume.

For additional information around adding additional volumes, see

Unprotected Private Key File Error

This error can occur if your .pem file on your compute instance has insufficient read/write permissions.

Action to Take

You can resolve this by changing the permissions for the file with the following procedure:

  1. Open a terminal and navigate to the location that you saved your .pem file to.

  2. Enter the following command.

    chmod 400 filename.pem