Agent-ready OpenAPI document · curated by JenticCRMCustomer SupportapiKey14 EndpointsREST
Know of an official OpenAPI document? Contribute it →
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://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Fsupport" | 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%2Fsupport" | 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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
AWS Support
- AI-Aware (B-)60/100
99
Foundational Compliance63
Developer Experience & Jentic Compatibility36
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
36
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
46%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring AWS Support by hand means computing SigV4 signatures against the us-east-1 support endpoint and routing calls through the X-Amz-Target action header yourself. Through Jentic you install once, import AWS Support from the API Directory, store the access keys once, and your agent calls it.
Permission scoping
AWS Support routes its actions through one endpoint by X-Amz-Target rather than resource ids in the path, so scope the agent to the operations it needs, such as CreateCase and DescribeCases. You choose the operations it may call, so ResolveCase is not included unless you add it.
Credential isolation
Your AWS access keys are stored once, encrypted, by your own Jentic One instance and used to sign each AWS Support request with SigV4 at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'open an AWS support case' or 'check a Trusted Advisor result', and Jentic returns the matching AWS Support operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
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 with Jentic One, the self-hosted execution layer.
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.
Can I limit what my agent is allowed to do with the AWS Support API?
Yes. Because you self-host Jentic One, your own rules decide which AWS Support operations the agent may call, and the API routes every action through a single endpoint by its X-Amz-Target header rather than by resource ids in the path, so you scope access per operation. You can allow the agent to run only the operations it needs, such as CreateCase and DescribeCases, while leaving ResolveCase out unless you explicitly add it. The AWS access keys stay with your Jentic One instance and are used to sign each request, so the agent never gains broader reach than the operations you granted.
GET STARTED