Wait for Route53 changes to propagate #34
Closed
Conversation
This file contains 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
Avoids these errors, which are caused by attempting to issue certs before records have propagated to all Route53 servers:
{
"type": "urn:ietf:params:acme:error:orderNotReady",
"detail": "Order's status (\"invalid\") is not acceptable for finalization",
"status": 403
}
Fixes ocelotconsulting#33
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.
Avoids these sporadic errors, which are caused by attempting to issue certs before records have propagated to all Route53 servers:
Waiting for the ChangeResourceRecordSets result to enter the INSYNC state ensures that the ACME server will see the new record regardless of which Route53 server it queries.
Fixes #33