Repository navigation
Conversation
AWS Certificate Manager can now run a managed ACME server which issues publicly trusted certificates to clusters outside the AWS managed services. It uses External Account Binding and pre-approved domain validation instead of live HTTP-01 or DNS-01 challenges, so it needs a different Issuer configuration from Let's Encrypt. Add a tutorial covering the AWS setup, the Issuer and Certificate configuration, and the failure modes specific to this server. The page carries a warning that it has not yet been verified against a live endpoint. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Richard Wall <richard@the-moon.net>
cert-manager-prow
Bot
added
do-not-merge/work-in-progress
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
cert-manager-prow
Bot
added
the
size/L
✅ Deploy Preview for cert-manager ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
bmsiegel
reviewed
Nov 5, 2026
| --query 'EndpointUrl' --output text | ||
| ``` | ||
|
|
||
| The URL has the form `https://acm-acme-enroll.<region>.api.aws/<endpoint-id>/directory`. |
There was a problem hiding this comment.
The slug here is not , it's a different uuid
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Preview:
AWS Certificate Manager (ACM) now offers a managed ACME server which issues publicly trusted certificates to workloads outside the AWS managed services. AWS names cert-manager as a supported client. This PR adds a tutorial showing how to use it.
Why a separate page?
The server behaves differently from Let's Encrypt in three ways that affect cert-manager configuration:
valid, so cert-manager skips Challenge creation (seebuildPartialRequiredChallenges). The Issuer needs no solvers.Not yet verified
I have not run this against a live ACM ACME endpoint. The steps come from the AWS documentation and from reading the cert-manager Order controller. The page says so in a warning at the top. Two things in particular need checking before this is merged:
MacKeyreturned byget-acme-external-account-binding-credentialscan be stored in the Secret as-is, or needs the base64 URL re-encoding described in the EAB docs.processingwithRetry-Afterduring the two minute issuance window, as the tutorial assumes, rather than holding the finalize request open past cert-manager's 90 second HTTP timeout.I will remove the draft status once someone has run it end to end.
[Claude Fable 5.1]