AWS Route53: Route53 managed policy adds scoped iam:CreateServiceLinkedRole
Summary
Documents a new iam:CreateServiceLinkedRole permission in AmazonRoute53FullAccess, constrained by a StringEquals condition on iam:AWSServiceName to route53healthchecks.amazonaws.com, plus a policy change-history entry.
Security assessment
The added IAM statement grants a privileged action (creating a service-linked role) but scopes it with a condition limiting the target service, which is least-privilege hardening guidance for an AWS managed policy rather than a fix for a specific vulnerability.
Evidence
+ "iam:AWSServiceName": "route53healthchecks.amazonaws.com"
Diff
diff --git a/Route53/latest/DeveloperGuide/security-iam-awsmanpol-route53.md b/Route53/latest/DeveloperGuide/security-iam-awsmanpol-route53.md index 098714c..6895aac 100644 --- a//Route53/latest/DeveloperGuide/security-iam-awsmanpol-route53.md +++ b//Route53/latest/DeveloperGuide/security-iam-awsmanpol-route53.md @@ -88,0 +89,2 @@ These permissions aren't required if you aren't using the Route 53 console. Rout + * `iam:CreateServiceLinkedRole` – Allows principals to create the service-linked role for health checking. This permission is needed when the service-linked role doesn't exist in the account yet. + @@ -135,0 +138,12 @@ JSON + }, + { + "Effect": "Allow", + "Action": [ + "iam:CreateServiceLinkedRole" + ], + "Resource": "*", + "Condition": { + "StringEquals": { + "iam:AWSServiceName": "route53healthchecks.amazonaws.com" + } + } @@ -509,0 +524 @@ Managed policy change history Change | Description | Date +AmazonRoute53FullAccess – Updated policy | Adds permission for `iam:CreateServiceLinkedRole`, limited to the `route53healthchecks.amazonaws.com` service. With this permission, principals can create the service-linked role for health checking when the role doesn't exist in the account yet. | October 08, 2026