Traffic policies and policy statements
A traffic policy is a container for policy statements that you assign to an ingress endpoint so that it can sort the incoming mail by allowing or blocking specific types of email when the conditions of the policy statements are met. A traffic policy can be used by multiple ingress endpoints.
Tip
You can think of a traffic policy as a "filter set", and a policy statement as a "filter". The traffic policy (filter set) contains polices (filters) that you use to filter your incoming mail.
When you create a traffic policy, you have the option to set a maximum message size (in bytes). When a message exceeds that size, it's immediately be discarded. This acts as a “first pass” filter when set. Next, you set the default action to allow or block email that falls outside of the conditions of your policy statements—think of this as a “catch all” action for the traffic policy.
Policy statements are also created with either an allow or block action that is taken when the statements' conditions are met. You build the conditions by selecting an email protocol and a conditional operator for a value you enter that must be matched by the incoming message before the policy statement will allow or block it. Each policy statement can have multiple conditions.
A traffic policy can contain multiple policy statements and executes them in an order that's based on the implicit hierarchy of how it evaluates email:
-
Maximum message size – If this optional parameter is set, any message greater than this size is immediately discarded, bypassing the policy statements.
-
Policy statements that block – These statements are evaluated first and block any message that meets the statement's conditions.
-
Policy statements that allow – These statements are evaluated next and allow any message that meets the statement's conditions.
-
Default action of traffic policy – The remainder of messages that fall outside of the policy statements are allowed or blocked based on how you've defined this parameter.
A traffic policy is an independent resource which can be used by more than one ingress endpoint, but policy statements belong exclusively to the traffic policy in which they were created. Thus, you must first create a traffic policy, or edit an existing one, before you can create policy statements to evaluate the email coming into your ingress endpoint.
The procedure in the next section explains how to create traffic policies and their policy statements in the SES console.
Creating traffic policies and policy statements in the SES console
The following procedure shows you how to use the Traffic policies page in the SES console to create traffic policies and their policy statements, and manage the ones you've already created.
To create and manage traffic policies and policy statements using the console
Sign in to the AWS Management Console and open the Amazon SES console at https://console.aws.amazon.com/ses/
. -
In the left navigation panel, choose Traffic policies under Mail Manager.
-
On the Traffic policies page, select Create traffic policy.
-
On the Create a traffic policy page, enter a unique name for your traffic policy.
-
(Optional) If you want to discard any messages above a certain size, enter a value in bytes in the Maximum message size field.
-
In Default action, choose whether the traffic policy is to either Allow or Deny (block) messages that fall outside of (are not addressed by) the conditions of your policy statements.
-
Select Add new policy statement to create a statement for your traffic policy.
-
Choose either Allow or Deny (block) for the action to be taken when the statement's conditions are met.
-
Build a condition by selecting an email protocol and a conditional operator for the value you enter. Select Add new condition if you want to add more conditions to this policy statement. To learn more about a condition property and its operators and valid values, see the Policy statement conditions reference.
-
If you're subscribed to an Email Add On, you'll be able to select it here as an email protocol.
-
-
If you want add more policy statements and conditions, repeat steps 7 - 9 above.
-
When you're done creating policy statements and their conditions, select Create traffic policy.
-
You can view and manage the traffic policies you've already created from the Traffic policies page. If there's an traffic policy you want to remove, select it's radio button followed by Delete.
-
To edit a traffic policy's properties or any of its policy statements, select its name to open its overview page, from here, select Edit.
-
In Traffic policy details, you can change the maximum message size and default action.
-
In any of the Policy statement containers, you can change the allow/deny property and edit any of the conditions. You can also remove policy statements and conditions, as well as add new ones.
-
When you're done with all your edits, save your changes by selecting Save changes.
Reference for policy statement conditions
Policy statement conditions
The following reference table lists all the policy statement protocols that are available to build a policy statement condition. Selecting a protocol's expression type will take you to its reference page in the SES Mail Manager API Reference that lists all the available operators and valid values for that protocol.
| Protocol | Expression type |
|---|---|
|
Recipient address |
|
|
Sender IP range |
|
|
TLS protocol version |
|
|
Abusix Mail Intelligence (if subscribed) Spamhaus Domain Block List (if subscribed) |
