AWS Route53: Remove record set protection quotas from Route 53 limits
Summary
Deletes the record set protections quota row and the entire 'Number of elements in record set protection requests' section, including Create/Delete/List protection element limits.
Security assessment
This removes documentation of quota limits for the record set protection feature; it is a documentation cleanup with no security vulnerability, credential, or exposure content.
Evidence
-Record set protections | 10,000 per hosted zone To request a higher quota, contact AWS Support. Protections can exist on names that have no records, so this quota is separate from the quota on records.
Diff
diff --git a/Route53/latest/DeveloperGuide/DNSLimitations.md b/Route53/latest/DeveloperGuide/DNSLimitations.md index 5a2e763..896a47d 100644 --- a//Route53/latest/DeveloperGuide/DNSLimitations.md +++ b//Route53/latest/DeveloperGuide/DNSLimitations.md @@ -101 +100,0 @@ Geoproximity records | 30 records that have the same name and type -Record set protections | 10,000 per hosted zone To request a higher quota, contact AWS Support. Protections can exist on names that have no records, so this quota is separate from the quota on records. @@ -284,2 +282,0 @@ Amazon Route 53 API requests are subject to the following maximums. - * Number of elements in record set protection requests - @@ -305,14 +301,0 @@ The sum of the number of characters (including spaces) in all `Value` elements i -### Number of elements in record set protection requests - -The following limits apply to the number of protections in record set protection requests and responses: - -**`CreateResourceRecordSetProtections` and `DeleteResourceRecordSetProtections` requests** - - -A request must contain at least 1 and at most 100 protections. - -**`ListResourceRecordSetProtections` responses** - - -A response contains at most 300 protections per page. -