AWS ses documentation change
Summary
Restructured examples for Email Add Ons usage, including Spamhaus and Trend Micro integrations
Security assessment
The changes document security-related features (spam/virus filtering) but do not address a specific security vulnerability.
Diff
diff --git a/ses/latest/dg/eb-addons.md b/ses/latest/dg/eb-addons.md index a66e431ca..27685bb9d 100644 --- a/ses/latest/dg/eb-addons.md +++ b/ses/latest/dg/eb-addons.md @@ -31 +31 @@ The following procedure shows you how to use the **Email Add Ons** page in the M - 4. Once you’ve subscribed to an Add On, you’ll be able to integrate it into your email workflow by selecting it as a traffic policy condition to deny or allow email into your ingress endpoint, or a rule set condition to determine an action to take on qualifying messages. The following examples depict using an Add On in a policy statement condition and in a rule condition: + 4. Once you’ve subscribed to an Add On, you’ll be able to integrate it into your email workflow by selecting it as a traffic policy condition to deny or allow email into your ingress endpoint, or a rule set condition to determine an action to take on qualifying messages. @@ -33 +33,5 @@ The following procedure shows you how to use the **Email Add Ons** page in the M - * Using the **Spamhaus Domain Block List** Add On in a policy statement condition to block email coming into your ingress endpoint that originates from a domain listed in Spamhaus: +The following examples depict using an Add On in a policy statement condition and in a rule condition: + +###### Traffic policy example using an Add On + +Using the **Spamhaus Domain Block List** Add On in a policy statement condition to block email coming into your ingress endpoint that originates from a domain listed in Spamhaus: @@ -37 +41,3 @@ The following procedure shows you how to use the **Email Add Ons** page in the M - * For details on how to create traffic policies and build policy statement conditions with Email Add Ons, see [Creating traffic policies and policy statements in the SES console](./eb-filters.html#eb-filters-create-console). +For details on how to create traffic policies and build policy statement conditions with Email Add Ons, see [Creating traffic policies and policy statements in the SES console](./eb-filters.html#eb-filters-create-console). + +###### Rule condition example using an Add On @@ -39 +45 @@ The following procedure shows you how to use the **Email Add Ons** page in the M - * Using the **Trend Micro Virus Scanning** Add On in a rule condition to determine a rule action for email that passes the virus scan: +Using the **Trend Micro Virus Scanning** Add On in a rule condition to determine a rule action for email that passes the virus scan: @@ -43 +49 @@ The following procedure shows you how to use the **Email Add Ons** page in the M - * For details on how to create rule sets and build rule conditions with Email Add Ons, see [Creating rule sets and rules in the SES console](./eb-rules.html#eb-rules-create-console). +For details on how to create rule sets and build rule conditions with Email Add Ons, see [Creating rule sets and rules in the SES console](./eb-rules.html#eb-rules-create-console).