Amazon SES Sending Authorization Policies - Amazon Simple Email Service Classic

This is the user guide for Amazon SES Classic. Updates and new features are only being documented in the new Amazon SES Developer Guide which we recommend to use.

Amazon SES Sending Authorization Policies

To enable another AWS account, Identity Access and Management (IAM) user, or AWS service to send email through Amazon SES on your behalf, you create a sending authorization policy, which is a JSON document that you attach to an identity that you own. The policy explicitly lists who you're allowing to send for that identity, and under which conditions. All senders except you and the entities that you explicitly grant permissions to in the policies are denied. An identity can have no policy, one policy, or multiple policies attached to it. You can also have one policy with multiple statements to achieve the effect of multiple policies.

Policies can be simple, or can be configured to provide fine-grained control. For example, if you owned, you could write a simple policy to grant AWS ID 123456789012 permission to send from that domain. A more detailed policy could specify that AWS ID 123456789012 can send email only from and only within a specified date range.

Amazon SES sending authorization policies apply to email sending APIs (SendEmail, SendRawEmail, SendTemplatedEmail, and SendBulkTemplatedEmail) only. They don't enable a user to access your AWS account in any other way.

Policy Structure

Each sending authorization policy is a JSON document that is attached to an identity. Each policy includes the following sections:

  • Policy-wide information at the top of the document.

  • One or more individual statements, each of which describes a set of permissions.

The following example policy grants AWS account ID 123456789012 permission to send from the verified domain

{ "Id":"ExampleAuthorizationPolicy", "Version":"2012-10-17", "Statement":[ { "Sid":"AuthorizeAccount", "Effect":"Allow", "Resource":"arn:aws:ses:us-east-1:123456789012:identity/", "Principal":{ "AWS":[ "123456789012" ] }, "Action":[ "ses:SendEmail", "ses:SendTemplatedEmail", "ses:SendRawEmail", "ses:SendBulkTemplatedEmail" ] } ] }

You can find more sending authorization policy examples at Sending Authorization Policy Examples.

Policy Elements

This section describes the elements contained in sending authorization policies. First we describe policy-wide elements, and then we describe elements that apply only to the statement in which they are included. We follow with a discussion of how to add conditions to your statements.

For specific information about the syntax of the elements, see Grammar of the IAM Policy Language in the IAM User Guide.

Policy-Wide Information

There are two policy-wide elements: Id and Version. The following table provides information about these elements.




Valid Values


Uniquely identifies the policy.


Any string


Specifies the policy access language version.


Any string. As a best practice, we recommend that you include this field with a value of "2012-10-17".

Statements Specific to the Policy

Sending authorization policies require at least one statement. Each statement can include the elements described in the following table.




Valid Values


Uniquely identifies the statement.


Any string.


Specifies the result that you want the policy statement to return at evaluation time.


"Allow" or "Deny".


Specifies the identity to which the policy applies. This is the email address or domain that the identity owner is authorizing the delegate sender to use.


The Amazon Resource Name (ARN) of the email identity.


Specifies the AWS account, IAM user, or AWS service that receives the permission in the statement.


A valid AWS account ID, IAM user ARN, or AWS service. AWS account IDs and IAM user ARNs are specified using "AWS" (for example, "AWS": ["123456789012"] or "AWS": ["arn:aws:iam::123456789012:root"]). AWS service names are specified using "Service" (for example, "Service": [""]).

For examples of the format of IAM user ARNs, see the AWS General Reference.


Specifies the email sending action that the statement applies to.


"ses:SendEmail", "ses:SendRawEmail", "ses:SendTemplatedEmail", "ses:SendBulkTemplatedEmail"

You can specify one or more of these operations. You can also specify "ses:Send*" to encompass all of these operations. If the delegate sender plans to send email by using the SMTP interface, you have to specify "ses:SendRawEmail", or use "ses:Send*".


Specifies any restrictions or details about the permission.


See the information about conditions following this table.


A condition is any restriction about the permission in the statement. The part of the statement that specifies the conditions can be the most detailed of all the parts. A key is the specific characteristic that's the basis for access restriction, such as the date and time of the request.

You use both conditions and keys together to express the restriction. For example, if you want to restrict the delegate sender from making requests to Amazon SES on your behalf after July 30, 2019, you use the condition called DateLessThan. You use the key called aws:CurrentTime and set it to the value 2019-07-30T00:00:00Z.

You can use any of the AWS-wide keys listed at Available Keys in the IAM User Guide, or you can use one of the following keys specific to Amazon SES:

Condition Key



Restricts the recipient addresses, which include the To:, "CC", and "BCC" addresses.


Restricts the "From" address.


Restricts the contents of the string that is used as the "From" display name (sometimes called "friendly from"). For example, the display name of "John Doe <>" is John Doe.


Restricts the "Return Path" address, which is the address where bounce and complaints can be sent to you by email feedback forwarding. For information about email feedback forwarding, see Amazon SES notifications sent by email.

You can use the StringEquals and StringLike conditions with Amazon SES keys. These conditions are for case-sensitive string matching. For StringLike, the values can include a multi-character match wildcard (*) or a single-character match wildcard (?) anywhere in the string. For example, the following condition specifies that the delegate sender can only send from a "From" address that starts with invoicing and ends with

"Condition": { "StringLike": { "ses:FromAddress": "invoicing*" } }

You can also use the StringNotLike condition to prevent delegate senders from sending email from certain email addresses. For example, you can disallow sending from, as well as similar addresses such as "admin",, or, by including the following condition in your policy statement:

"Condition": { "StringNotLike": { "ses:FromAddress": "*admin*" } }

For more information about how to specify conditions, see IAM JSON Policy Elements: Condition in the IAM User Guide.

Policy Requirements

Policies must meet all of the following requirements:

  • Each policy has to include at least one statement.

  • Each policy has to include at least one valid principal.

  • Each policy has to specify one resource, and that resource has to be the ARN of the identity that the policy is attached to.

  • Identity owners can associate up to 20 policies with each unique identity.

  • Policies can't exceed 4 kilobytes (KB) in size.

  • Policy names can't exceed 64 characters. Additionally, they can only include alphanumeric characters, dashes, and underscores.