AWS Route53: Document record set protection behavior during accelerated recovery failover
Summary
Adds notes that protections persist across accelerated recovery toggling, that protection API calls may be throttled during the toggle, and that protections cannot be created, deleted, or listed during failover.
Security assessment
The added line documents that existing record set protections (a control preventing unauthorized or accidental DNS record changes) remain enforced during failover, which is security-relevant operational guidance but not a fix for a specific vulnerability.
Evidence
+ 6. You can't create, delete, or list record set protections during failover. Protections that exist before failover remain in effect.
Diff
diff --git a/Route53/latest/DeveloperGuide/accelerated-recovery.md b/Route53/latest/DeveloperGuide/accelerated-recovery.md index 102c55b..9082f30 100644 --- a//Route53/latest/DeveloperGuide/accelerated-recovery.md +++ b//Route53/latest/DeveloperGuide/accelerated-recovery.md @@ -74 +74,5 @@ There are a few more things to know about the accelerated recovery feature: - 5. During failover, these API methods will still work for public hosted zones with accelerated recovery. All other Route 53 API methods won't work until failback. + 5. Record set protections stay in effect when you turn accelerated recovery on or off. While you turn accelerated recovery on or off, requests to create or delete protections can fail with a `Throttling` error. Retry after a short wait. For more information about record set protections and accelerated recovery, see [Record set protections and accelerated recovery](./rrset-protection.html#rrset-protection-accelerated-recovery). + + 6. You can't create, delete, or list record set protections during failover. Protections that exist before failover remain in effect. + + 7. During failover, these API methods will still work for public hosted zones with accelerated recovery. All other Route 53 API methods won't work until failback.