Amazon Import/Export Snowball

Name: Amazon Import/Export Snowball API
Brand: Amazon Import/Export Snowball
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageObject StorageapiKey26 EndpointsREST

For Agents

Manage AWS Snow Family data-transfer jobs from request to return shipping. Agents can create addresses, request import or export jobs, retrieve manifests and unlock codes, and track job status.

Quickstart

Get started with Amazon Import/Export Snowball in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create an aws snowball import job"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Amazon Import/Export Snowball API.

Create shipping addresses with CreateAddress so jobs can be sent to a physical site

Request import or export jobs against an S3 bucket using CreateJob

Group multiple devices into a Snowball Edge cluster with CreateCluster

Retrieve the encrypted job manifest and unlock code needed to access a device on arrival

GET STARTED

Start building with Amazon Import/Export Snowball API

Explore with Jentic

View OpenAPI Document

Use for: I need to create a Snowball job to import data into S3, Register a new shipping address for a Snowball delivery, Get the job manifest and unlock code for a Snowball device that arrived, List all Snowball jobs that are currently in transit

Not supported: Does not transfer data between regions over the network, manage S3 object lifecycle, or perform on-device data manipulation — use for ordering and tracking Snow Family physical data-transfer jobs only.

Jentic publishes the only available OpenAPI document for Amazon Import/Export Snowball, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Amazon Import/Export Snowball, keeping it validated and agent-ready. The Snow Family management API lets organisations create and track jobs that move large volumes of data between on-premises sites and Amazon S3 using physical Snowball, Snowball Edge, and Snowcone devices. Agents can create addresses, request jobs and clusters, fetch job manifests and unlock codes, generate return shipping labels, and manage long-term pricing arrangements. The 26 operations cover addresses, jobs, clusters, manifests, return shipping, and Snow device pricing.

Use Cases

Patterns agents use Amazon Import/Export Snowball API for, with concrete tasks.

★ Bulk Data Migration into Amazon S3

Enterprises moving petabyte-scale data into AWS use Snowball to ship physical devices rather than saturate their network. Operators CreateAddress, CreateJob with JobType=IMPORT and the destination S3 bucket, and use the returned JobId to fetch the manifest and unlock code via GetJobManifest and GetJobUnlockCode once the device arrives.

CreateAddress for the data centre, CreateJob with JobType=IMPORT, RoleARN, and S3 destination bucket, then GetJobManifest and GetJobUnlockCode once Status=IN_TRANSIT_TO_CUSTOMER.

Edge Computing Cluster for Disconnected Sites

Field operations (research vessels, remote installations) order Snowball Edge clusters to run compute and storage in environments without reliable internet. CreateCluster provisions multiple devices that operate as a unit, and DescribeCluster tracks shipment, deployment, and return status.

CreateCluster with JobType=LOCAL_USE, AddressId, and node count, then DescribeCluster periodically to track ClusterState moving from AwaitingQuorum to InUse.

Job Lifecycle Tracking and Return Logistics

Operations teams track Snowball job state across creation, shipping, customer use, and return — using ListJobs, DescribeJob, CreateReturnShippingLabel, and DescribeReturnShippingLabel. Agents can flag jobs that are overdue for return or generate replacement labels when one is lost.

ListJobs filtered by JobState=WITH_CUSTOMER, then for any job past its expected return date call CreateReturnShippingLabel and DescribeReturnShippingLabel to confirm generation.

AI Agent Operational Status via Jentic

AI agents using Jentic can answer fleet-management questions like 'which Snowball jobs are still active?' or 'what is the unlock code for job X?' by calling the Snowball API through Jentic. Searches by intent return the right operation, and vault-stored AWS credentials sign each call.

Search Jentic for 'list snowball jobs', execute ListJobs filtered by JobState=IN_TRANSIT_TO_AWS, and return JobId, JobState, and CreationDate for each.

Key Endpoints

26 endpoints — jentic publishes the only available openapi specification for amazon import/export snowball, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#X-Amz-Target=AWSIESnowballJobManagementService.CreateJob

Create an import, export, or local-use Snowball job

POST

/#X-Amz-Target=AWSIESnowballJobManagementService.CreateAddress

