AWS Route53 documentation change
Summary
Updated terminology from 'customer managed KMS key' to 'KMS key'
Security assessment
The change simplifies terminology but does not alter security guidance or address a security issue. DNSSEC-related content remains unchanged in substance.
Diff
diff --git a/Route53/latest/DeveloperGuide/dns-configuring-dnssec-enable-signing.md b/Route53/latest/DeveloperGuide/dns-configuring-dnssec-enable-signing.md index 4c5dca6d3..b0a51d7fb 100644 --- a//Route53/latest/DeveloperGuide/dns-configuring-dnssec-enable-signing.md +++ b//Route53/latest/DeveloperGuide/dns-configuring-dnssec-enable-signing.md @@ -88 +88 @@ You can enable DNSSEC signing and create a key-signing key (KSK) by using AWS CL -When you provide or create a customer managed KMS key, there are several requirements. For more information, see [Working with customer managed keys for DNSSEC](./dns-configuring-dnssec-cmk-requirements.html). +When you provide or create a KMS key, there are several requirements. For more information, see [Working with customer managed keys for DNSSEC](./dns-configuring-dnssec-cmk-requirements.html).