AWS ses documentation change
Summary
Added DKIM configuration guidance and corrected 'signing length' typo
Security assessment
The DKIM CNAME record examples help prevent misconfigurations that could compromise email authentication security. While not fixing an active vulnerability, it improves security documentation quality. The typo fix ('singing' to 'signing') clarifies technical documentation.
Diff
diff --git a/ses/latest/dg/creating-identities.md b/ses/latest/dg/creating-identities.md index c05accf7f..f6d846cfc 100644 --- a//ses/latest/dg/creating-identities.md +++ b//ses/latest/dg/creating-identities.md @@ -154 +154 @@ Amazon SES only defaults to the assigned configuration set when no other set is - 8. (Optional) To configure customized DKIM-based verification, other than the SES default setting which uses [Easy DKIM](./send-email-authentication-dkim-easy.html) _with a 2048 bit singing length_ , under **Verifying your domain** , expand **Advanced DKIM settings** and choose the type of DKIM you want to configure: + 8. (Optional) To configure customized DKIM-based verification, other than the SES default setting which uses [Easy DKIM](./send-email-authentication-dkim-easy.html) _with a 2048 bit signing length_ , under **Verifying your domain** , expand **Advanced DKIM settings** and choose the type of DKIM you want to configure: @@ -281,0 +282,16 @@ When you publish (add) your public key to your DNS provider, it must be formatte +###### Tip + +When adding CNAME records to your DNS configuration: + + * Use the exact record names as provided in the SES console. + + * Do not add any additional underscores (`_`) at the beginning of the CNAME record names. + + * The `_domainkey` portion is part of the record name and should be used exactly as shown. + +Example showing correct vs incorrect CNAME Record implementation: + + * _Correct:_ `abc123._domainkey.domain.com` + + * _Incorrect:_ `_abc123._domainkey.domain.com` + @@ -324 +340 @@ Complete the following procedure to create an email address identity by using th - 2. In the navigation pane, under **Configuration** , choose **Verified identities**. + 2. In the navigation pane, under **Configuration** , choose **Identities**.