AWS acm documentation change
Summary
Adjusted renewal check from 60 to 45 days pre-expiration and modified event notification schedule
Security assessment
Operational timing changes for renewal processes. Removed 45-day event notification but no security implications or vulnerability fixes mentioned.
Diff
diff --git a/acm/latest/userguide/http-renewal-validation.md b/acm/latest/userguide/http-renewal-validation.md index 39a23e43b..f4eb42b5e 100644 --- a//acm/latest/userguide/http-renewal-validation.md +++ b//acm/latest/userguide/http-renewal-validation.md @@ -9 +9 @@ ACM provides automated managed renewal for certificates that were originally iss -At 60 days prior to expiration, ACM checks for the following renewal criteria: +At 45 days prior to expiration, ACM checks for the following renewal criteria: @@ -20 +20 @@ If these criteria are met, ACM considers the domain names validated and renews t -ACM sends AWS Health events and Amazon EventBridge events if it can't automatically validate a domain during renewal. These events are sent at 45 days, 30 days, 15 days, seven days, three days, and one day prior to expiration. For more information, see [Amazon EventBridge support for ACM](./supported-events.html). +ACM sends AWS Health events and Amazon EventBridge events if it can't automatically validate a domain during renewal. These events are sent at 30 days, 15 days, seven days, three days, and one day prior to expiration. For more information, see [Amazon EventBridge support for ACM](./supported-events.html).