AWS Route53 documentation change
Summary
Fixed redundant phrasing in KMS key documentation
Security assessment
Corrects a typo ('customer managed customer managed key' to 'customer managed key'). No security implications identified.
Diff
diff --git a/Route53/latest/DeveloperGuide/dns-configuring-dnssec-ksk.md b/Route53/latest/DeveloperGuide/dns-configuring-dnssec-ksk.md index 6a9f7d2c5..b5e332efd 100644 --- a//Route53/latest/DeveloperGuide/dns-configuring-dnssec-ksk.md +++ b//Route53/latest/DeveloperGuide/dns-configuring-dnssec-ksk.md @@ -30 +30 @@ When you enable DNSSEC signing, Route 53 creates a key-signing (KSK) for you. Yo -When you create a KSK, you must provide or request Route 53 to create a customer managed customer managed key to use with the KSK. When you provide or create a customer managed customer managed key, there are several requirements. For more information, see [Working with customer managed keys for DNSSEC](./dns-configuring-dnssec-cmk-requirements.html). +When you create a KSK, you must provide or request Route 53 to create a customer managed key to use with the KSK. When you provide or create a customer managed key, there are several requirements. For more information, see [Working with customer managed keys for DNSSEC](./dns-configuring-dnssec-cmk-requirements.html). @@ -44 +44 @@ Follow these steps to add a KSK in the AWS Management Console. - 5. Enter the alias for a customer managed customer managed key that applies to DNSSEC signing, or enter an alias for a new customer managed customer managed key that Route 53 will create for you. + 5. Enter the alias for a customer managed key that applies to DNSSEC signing, or enter an alias for a new customer managed key that Route 53 will create for you.