Troubleshooting Compute Instances on Snowball Edge Devices - AWS Snowball Edge Developer Guide
Virtual Network Interface Has an IP Address of 0.0.0.0Snowball Edge Hangs When Launching a Large Compute InstanceMy Instance Has One Root VolumeUnprotected Private Key File Error

Troubleshooting Compute Instances on Snowball Edge Devices

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

Virtual Network Interface Has an IP Address of 0.0.0.0

This issue can occur if the physical network interface (NIC) you associated with your virtual network interface (VNIC) also has an IP address of 0.0.0.0. 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 interface. For example, you might be trying to get the IP address of the SFP+ interface, but it's the RJ45 interface that's connected to your network.

Action to Take

If this occurs, you can do the following:

Snowball Edge Hangs When Launching a Large Compute Instance

It can appear that your Snowball Edge 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.

To check the status of your instances, use the AWS CLI command aws ec2 describe-instances run against the HTTP or HTTPS Amazon EC2-compatible endpoint on the Snowball Edge.

My Instance Has One Root Volume

Instances have one root volume by design. All sbe instances have a single root volume, but with Snowball Edge, you can add or remove block storage based on the needs of your applications. For more information, see Using Block Storage with Your Amazon EC2-compatible Instances.

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