POST

/#X-Amz-Target=AWSIESnowballJobManagementService.DescribeJob

Fetch job state, shipping, and configuration

POST

/#X-Amz-Target=AWSIESnowballJobManagementService.GetJobManifest

Retrieve the encrypted manifest for a delivered device

POST

/#X-Amz-Target=AWSIESnowballJobManagementService.GetJobUnlockCode

Fetch the device unlock code

POST

/#X-Amz-Target=AWSIESnowballJobManagementService.CreateReturnShippingLabel

Generate a return shipping label for a completed job

POST

/#X-Amz-Target=AWSIESnowballJobManagementService.CancelJob

Cancel a Snowball job that has not yet shipped

POST

/#X-Amz-Target=AWSIESnowballJobManagementService.CreateJob

Create an import, export, or local-use Snowball job

POST

/#X-Amz-Target=AWSIESnowballJobManagementService.CreateAddress

POST

/#X-Amz-Target=AWSIESnowballJobManagementService.DescribeJob

Fetch job state, shipping, and configuration

POST

/#X-Amz-Target=AWSIESnowballJobManagementService.GetJobManifest

Retrieve the encrypted manifest for a delivered device

POST

/#X-Amz-Target=AWSIESnowballJobManagementService.GetJobUnlockCode

Fetch the device unlock code

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS access keys are stored encrypted in the Jentic vault. Snowball API calls are signed with SigV4 inside Jentic — the agent never holds the raw credentials.

Intent-based discovery

Agents search by intent (for example, 'create a snowball job' or 'list jobs in transit') and Jentic returns the matching Snowball operations with input schemas, so the agent invokes CreateJob or ListJobs without browsing AWS docs.

Time to first call

Direct Snowball integration: 1-2 days for IAM, SigV4 signing, manifest handling, and state machines around shipping. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

AWS Database Migration Service

Online database migration over the network rather than physical device shipping

Use DMS when bandwidth is sufficient and downtime must be minimised; reach for Snowball when network transfer would take too long

Complementary

AWS Backup

Centralised backup management; complements Snowball for ongoing protection after initial bulk import

Use Snowball for the one-time bulk migration into S3, then AWS Backup to protect the resulting data

Complementary

AWS Data Pipeline

Workflow scheduling that can orchestrate post-import processing of S3 data delivered by Snowball

Trigger Data Pipeline workflows once a Snowball import completes to transform the newly-loaded S3 objects

FAQs

Specific to using Amazon Import/Export Snowball API through Jentic.

Why is there no official OpenAPI spec for Amazon Import/Export Snowball?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon Import/Export Snowball via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Amazon Import/Export Snowball use?

Snowball uses AWS Signature Version 4 with IAM credentials and permissions on the snowball:* and importexport:* actions. Through Jentic, AWS keys are stored encrypted in the vault and signed into each call — the raw credentials never enter the agent's runtime.

Can I track a Snowball device after it ships to me?

Yes. DescribeJob returns the JobState (NEW, PREPARING_APPLIANCE, IN_TRANSIT_TO_CUSTOMER, WITH_CUSTOMER, IN_TRANSIT_TO_AWS, COMPLETE) along with shipping carrier and tracking number details. GetJobManifest and GetJobUnlockCode are required once the device is on site to access the encrypted contents.

What are the rate limits for the Amazon Import/Export Snowball?

Snowball applies standard AWS API throttling — most operations are limited to a few requests per second per account per region with brief burst capacity. Throttled requests return a ThrottlingException; clients should retry with exponential backoff.

How do I create a Snowball import job through Jentic?

Through Jentic, search for 'create a snowball import job', load the CreateJob schema, and execute with JobType=IMPORT, RoleARN, AddressId, and the Resources block listing destination S3 buckets. Jentic returns the JobId so the agent can poll DescribeJob until the device ships.

Is the Amazon Import/Export Snowball free?

Snowball charges per device-job (a service fee that includes 10 days of on-site use) plus shipping and per-day rental beyond the included period. Long-term pricing offers reduced rates for multi-year commitments; see https://aws.amazon.com/snowball/pricing/.