AWS Support
Browse all Amazonaws APIs★ Only Publicly Available OpenAPI DocumentCRMCustomer SupportapiKey14 EndpointsREST
For Agents
Open, update, and resolve AWS Support cases and pull Trusted Advisor check results so an agent can triage AWS issues and surface optimisation findings without leaving its workflow.
Use for: I want to open a new AWS support case for an outage, Add a comment and an attachment to an existing support case, List all open AWS support cases for my account, Resolve a support case once the issue is fixed
Not supported: Does not handle billing disputes, account creation, or service-level configuration — use for managing AWS Support cases and Trusted Advisor checks only.
Jentic publishes the only available OpenAPI specification for AWS Support, keeping it validated and agent-ready. The AWS Support API gives programmatic access to AWS Support cases and Trusted Advisor checks. It lets developers open and resolve support cases, attach files, post communications, list services and severity levels, and inspect Trusted Advisor recommendations across cost optimisation, security, fault tolerance, performance, and service limits. Access requires a Business, Enterprise On-Ramp, or Enterprise support plan, and 14 operations cover the full case lifecycle and Trusted Advisor refresh workflow.
Install Jentic One Beta
Connect the AWS Support to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Support, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: 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 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 Support API.
Open AWS support cases with service code, severity, and category via CreateCase
Attach diagnostic logs and screenshots to support cases through AddAttachmentsToSet
Post follow-up communications and read the case message history
Resolve cases programmatically once an incident is closed
Pull Trusted Advisor check results for cost, security, and limits
Trigger refreshes of stale Trusted Advisor checks
Enumerate available AWS services and severity levels for case routing
Use Cases
Patterns agents use AWS Support API for, with concrete tasks.
★ Automated Case Creation from Monitoring Alerts
When an internal alerting system detects an AWS-side issue (e.g. an EC2 instance stuck in stopping, a sudden RDS failover), automatically open a support case with the relevant service code, severity, and a pre-formatted description. CreateCase accepts a subject, communication body, service code, severity code, category code, and optional attachment set, returning a caseId that can be tracked in your incident tooling.
Call CreateCase with subject 'RDS failover took 12 minutes', serviceCode 'amazon-relational-database-service', severityCode 'high', categoryCode 'performance', and a communicationBody describing the impact, then return the caseId.
Trusted Advisor Compliance Reporting
Build a recurring report of Trusted Advisor findings across cost, security, fault tolerance, performance, and service limits. DescribeTrustedAdvisorChecks lists every available check; DescribeTrustedAdvisorCheckResult returns the flagged resources for a given checkId. Combine with RefreshTrustedAdvisorCheck to ensure findings are current before publishing the report.
Call DescribeTrustedAdvisorChecks, then for each check with category 'security' call RefreshTrustedAdvisorCheck and DescribeTrustedAdvisorCheckResult, and return the flagged resources.
Case Triage and Escalation Workflow
Triage incoming support cases by combining DescribeCases (filtered by status and afterTime) with DescribeCommunications to read the latest message thread. AddCommunicationToCase posts an internal update or customer reply; ResolveCase closes the ticket once the work is complete. Useful for support teams running their own dashboards on top of AWS Support.
Call DescribeCases with includeResolvedCases=false and afterTime set to 24 hours ago, return the case list with their latest communication body from DescribeCommunications.
Agent-Driven Support Case Management via Jentic
An on-call agent can use Jentic to open, comment on, and resolve AWS support cases without holding AWS keys. The agent submits an intent like 'open a high-severity case about RDS slow queries', Jentic loads the CreateCase schema, validates required fields, and returns a structured caseId. Subsequent updates flow through AddCommunicationToCase using the same vaulted credentials.
Through Jentic, search for 'open an aws support case', load the CreateCase schema, and execute it with serviceCode, severityCode, subject, and communicationBody.
Key Endpoints
14 endpoints — jentic publishes the only available openapi specification for aws support, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/#X-Amz-Target=AWSSupport_20130415.CreateCase
Open a new AWS support case
POST
/#X-Amz-Target=AWSSupport_20130415.DescribeCases
List or query support cases
POST
/#X-Amz-Target=AWSSupport_20130415.AddCommunicationToCase
Post a message on a case
POST
/#X-Amz-Target=AWSSupport_20130415.ResolveCase
Mark a support case as resolved
POST
/#X-Amz-Target=AWSSupport_20130415.DescribeTrustedAdvisorCheckResult
Return findings for a Trusted Advisor check
POST
/#X-Amz-Target=AWSSupport_20130415.RefreshTrustedAdvisorCheck
Force a refresh of a Trusted Advisor check
POST
/#X-Amz-Target=AWSSupport_20130415.CreateCase
Open a new AWS support case
POST
/#X-Amz-Target=AWSSupport_20130415.DescribeCases
List or query support cases
POST
/#X-Amz-Target=AWSSupport_20130415.AddCommunicationToCase
Post a message on a case
POST
/#X-Amz-Target=AWSSupport_20130415.ResolveCase
Mark a support case as resolved
POST
/#X-Amz-Target=AWSSupport_20130415.DescribeTrustedAdvisorCheckResult
Return findings for a Trusted Advisor check
POST
/#X-Amz-Target=AWSSupport_20130415.RefreshTrustedAdvisorCheck
Force a refresh of a Trusted Advisor check
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AWS access keys for AWS Support (used to compute the AWS Signature v4 HMAC in the Authorization header) are held encrypted in the Jentic vault. Agents receive scoped, short-lived execution permissions; the raw access key ID and secret access key never enter the agent's prompt or memory.
Intent-based discovery
Agents call Jentic with an intent like 'open an aws support case' and Jentic returns the matching AWS Support operation along with its input schema, so the agent can invoke the right action without parsing AWS service docs.
Time to first call
Direct integration with AWS Support: 2-4 days to wire up SigV4 signing, error handling, retries, and IAM scoping. Through Jentic: under an hour — search by intent, load the operation schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AWS Support API through Jentic.
Why is there no official OpenAPI spec for AWS Support?
AWS does not publish an OpenAPI specification for AWS Support; it ships Smithy models and language-specific SDKs instead. Jentic generates and maintains this OpenAPI spec so that AI agents and developers can call AWS Support 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 Support API use?
AWS Support uses SigV4 (HMAC-SHA256 over the request, sent in the Authorization header). The IAM principal must also have support:* permissions and the account must be on a Business, Enterprise On-Ramp, or Enterprise support plan. Through Jentic, your AWS keys stay in the vault and Jentic signs each request.
Can I open and resolve cases through the Support API?
Yes. CreateCase opens a case (you must supply a valid serviceCode and severityCode from DescribeServices and DescribeSeverityLevels). AddCommunicationToCase posts updates, and ResolveCase closes the case when the work is done.
What are the rate limits for the AWS Support API?
AWS Support is a regional service hosted only in us-east-1 with low default throughput intended for case management workflows, not high-volume polling. Expect burst limits of a few requests per second and back off on ThrottlingException responses.
How do I pull Trusted Advisor results through Jentic?
Search Jentic with 'list trusted advisor checks', load DescribeTrustedAdvisorChecks, then for each checkId of interest call RefreshTrustedAdvisorCheck followed by DescribeTrustedAdvisorCheckResult. Jentic returns the flagged resources as a structured response.
Do I need a paid AWS Support plan to call this API?
Yes. The Support API requires a Business, Enterprise On-Ramp, or Enterprise support plan. Calls from accounts on the Basic or Developer plan return a SubscriptionRequiredException.
Can I attach files to a support case via the API?
Yes. Call AddAttachmentsToSet to upload one or more files and receive an attachmentSetId, then pass that id to CreateCase or AddCommunicationToCase. DescribeAttachment retrieves the contents of an existing attachment.
GET STARTED