AWS Snow Family Diagnostics
When to use
Any AWS Snow Family investigation — device ordering, unlocking, data transfer, NFS shares, Snowball Edge compute, EC2 on Snow, S3 adapter, clustering, network configuration, optics, OTA updates, return shipping, or Snowcone-specific issues.
Investigation workflow
Step 1 — Collect and triage
aws snowball list-jobs --query 'JobListEntries[*].{JobId:JobId,State:JobState,Type:JobType,CreationDate:CreationDate}'
aws snowball describe-job --job-id <job-id>
aws snowball list-cluster-jobs --cluster-id <cluster-id>
Step 2 — Domain deep dive
aws snowball get-job-manifest --job-id <job-id>
aws snowball get-job-unlock-code --job-id <job-id>
snowballEdge describe-device --endpoint https://<device-ip>:8243 --manifest-file <manifest> --unlock-code <code>
Step 3 — Detailed investigation
snowballEdge describe-service --service-id s3 --endpoint https://<device-ip>:8243 --manifest-file <manifest> --unlock-code <code>
snowballEdge list-ec2-instances --endpoint https://<device-ip>:8243 --manifest-file <manifest> --unlock-code <code>
aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventSource,AttributeValue=snowball.amazonaws.com --max-results 20
Read references/guardrails.md before concluding on any Snow Family issue.
Tool quick reference
| Tool / API |
When to use |
snowball list-jobs |
List all Snow Family jobs |
snowball describe-job |
Get job details and status |
snowball get-job-manifest |
Download device manifest |
snowball get-job-unlock-code |
Retrieve unlock code |
snowballEdge describe-device |
Get device status (on-device) |
snowballEdge describe-service |
Check service status on device |
snowballEdge list-ec2-instances |
List EC2 instances on device |
Gotchas: AWS Snow Family
- Snowball Edge client commands run LOCALLY on the device, not through AWS API. You must have network access to the device IP.
- Manifest files and unlock codes are job-specific. They expire when the job is completed or cancelled.
- S3 adapter on Snowball Edge is NOT the same as Amazon S3. It supports a subset of S3 API operations.
- EC2 instances on Snowball Edge use device-specific AMIs (sbe1 instance types). Standard EC2 AMIs do not work.
- Snowball Edge clusters require a minimum of 5 devices. Individual devices cannot join or leave a cluster after creation.
- OTA updates require the device to have internet connectivity. Disconnected devices cannot receive updates.
- Snowcone has significantly less storage (14 TB HDD or 14 TB SSD) compared to Snowball Edge (80 TB or 210 TB).
Anti-hallucination rules
- Always cite specific job IDs, device status, or Snowball Edge client output as evidence.
- Snowball Edge client commands and AWS CLI commands are different tools. Never conflate them.
- S3 adapter on Snow devices has limited API support. Never assume full S3 API compatibility.
- EC2 on Snow uses sbe1 instance types. Never suggest standard EC2 instance types.
- Spend no more than 2 minutes on any single hypothesis. Pivot if inconclusive.
14 runbooks
| Category |
IDs |
Covers |
| A — Device Setup |
A1-A2 |
Device ordering issues, device unlock failures |
| B — Data Transfer |
B1-B2 |
Data transfer errors, NFS share issues |
| C — Edge Compute |
C1-C2 |
Snowball Edge compute, EC2 on Snow |
| D — Storage |
D1-D2 |
S3 adapter errors, clustering issues |
| E — Networking |
E1-E2 |
Network configuration, optics connectivity |
| F — Maintenance |
F1-F2 |
OTA updates, device return shipping |
| G — Snowcone |
G1 |
Snowcone-specific issues |
| Z — Catch-All |
Z1 |
General troubleshooting |
1---2name: snowfamily-diagnostics3description: Use this skill to investigate and troubleshoot AWS Snow Family problems by analyzing device ordering, unlocking, data transfer, NFS shares, edge compute, EC2 on Snow, S3 adapter, clustering, networking, OTA updates, return shipping, and following structured runbooks. Covers Snowball, Snowball Edge, and Snowcone devices. Activate when: device ordering issues, unlock failures, data transfer errors, NFS problems, compute failures, S3 adapter errors, clustering issues, network problems, OTA update failures, shipping issues, or the user says something is wrong with Snow Family.4---56# AWS Snow Family Diagnostics78## When to use910Any AWS Snow Family investigation — device ordering, unlocking, data transfer, NFS shares, Snowball Edge compute, EC2 on Snow, S3 adapter, clustering, network configuration, optics, OTA updates, return shipping, or Snowcone-specific issues.1112## Investigation workflow1314### Step 1 — Collect and triage1516```17aws snowball list-jobs --query 'JobListEntries[*].{JobId:JobId,State:JobState,Type:JobType,CreationDate:CreationDate}'18aws snowball describe-job --job-id <job-id>19aws snowball list-cluster-jobs --cluster-id <cluster-id>20```2122### Step 2 — Domain deep dive2324```25aws snowball get-job-manifest --job-id <job-id>26aws snowball get-job-unlock-code --job-id <job-id>27snowballEdge describe-device --endpoint https://<device-ip>:8243 --manifest-file <manifest> --unlock-code <code>28```2930### Step 3 — Detailed investigation3132```33snowballEdge describe-service --service-id s3 --endpoint https://<device-ip>:8243 --manifest-file <manifest> --unlock-code <code>34snowballEdge list-ec2-instances --endpoint https://<device-ip>:8243 --manifest-file <manifest> --unlock-code <code>35aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventSource,AttributeValue=snowball.amazonaws.com --max-results 2036```3738Read `references/guardrails.md` before concluding on any Snow Family issue.3940## Tool quick reference4142| Tool / API | When to use |43|------------|-------------|44| `snowball list-jobs` | List all Snow Family jobs |45| `snowball describe-job` | Get job details and status |46| `snowball get-job-manifest` | Download device manifest |47| `snowball get-job-unlock-code` | Retrieve unlock code |48| `snowballEdge describe-device` | Get device status (on-device) |49| `snowballEdge describe-service` | Check service status on device |50| `snowballEdge list-ec2-instances` | List EC2 instances on device |5152## Gotchas: AWS Snow Family5354- Snowball Edge client commands run LOCALLY on the device, not through AWS API. You must have network access to the device IP.55- Manifest files and unlock codes are job-specific. They expire when the job is completed or cancelled.56- S3 adapter on Snowball Edge is NOT the same as Amazon S3. It supports a subset of S3 API operations.57- EC2 instances on Snowball Edge use device-specific AMIs (sbe1 instance types). Standard EC2 AMIs do not work.58- Snowball Edge clusters require a minimum of 5 devices. Individual devices cannot join or leave a cluster after creation.59- OTA updates require the device to have internet connectivity. Disconnected devices cannot receive updates.60- Snowcone has significantly less storage (14 TB HDD or 14 TB SSD) compared to Snowball Edge (80 TB or 210 TB).6162## Anti-hallucination rules63641. Always cite specific job IDs, device status, or Snowball Edge client output as evidence.652. Snowball Edge client commands and AWS CLI commands are different tools. Never conflate them.663. S3 adapter on Snow devices has limited API support. Never assume full S3 API compatibility.674. EC2 on Snow uses sbe1 instance types. Never suggest standard EC2 instance types.685. Spend no more than 2 minutes on any single hypothesis. Pivot if inconclusive.6970## 14 runbooks7172| Category | IDs | Covers |73|----------|-----|--------|74| A — Device Setup | A1-A2 | Device ordering issues, device unlock failures |75| B — Data Transfer | B1-B2 | Data transfer errors, NFS share issues |76| C — Edge Compute | C1-C2 | Snowball Edge compute, EC2 on Snow |77| D — Storage | D1-D2 | S3 adapter errors, clustering issues |78| E — Networking | E1-E2 | Network configuration, optics connectivity |79| F — Maintenance | F1-F2 | OTA updates, device return shipping |80| G — Snowcone | G1 | Snowcone-specific issues |81| Z — Catch-All | Z1 | General troubleshooting |
aws-samples