AWS Security ChangesHomeSearch

AWS Route53: Removal of Route 53 record set protection documentation page

Service: Route53 · 2026-11-11 · Documentation medium

File: Route53/latest/DeveloperGuide/rrset-protection.md · Type: iam

Summary

The entire page documenting Route 53 record set protections was deleted. The removed content described how protections block ChangeResourceRecordSets requests (CREATE, DELETE, UPSERT) for protected name/type pairs, the console/CLI workflows (CreateResourceRecordSetProtections, DeleteResourceRecordSetProtections, ListResourceRecordSetProtections), error handling, CloudTrail logging, and IAM guidance for restricting who can remove protections. With the file emptied, all guidance on this change-control security feature is gone from the Developer Guide.

Security assessment

The deleted page documented a defense-in-depth control that prevents accidental or unauthorized modification/deletion of critical DNS records (e.g., apex A, MX, NS, SOA) by any principal, including those with route53:*, and it gave explicit IAM hardening guidance (limit route53:DeleteResourceRecordSetProtections, use SCPs) plus CloudTrail logging coverage. No CVE, vulnerability, or incident is referenced in the diff, so this is a documentation removal rather than a fix for a specific weakness; however, removing this access-control/hardening guidance is security-adjacent and warrants medium severity.

Evidence

-  * A protection is only as strong as your control over `route53:DeleteResourceRecordSetProtections`. Grant it to a small set of administrators, and consider denying it to everyone else, for example with a service control policy.

Diff

