AWS Mobile
Browse all Amazonaws APIsAgent-ready OpenAPI document · curated by JenticDeveloper ToolsCi Cdhmac9 EndpointsREST
Know of an official OpenAPI document? Contribute it →
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.
Use for: Create a Mobile Hub project for a new iOS app, List all Mobile Hub projects in the us-east-1 region, Get the SDK bundle for an Android client of project pId-abc123, Retrieve the resource details attached to a Mobile Hub project
Not supported: Does not handle mobile push delivery, in-app analytics events, or device testing - use for provisioning and tearing down AWS Mobile Hub backend projects and SDK bundles only.
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.
Install Jentic One Beta
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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Faws-mobile" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Faws-mobile" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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
Export a project YAML to clone its backend configuration into another region or account
Delete a Mobile Hub project and its tracked backend resources in a single call
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
POST
/bundles/{bundleId}
Generate a downloadable SDK bundle for a project
POST
/exports/{projectId}
Export a project's YAML configuration
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring AWS Mobile by hand means implementing Signature Version 4 signing, resolving the regional mobile host, and managing the project and bundle lifecycle yourself. Through Jentic you install once, import AWS Mobile from the API Directory, store the AWS keys once, and your agent calls it.
Permission scoping
AWS Mobile puts the project id in the URL path (/projects/{projectId}) and bundle id in /bundles/{bundleId}, so a rule can pin your agent to one project: it can read and export that project and nothing else. You choose the operations it may call, so DeleteProject is not included unless you add it.
Credential isolation
Your AWS access keys are stored once, encrypted, by your own Jentic One instance and each request is signed with Signature Version 4 at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a Mobile Hub project' or 'export an SDK bundle', and Jentic returns the matching AWS Mobile operation with its input schema, so the agent calls CreateProject or ExportBundle without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 with Jentic One, the self-hosted execution layer.
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 your Jentic One instance 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 API Directory) for newer features and ongoing investment.
Can I limit what my agent is allowed to do with the AWS Mobile API?
Yes. Jentic One is self-hosted, so your own rules decide which AWS Mobile operations and credentials your agent may use. Because the project id sits in the URL path (/projects/{projectId}) and the bundle id in /bundles/{bundleId}, you can pin the agent to a single project so it only describes and exports that one and touches nothing else. You choose the operations it may call, so a destructive call like DeleteProject is available only if you explicitly add it.
GET STARTED