AWS Route53: Route53 Resolver SLR doc: wording cleanup and mandatory log config deletion
Summary
Rewords references from 'resolver query log configuration association' to 'resolver query log configuration' and changes the optional deletion of the query logging configuration to a required step.
Security assessment
The change is editorial around the AWSServiceRoleForRoute53Resolver service-linked role and query logging configuration; it makes deleting the logging configuration mandatory but introduces no new permission, policy, or vulnerability fix.
Evidence
+ 6. After logging queries has stopped, type `delete` in the field and choose **Delete** to delete the query logging configuration.
Diff
diff --git a/Route53/latest/DeveloperGuide/using-service-linked-roles.md b/Route53/latest/DeveloperGuide/using-service-linked-roles.md index 4aae329..d272c3a 100644 --- a//Route53/latest/DeveloperGuide/using-service-linked-roles.md +++ b//Route53/latest/DeveloperGuide/using-service-linked-roles.md @@ -72 +72 @@ You must configure permissions to allow an IAM entity (such as a user, group, or -You don't need to manually create a service-linked role. When you create a resolver query log configuration association in the Amazon Route 53 console, the AWS CLI, or the AWS API, VPC Resolver creates the service-linked role for you. +You don't need to manually create a service-linked role. When you create a resolver query log configuration in the Amazon Route 53 console, the AWS CLI, or the AWS API, VPC Resolver creates the service-linked role for you. @@ -78 +78 @@ This service-linked role can appear in your account if you completed an action i -If you delete this service-linked role, and then need to create it again, you can use the same process to recreate the role in your account. When you create a new Resolver query log configuration association, the `AWSServiceRoleForRoute53Resolver` service-linked role is created for you again. +If you delete this service-linked role, and then need to create it again, you can use the same process to recreate the role in your account. When you create a new Resolver query log configuration, the `AWSServiceRoleForRoute53Resolver` service-linked role is created for you again. @@ -106 +106 @@ This will disassociate the configuration from the VPC. You can also disassociate - 6. After logging queries has stopped, you can optionally type `delete` in the field and choose **Delete** to delete the query logging configuration. However, this is not necessary for deleting the resources used by `AWSServiceRoleForRoute53Resolver`. + 6. After logging queries has stopped, type `delete` in the field and choose **Delete** to delete the query logging configuration.