diff --git a/Route53/latest/DeveloperGuide/rrset-protection.md b/Route53/latest/DeveloperGuide/rrset-protection.md
index 77cbb16..8b13789 100644
--- a//Route53/latest/DeveloperGuide/rrset-protection.md
+++ b//Route53/latest/DeveloperGuide/rrset-protection.md
@@ -1 +0,0 @@
-[View a markdown version of this page](rrset-protection.md)
@@ -3,303 +1,0 @@
-[](/pdfs/Route53/latest/DeveloperGuide/route53-dg.pdf#rrset-protection "Open PDF")
-
-[Documentation](/index.html)[Amazon Route 53](/route53/index.html)[Developer Guide](Welcome.html)
-
-How record set protections workManaging record set protections by using the Route 53 consoleManaging record set protections by using the AWS CLIChanging records that are protectedDeleting a hosted zone that has protectionsRecord set protections and accelerated recoveryPermissions for record set protectionsTroubleshooting record set protection errors
-
-# Protecting records from changes
-
-To prevent a critical record from being changed or deleted by mistake, add a record set protection for its name and type. While the protection exists, Route 53 rejects any `ChangeResourceRecordSets` request that would create, update, or delete those records. The protection applies to every user and role, including users with full Route 53 permissions. To change a protected record, you first delete its protection.
-
-Use protections for records that rarely change and that would cause an outage if someone changed them by mistake, such as the apex records of a production domain, mail exchanger (MX) records, or records that route traffic to critical endpoints.
-
-###### Topics
-
-  * How record set protections work
-
-  * Managing record set protections by using the Route 53 console
-
-  * Managing record set protections by using the AWS CLI
-
-  * Changing records that are protected
-
-  * Deleting a hosted zone that has protections
-
-  * Record set protections and accelerated recovery
-
-  * Permissions for record set protections
-
-  * Troubleshooting record set protection errors
-
-
-
-
-## How record set protections work
-
-  * You identify a protection by a record name and a record type in one hosted zone, for example `www.example.com` and `A`.
-
-  * A protection covers every record with that name and type, whatever its set identifier. For example, if `www.example.com` has three weighted `A` records, one protection on `www.example.com` `A` protects all three. You can't protect only some of those records.
-
-  * You can create a protection for a name and type that has no records yet. The protection reserves that name and type: no one can create a record with that name and type until you delete the protection. Reserved names appear in the list of protections but not in the list of records.
-
-  * Route 53 checks protections for every change in a `ChangeResourceRecordSets` request, for `CREATE`, `DELETE`, and `UPSERT`. If any change in the request affects a protected name and type, Route 53 rejects the whole request and makes none of the changes.
-
-  * Route 53 doesn't reject a change that would not modify anything. For example, an `UPSERT` whose values are identical to the existing record succeeds without changing the record.
-
-  * You can add an optional comment of up to 256 characters to each protection. Route 53 includes the comment in the error message when it rejects a change, so use the comment to tell people why the record is protected and whom to contact.
-
-  * You can't update a protection. To change its comment, delete the protection and create it again.
-
-  * You can use protections in public and private hosted zones.
-
-  * You can't delete a hosted zone that has protections. Delete the protections first. For more information about deleting a hosted zone that has protections, see Deleting a hosted zone that has protections.
-
-  * Requests to create and delete protections are all-or-nothing. Each request either adds or removes every protection in the request, or none of them.
-
-  * Protections don't change how Route 53 answers DNS queries. They only control changes to records.
-
-
-
-
-The following details explain how record set protections behave in specific situations:
-
-**Record types that you can protect**
-    
-
-You can protect every record type that `ChangeResourceRecordSets` accepts, including the NS and SOA records at the zone apex.
-
-**Who can remove a protection**
-    
-
-Any principal that has the `route53:DeleteResourceRecordSetProtections` permission on the hosted zone can delete any protection in that zone. A protection is only as strong as the IAM policies that control that permission. For more information about these permissions, see Permissions for record set protections.
-
-**Records that Route 53 manages**
-    
-
-Protections apply to changes that you request. A protection on the apex NS or SOA records blocks your changes to them, but it doesn't prevent Route 53 from updating those records as it manages the hosted zone.
-
-**Other services and tools**
-    
-
-When an AWS CloudFormation stack, the AWS CLI, or an AWS SDK changes a protected record, the change fails with the same `InvalidChangeBatch` error.
-
-**Logging**
-    
-
-CloudTrail logs requests to create, delete, and list protections. For more information, see [Logging Amazon Route 53 API calls with AWS CloudTrail](./logging-using-cloudtrail.html).
-
-## Managing record set protections by using the Route 53 console
-
-The hosted zone details page has a **Protections** tab. On the **Records** tab, the **Protection** column shows whether each record is protected. When a record is protected, the console disables **Edit** and **Delete** for it and explains that you must remove the protection first.
-
-###### To add a protection
-
-  1. Sign in to the AWS Management Console and open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/).
-
-  2. In the navigation pane, choose **Hosted zones** , and then choose the name of the hosted zone.
-
-  3. On the **Protections** tab, choose **Add protection**.
-
-  4. Enter the following values:
-
-     * **Record name** – The subdomain to protect, without the hosted zone name. Leave it blank to protect the zone apex.
-
-     * **Record types** – One or more record types. The console creates one protection for each type.
-
-     * (Optional) **Comment** – Why the record is protected. This text appears in error messages when Route 53 blocks a change.
-
-  5. Choose **Add protection**.
-
-
-
-
-If a protection already exists for a selected type, the console reports **`A protection already exists for`name` (`type`)`** and adds none of the protections.
-
-**To protect records when you create them** – On the create record page, in the **Protection** section, select **Enable protection**. The console creates the records and then adds the protections. If you see a message that the records were created but aren't protected, add the protection on the **Protections** tab. You can add protection to at most 100 records in one submission.
-
-###### To remove a protection
-
-  1. On the hosted zone's **Protections** tab, select one or more protections.
-
-  2. Choose **Remove protection**.
-
-  3. Review the records that will be unprotected. A protection covers all records with the same name and type.
-
-  4. To confirm, type `confirm`, and then choose **Remove protection**.
-
-
-
-
-The console removes the selected protections in one request of up to 100. If any one of them fails, the console removes none of them.
-
-**To view protections** – Choose the **Protections** tab. The table shows **Record name** , **Record type** , **Protection type** , and **Comment**.
-
-## Managing record set protections by using the AWS CLI
-
-To manage protections programmatically, use the [CreateResourceRecordSetProtections](https://docs.aws.amazon.com/Route53/latest/APIReference/API_CreateResourceRecordSetProtections.html), [DeleteResourceRecordSetProtections](https://docs.aws.amazon.com/Route53/latest/APIReference/API_DeleteResourceRecordSetProtections.html), and [ListResourceRecordSetProtections](https://docs.aws.amazon.com/Route53/latest/APIReference/API_ListResourceRecordSetProtections.html) actions. The following examples use the AWS CLI.
-
-**Create protections**
-
-The following command creates two protections at the apex of the `example.com` hosted zone: one for the `A` records, with a comment, and one for the `MX` records.
-    
-    
-    aws route53 create-resource-record-set-protections \
-        --hosted-zone-id Z1D633PJN98FT9 \
-        --protections '[{"RecordName":"example.com","RecordType":"A","Comment":"Production apex. Contact the DNS team before changing."},{"RecordName":"example.com","RecordType":"MX"}]'
-
-Each element of `--protections` has the following values:
-
-**`RecordName`**
-    
-
-The name of the records to protect. Specify the full name, such as `www.example.com`.
-
-**`RecordType`**
-    
-
-The type of the records to protect, such as `A` or `MX`.
-
-**`Comment`**
-    
-
-(Optional) Up to 256 characters that explain why the records are protected. Route 53 includes the comment in the error message when it rejects a change.
-
-A successful request returns an empty response.
-
-**List protections**
-
-The following command lists the protections in the hosted zone.
-    
-    
-    aws route53 list-resource-record-set-protections \
-        --hosted-zone-id Z1D633PJN98FT9
-
-Example output:
-    
-    
-    {
-        "ResourceRecordSetProtections": [
-            {
-                "RecordName": "example.com.",
-                "RecordType": "A",
-                "Comment": "Production apex. Contact the DNS team before changing."
-            },
-            {
-                "RecordName": "example.com.",
-                "RecordType": "MX"
-            }
-        ]
-    }
-
-Route 53 returns `RecordName` in fully qualified form with a trailing dot, as `ListResourceRecordSets` does.
-
-**Delete protections**