AWS Mobile

Name: AWS Mobile API
Brand: AWS Mobile
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi Cdhmac9 EndpointsREST

For Agents

Programmatically create and tear down AWS Mobile Hub projects, list configured backend resources, and download platform-specific SDK bundles for iOS, Android, and JavaScript.

Connect the AWS Mobile to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Mobile, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AWS Mobile API.

Create a mobile backend project that wires together Cognito, S3, Lambda, API Gateway, and Pinpoint resources from a single descriptor

List existing Mobile Hub projects in a region and inspect their attached resources

Fetch a project snapshot to see which backend services and ARNs are currently provisioned

Generate and download an SDK bundle scoped to a specific project for iOS Swift, Android, or JavaScript targets

GET STARTED

Start building with AWS Mobile API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for AWS Mobile, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AWS Mobile, keeping it validated and agent-ready. AWS Mobile Hub provisions and configures the AWS resources required to back a mobile app — identity pools, analytics, push messaging, storage, APIs and bot connectors — and packages SDK bundles that ship those resources to a developer desktop. Through the Mobile API, agents can create projects, list their backing resources, fetch a snapshot, request platform-specific bundles (iOS, Android, JavaScript) and tear down a project once it is no longer needed. The service is region-scoped and access is controlled with AWS SigV4 (hmac) credentials.

Use Cases

Patterns agents use AWS Mobile API for, with concrete tasks.

★ Provision a Mobile App Backend From a Project Descriptor

Front-end teams that need a backend wired up — auth, storage, analytics and push — can have an agent create a Mobile Hub project that provisions Cognito identity pools, S3 buckets, Pinpoint apps and Lambda integrations from a single project descriptor. The CreateProject endpoint accepts a YAML or JSON contents block and returns the project identifier, removing the need to click through the AWS console to wire each service up by hand.

Call POST /projects with a project name and a YAML contents block defining Cognito and Pinpoint resources, then return the projectId from the response

Distribute SDK Bundles To Mobile App Developers

Once a Mobile Hub project exists, mobile developers need the configured SDK to talk to those backend resources. An agent can list available bundles, then call ExportBundle scoped to a projectId and a target platform (iOS Swift, Android, JavaScript) to retrieve a download URL for a zipped SDK pre-wired with the project's resource ARNs and pool IDs. This removes the manual config-file step that mobile teams typically copy from the console.

List bundles via GET /bundles, then call POST /bundles/{bundleId} with platform=IOS_SWIFT and projectId to fetch a downloadUrl for the SDK archive

Audit and Tear Down Stale Mobile Backends

Cost and security reviews require visibility into which Mobile Hub projects still exist and what backend resources they hold. An agent can enumerate every project with ListProjects, fetch the resource snapshot for each with DescribeProject, and call DeleteProject on stale ones to reclaim Cognito pools, S3 buckets and Pinpoint apps. The flow is fully API-driven and avoids the per-resource cleanup that an agent would otherwise have to script across several AWS services.

Call GET /projects to list project summaries, then for each older than a threshold call GET /project#projectId followed by DELETE /projects/{projectId}

AI Agent Integration for Mobile Backend Lifecycle

Through Jentic, an AI coding agent can manage the full lifecycle of an AWS Mobile Hub project — create, describe, export, bundle, and delete — without browsing the AWS console or the boto3 reference. Jentic resolves natural-language intents like 'set up a mobile backend for an iOS chat app' to the right Mobile Hub operation, hands the agent the input schema, and brokers SigV4 credentials so raw AWS keys never enter the agent's context.

Resolve the intent 'create a mobile backend project' via Jentic search, load the CreateProject schema, and execute it with a project name and contents descriptor

Key Endpoints

9 endpoints — jentic publishes the only available openapi specification for aws mobile, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/projects

Create a Mobile Hub project from a descriptor

GET

/projects

List all Mobile Hub projects in the account

GET

/project#projectId

Describe a project's resources

DELETE

/projects/{projectId}

Delete a Mobile Hub project

GET

/bundles

List available SDK bundles

POST

/bundles/{bundleId}

Generate a downloadable SDK bundle for a project

POST

/exports/{projectId}

Export a project's YAML configuration

POST

/projects

Create a Mobile Hub project from a descriptor

GET

/projects

List all Mobile Hub projects in the account

GET

/project#projectId

Describe a project's resources

DELETE

/projects/{projectId}

Delete a Mobile Hub project

GET

/bundles

List available SDK bundles

Why though Jentic?

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

Credential isolation

AWS access keys are stored encrypted in the Jentic MAXsystem vault. Jentic signs each AWS Mobile request with SigV4 on the agent's behalf — the agent receives a scoped session, never the raw IAM access key or secret.

Intent-based discovery

Agents search by intent (e.g., 'create a Mobile Hub project') and Jentic returns the matching AWS Mobile operation with its input schema, so the agent can call CreateProject, ExportBundle or DeleteProject without browsing the AWS docs.

Time to first call

Direct AWS Mobile integration: 1-2 days for SigV4 signing, IAM policy scoping and SDK plumbing. Through Jentic: under an hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

AWS Amplify

AWS Amplify is the modern successor for hosting and provisioning mobile and web app backends

Choose Amplify for new projects — it has fuller features and ongoing AWS investment. Use AWS Mobile only for legacy Mobile Hub projects already provisioned through that service.

Complementary

AWS Amplify Backend

Amplify Backend manages the backend resources behind an Amplify-built mobile or web app

Use alongside Amplify when an agent needs fine-grained control of the backend resources (auth, API, storage) that an Amplify project provisions.

Complementary

Amazon Cognito Identity

Cognito Identity provides the user identity and federated auth that Mobile Hub projects wire into mobile clients

Use directly when the agent only needs to manage identity pools and federated logins for a mobile app, rather than provisioning a full Mobile Hub project.

Complementary

AWS Device Farm

Device Farm runs automated tests against the resulting mobile app on real devices

Use after building a client with the Mobile Hub SDK bundle — Device Farm validates the app on real iOS and Android hardware.

FAQs

Specific to using AWS Mobile API through Jentic.

Why is there no official OpenAPI spec for AWS Mobile?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Mobile 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 AWS Mobile API use?

AWS Mobile uses AWS Signature Version 4 (hmac) signing with an access key ID and secret access key scoped by IAM. Through Jentic, those AWS credentials are stored in the MAXsystem vault and used to sign requests on the agent's behalf — the raw access key never enters the agent's context.

Can I create a full mobile backend with one API call using AWS Mobile?

Yes. POST /projects accepts a contents block (YAML or JSON) describing Cognito identity, S3 storage, Pinpoint analytics and other backend services, and Mobile Hub provisions the underlying resources and returns a projectId. You then call POST /bundles/{bundleId} with that projectId to fetch a platform-specific SDK archive.

What are the rate limits for the AWS Mobile API?

AWS Mobile inherits standard AWS service throttling — quotas are per-account and per-region, and 429 responses include a retry-after hint. Specific TPS limits are not published in the spec; treat throttling as an expected error and apply exponential backoff.

How do I generate an Android SDK bundle through Jentic?

Use the Jentic search query 'generate a Mobile Hub SDK bundle', load the operation behind POST /bundles/{bundleId}, and execute it with platform=ANDROID and your projectId. Jentic returns the downloadUrl from the response so the agent can fetch the SDK archive in a follow-up step.

Is AWS Mobile being deprecated?

AWS has positioned AWS Amplify as the successor for new mobile and web app backends. AWS Mobile Hub is still callable for existing projects, but for greenfield work consider the Amplify or Amplify Backend APIs (also in the Jentic catalogue) for newer features and ongoing investment.