canonical: https://jentic.com/apis/amazonaws.com/acm # AWS Certificate Manager Jentic publishes the only available OpenAPI specification for AWS Certificate Manager, keeping it validated and agent-ready. AWS Certificate Manager (ACM) provisions, manages, and deploys SSL/TLS certificates for AWS resources such as Elastic Load Balancers, CloudFront distributions, and API Gateway endpoints. The API exposes 15 operations covering certificate request, import, listing, deletion, tagging, and account-level configuration, so platform teams can automate certificate lifecycle and avoid expiry-related outages. ## For AI agents Provision, list, import, and delete SSL/TLS certificates for AWS resources, and manage tags and account-level configuration through 15 ACM operations. ## Scope Does not handle DNS hosting, web application firewall rules, or KMS key management - use for SSL/TLS certificate issuance, import, and lifecycle on AWS only. ## Capabilities - Request public ACM certificates for one or more domain names with DNS or email validation - Import third-party certificates into ACM so they can be deployed onto AWS load balancers and CloudFront - List and describe issued certificates with their domain coverage, validation state, and expiry - Export private certificates from ACM Private CA in PEM format with passphrase protection - Tag certificates for cost allocation and apply account-level transparency-logging configuration ## Use cases ### Automate Public Certificate Issuance Platform teams use ACM to issue and renew public SSL/TLS certificates for production domains without manual intervention. The RequestCertificate operation creates a new certificate for the requested domain names, and ACM auto-renews validated public certificates before expiry. Combining DNS validation with Route 53 means the entire issuance flow can be automated end to end in a few seconds, with renewal handled silently behind the scenes. Example prompt: Call RequestCertificate with DomainName=api.example.com and ValidationMethod=DNS, then poll DescribeCertificate until Status is ISSUED ### Certificate Inventory and Expiry Monitoring Security teams use ListCertificates and DescribeCertificate to maintain an inventory of issued and imported certificates, surfacing those approaching expiry. ACM tags returned by ListTagsForCertificate let the inventory be filtered by environment or owner so notifications can be routed to the right team well before an outage risk. Example prompt: Call ListCertificates, then DescribeCertificate for each ARN, and report any certificate with NotAfter within the next 30 days ### Import Third-Party Certificates Teams using a non-Amazon certificate authority use ImportCertificate to bring an externally issued PEM certificate, private key, and chain into ACM so it can be deployed onto AWS load balancers and CloudFront. Reissuance from the third party is followed by another ImportCertificate call against the same ARN, which keeps existing AWS resources bound to the same certificate identity. Example prompt: Call ImportCertificate with Certificate, PrivateKey, and CertificateChain in PEM format, then attach the returned ARN to a load balancer listener ### AI Agent Certificate Operator An AI agent invoked through Jentic operates ACM as part of a wider deploy workflow: it requests a certificate for a new domain, validates it via DNS, and reports the resulting ARN back to a deploy pipeline. The agent searches Jentic for the request-certificate operation, loads its schema, and executes calls without needing to handle SigV4 signing manually. Example prompt: Search Jentic for request a public ssl certificate, load the RequestCertificate operation, execute it for the target domain, and return the ARN ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /#X-Amz-Target=CertificateManager.RequestCertificate | Request a new public ACM certificate for one or more domains | | POST | /#X-Amz-Target=CertificateManager.ListCertificates | List certificates in the account | | POST | /#X-Amz-Target=CertificateManager.DescribeCertificate | Get detailed metadata for a certificate by ARN | | POST | /#X-Amz-Target=CertificateManager.ImportCertificate | Import a third-party certificate into ACM | | POST | /#X-Amz-Target=CertificateManager.DeleteCertificate | Delete a certificate that is not associated with any AWS resource | | POST | /#X-Amz-Target=CertificateManager.ExportCertificate | Export a private certificate including its private key in PEM format | ## Key resources - **Certificates** — Request, import, list, describe, and delete public and imported SSL/TLS certificates - **Certificate Validation** — Resend domain validation emails and inspect validation status for pending certificates - **Tags** — Add, remove, and list tags on certificates for cost allocation and ownership tracking - **Account Configuration** — Read and update account-level certificate transparency logging preferences ## Why Jentic - **Setup:** Wiring AWS Certificate Manager by hand means computing an AWS Signature Version 4 for every request, resolving the acm.{region}.amazonaws.com host for your region, and setting the X-Amz-Target header for each operation. Through Jentic you install once, import AWS Certificate Manager from the API Directory, store your AWS access key and secret once, and your agent calls it. - **Permission scoping:** ACM operations carry the certificate ARN in the request body rather than the URL path, so limit the agent to the operations it needs, such as RequestCertificate, ListCertificates, and DescribeCertificate. You choose which operations it may call, so destructive ones like DeleteCertificate or ExportCertificate, which returns a private key, are not included unless you add them. - **Credential handling:** Your AWS access key and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'request an SSL certificate' or 'list certificates in the account', and Jentic returns the matching ACM operation with its input schema so the agent does not have to know the X-Amz-Target operation-name format. ## Related APIs - **Amazon API Gateway** — API Gateway custom domain names use ACM certificates for TLS termination - **Amazon Route 53** — Route 53 hosts the DNS records used by ACM for DNS-based domain validation - **Cloudflare** — Cloudflare provides its own certificate issuance and management for resources fronted by Cloudflare ## FAQ ### Why is there no official OpenAPI spec for AWS Certificate Manager? AWS does not publish an OpenAPI specification for ACM; the official surface is the AWS SDKs and the Smithy model behind them. Jentic generates and maintains this spec so that AI agents and developers can call AWS Certificate Manager 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 Certificate Manager API use? ACM uses AWS Signature Version 4 (SigV4) signed with an IAM access key id and secret access key, optionally with a session token for temporary credentials. Through Jentic the access key id and secret access key are stored encrypted in the vault and SigV4 signing is performed server side, so the agent never sees the raw secret access key. ### Can I auto-renew imported certificates with the AWS Certificate Manager API? No. ACM only auto-renews certificates that ACM itself issued. Imported certificates must be reissued by the original certificate authority and then ImportCertificate called again against the same ARN to update the cryptographic material while preserving the binding to existing AWS resources. ### What are the rate limits for the AWS Certificate Manager API? ACM applies per-region throttling that varies by operation: read operations like ListCertificates and DescribeCertificate are throttled at higher rates than write operations like RequestCertificate and ImportCertificate. Persistent throttling returns ThrottlingException; back off with exponential delay and retry. ### How do I request a public certificate with the AWS Certificate Manager API through Jentic? Install the SDK with pip install jentic, search Jentic for request a public ssl certificate, load the RequestCertificate operation schema, and execute it with DomainName and ValidationMethod=DNS. Jentic handles SigV4 signing for you and returns the new certificate ARN, which you can then poll with DescribeCertificate. ### Can I export the private key of an ACM certificate? Only for certificates issued by ACM Private CA, via the ExportCertificate operation, which requires a passphrase to encrypt the exported key. Public ACM-issued certificates cannot have their private keys exported by design - they can only be deployed to integrated AWS services. ### Can I limit what my agent is allowed to do with the AWS Certificate Manager API? Yes. Because Jentic One is self-hosted, your own rules decide which ACM operations and credentials the agent may use, so you can restrict it to read-and-request operations like ListCertificates, DescribeCertificate, and RequestCertificate. ACM carries the certificate ARN in the request body rather than the URL path, so scoping is done at the operation level: destructive operations such as DeleteCertificate, and ExportCertificate which returns a private key, are excluded unless you explicitly add them. Your AWS access key and secret stay with your own instance and are injected only at execution time, so the agent can only call the operations you have granted it.