Q: What is Amazon Simple Email Service (Amazon SES)?
Amazon Simple Email Service (Amazon SES) is a highly scalable and cost-effective email service for businesses and developers. Amazon SES eliminates the complexity and expense of building an in-house email solution or licensing, installing, and operating a third-party email service for this type of email communication. In addition, the service integrates with other AWS services, making it easy to send emails from applications being hosted on AWS. With Amazon SES there is no long-term commitment, minimum spend or negotiation required — businesses can utilize a free usage tier, and beyond that pay only low fees for the number of emails sent or received plus data transfer fees.
Q: Who should use Amazon SES?
Any business or developer that needs a reliable, scalable, and inexpensive way to send or receive email — without having to build their own solution or license, install, and operate third-party software.
Q: What kinds of email can I send via Amazon SES?
You should send email that recipients expect and appreciate, and that comply with applicable laws and regulations, and the AWS Customer Agreement (including the AWS Acceptable Use Policy). Amazon SES can reliably deliver merchandising, subscription, transactional, and notification email messages.
Q: How does Amazon SES help ensure reliable email delivery?
For high email deliverability, Amazon SES uses content filtering technologies to scan a business's outgoing email messages to help ensure that the content meets ISP standards. To help businesses further improve the quality of email communications with their customers, Amazon SES provides a built-in feedback loop that includes bounce, complaint, and delivery notifications.
Q: What prevents Amazon SES users from sending spam?
Amazon SES uses in-house content filtering technologies to scan email content for spam and malware. In exceptional cases, accounts identified as sending spam or other low-quality email may be suspended, or AWS may take such other action as it deems appropriate. When malware is detected, Amazon SES prevents these emails from being sent.
Q: Do I need to sign up for Amazon EC2 or any other AWS services to use Amazon SES?
Amazon SES users do not need to sign up for any other AWS services. Any application with Internet access can use Amazon SES to deliver email, whether that application runs in your own data center, within Amazon EC2, or as a client software solution.
Q: How is Amazon SES different from Amazon SNS?
Amazon SES is for applications that need to send arbitrary communications via email. Amazon SES supports custom email header fields, and many MIME types.
By contrast, Amazon Simple Notification Service (Amazon SNS) is for messaging-oriented applications, with multiple subscribers requesting and receiving "push" notifications of time-critical messages via a choice of transport protocols, including HTTP, Amazon SQS, and email. The body of an Amazon SNS notification is limited to 8192 characters of UTF-8 strings, and is not intended to support multimedia content.
Q: How can I get started using Amazon SES?
To use Amazon SES, you simply:
- Sign Up: After signing up, you can access the Amazon SES sandbox – an environment specifically designed for developers to test and evaluate the service.
- Verify Domains or Email Addresses: Before you can send email via Amazon SES, you need to verify that you own the domain or address from which you’ll be sending email. To start the verification process, visit the Amazon SES console.
- Apply to Increase Your Sending Limits: Once you are ready to use Amazon SES to send email, you can apply to raise your sending limits and move your account out of the sandbox environment. It only takes a few minutes to apply, and you usually receive a response within 24 hours.
- Send Email: You can use either SMTP or the Amazon SES API to queue an email message for delivery.
- Get Feedback: Amazon SES provides useful statistics about your sending activities. With a simple query or Amazon SES console visit, you can quickly obtain vital statistics such as volume sent, bounces and complaints.
For more information about how to set up and use Amazon SES, see the Amazon SES Developer Guide.
Q: What should I do after I'm finished testing and evaluating Amazon SES?
Once you are ready to use Amazon SES to send email, you can request an Amazon SES sending limit increase in Support Center. If granted, this increase will move your account out of the sandbox environment so that you can begin sending email to your customers. You will no longer need to verify recipient email addresses or recipient domains, and you will be able to send much larger quantities of email.
To request a sending limit increase, please complete our brief request form in Support Center. We generally respond to these requests within 24 hours.
Q: Do I need to set up reverse DNS records in order to use Amazon SES?
Amazon SES users do not need to do this. Amazon Web Services manages the IP addresses used by Amazon SES, and provides reverse DNS records for these addresses.
Q: I am sending email using my own mail servers hosted on Amazon EC2. Do I have to start using Amazon SES instead?
Amazon SES does not affect any Amazon EC2-based solution that you may currently have. You can continue to use your existing solution, or use Amazon SES, or do both at the same time.
Q: Does Amazon SES provide an SMTP endpoint?
Yes. Amazon SES provides a full-featured SMTP interface for seamless integration with applications that can send email via SMTP. You can connect directly to this SMTP interface from your applications, or configure your existing email server to use this interface as an SMTP relay.
To connect to the Amazon SES SMTP interface, you must create SMTP credentials. To create your credentials, go to the Amazon SES console and click the SMTP link.
Q: How can I use the Amazon SES SMTP interface?
To use the Amazon SES SMTP interface, all you need are your SMTP username and password, the SMTP endpoint name, and the port number. Using this information, you can connect to the Amazon SES SMTP interface in the same manner as any other SMTP relay.
For example, you can integrate your existing packaged software so that it sends email through Amazon SES. You can add email sending capability to your applications, using a programming language that supports SMTP. You can integrate Amazon SES sending with popular mail transfer agents (MTAs) such as Sendmail, Postfix, and Exim. You can even connect to the SMTP interface from the command line, and send SMTP commands directly.
For more information about the SMTP interface, go to the Amazon SES Developer Guide.
Q: What are the available API operations for sending email?
In addition to SMTP sending support, Amazon SES provides the following APIs: SendEmail and SendRawEmail. These two APIs provide different levels of control over the composition of the actual email message. Both APIs provide the same level of email sending reliability and performance:
- The SendEmail API requires the user to provide only a source address, destination address, message subject, and message body. Upon calling this API, Amazon SES will automatically construct and send a properly formatted multi-part MIME email message optimized for display by email client software.
- The SendRawEmail API provides the advanced user with flexibility to format and send their own raw email message by specifying headers, MIME parts, and content types.
Q: Can I use Amazon SES to send bulk email?
Yes. Simply call the SendEmail or SendRawEmail APIs repeatedly for each email you would like to send. Software running on Amazon EC2, Amazon Elastic MapReduce, or your own servers can compose and deliver bulk emails via Amazon SES in whatever way best suits your business. If you already have your own bulk mailing software, it's easy to update it to deliver through Amazon SES — either by modifying the software to directly call Amazon SES, or reconfiguring it to deliver email through an Amazon SES SMTP relay as described above.
Q: Can Amazon SES send emails with attachments?
Yes. Amazon SES supports many popular content formats, including documents, images, audio, and video.
You can send email with attachments by using an email client that supports SMTP. When you configure such a client to send outgoing email through Amazon SES, the client constructs the appropriate MIME parts and email headers before sending the message. All of this happens automatically in your client with no additional user intervention.
You can also send email with attachments programmatically. To include an attachment in your email, construct a new multipart email message. In this message, include a MIME part that contains an appropriate Content-Type header, along with the MIME-encoded content. Next, use the Content-Disposition header to specify whether the content is to be displayed inline or treated as an attachment.
Once you have constructed your message, you can send it using the SendRawEmail API; you can also use the AWS Software Development Kits (SDKs) or a third-party library such as boto for Python.
To learn more about attachment pricing for Amazon SES, please see Amazon SES Pricing.
Q: How do I control the character encoding of my emails with Amazon SES?
The SMTP protocol requires that all data be sent in 7-bit ASCII format. If you want to use a different character encoding with the Amazon SES SMTP interface, you will need to apply your desired encoding to your subject and body, and then convert them to a valid 7-bit ASCII message before sending it to the SMTP endpoint.
The SendEmail API accepts UTF-8 subject and body inputs, transcodes them into whatever format you specify via an optional encoding parameter, and automatically converts the resulting content into 7-bit ASCII with appropriate encoded-word syntax and content-transfer-encoding headers before transmission. The SendRawEmail API requires you to apply your desired encoding to your subject and body and then convert them to a valid 7-bit ASCII message before submitting each request.
Q: What happens if I try to send a malformed email message or send an email that is disallowed for any other reason?
If Amazon SES determines that it is unable to deliver your message it will return an error specifying that delivery failed and providing the reason. In rare cases, Amazon SES may not detect the problem with your email until after accepting your request. In such cases, your email will be returned to you as a bounce with a corresponding error code and reason.
Q: Does Amazon SES support Sender Policy Framework (SPF)?
Yes. However, you do not need to make any changes to your DNS records for your emails to pass SPF authentication because Amazon SES sends your emails from a "Mail-From" domain that Amazon SES owns.
Q: Does Amazon SES support Domain Keys Identified Mail (DKIM)?
Yes. Amazon SES will DKIM-sign outgoing messages on your behalf if you have Easy DKIM configured and enabled. For more information on how to configure Easy DKIM and other DKIM topics, go to the Amazon SES Developer Guide.
If you wish, you can also DKIM-sign your email yourself. To ensure maximum deliverability, there are a few DKIM headers that you should not sign. For more information, go to the Amazon SES Developer Guide.
Q: Does Amazon SES send email over an encrypted connection using Transport Layer Security (TLS)?
Yes. If the receiving mail server advertises the STARTTLS extension, Amazon SES will attempt to upgrade the connection to a TLS connection. If that fails, Amazon SES will fall back to plain text.
Q: What TLS version does Amazon SES use to send email?
Amazon SES only supports TLS v1.
Q: Can I test Amazon SES responses without sending email to real recipients?
Yes. The Amazon SES mailbox simulator provides an easy way to test your sending rate and generic email responses, including bounces and complaints, without sending to actual recipients. Emails to the mailbox simulator do not affect your bounce and complaint metrics, and do not count against your sending quota.
For more information on the Amazon SES mailbox simulator, go to the Amazon SES Developer Guide.
Q: How long will it take for emails sent via Amazon SES to arrive?
Generally, Amazon SES attempts to deliver emails to the Internet within a few seconds of each request. However, due to a number of factors and the inherent uncertainties of the Internet, we cannot predict with certainty when your email will arrive nor the exact route the message will take to get to its destination. For example, an ISP might be unable to deliver the email to the recipient because of a temporary condition such as "mailbox full." In these cases, Amazon attempts to retry the message for a length of time. If the error is permanent, such as "mailbox does not exist," Amazon SES does not retry the delivery attempt and you will receive a hard bounce notification. You can set up delivery notifications to alert you when Amazon SES successfully delivers one of your emails to a recipient's mail server. For troubleshooting delivery issues, see the Amazon SES Developer Guide.
Q: Does Amazon SES guarantee receipt of my emails?
Amazon SES closely monitors ISP guidelines worldwide to help ensure that legitimate, good quality email will be delivered reliably to recipient inboxes. However, neither Amazon SES nor any other email-sending service can guarantee that emails will be received. ISPs can drop or lose email messages, recipients can accidentally provide the wrong email address, and if recipients do not wish to receive your email messages, ISPs may choose to reject or silently drop them.
Q: Do the AWS Software Development Kits contain support for Amazon SES?
Yes. You can use the AWS Software Development Kits (SDKs) for Android, iOS, Java, .NET, Node.js, Python, PHP, and Ruby to access the Amazon SES API. These SDKs make it easy to email-enable your applications, allowing them to send email with a simple API call.
Q: How do I make requests to Amazon SES?
Amazon SES accepts Query requests over HTTPS. These requests use verbs such as GET or POST, and a parameter named Action to indicate the action being performed. For security reasons, Amazon SES does not support HTTP requests; you must use HTTPS instead.
Q: Can I use Amazon SES for email-to-text delivery?
Yes. For example, if you know the email address associated with a mobile phone, you can use Amazon SES to send an email message to an SMS gateway, and the message will be delivered to the phone.
Q: Can I use Amazon SES to send email from my existing applications?
Yes. The Amazon SES Developer Guide provides instructions for configuring common mail transfer agents (MTAs) to use Amazon SES as an email transport. By following these instructions, you can create a private SMTP relay for use with any existing SMTP client software. This includes any software that you write, or any third-party software that supports SMTP, such as content management and database management systems.
Q: How does Amazon SES send bounce, complaint, and delivery notifications to me?
Amazon SES forwards bounce and complaint notifications to you by email or sends them to an Amazon SNS topic, depending on your configuration. Delivery notifications, which are triggered when Amazon SES successfully delivers one of your emails to a recipient’s mail server, are sent to you only through Amazon SNS.
Q. Where does Amazon SES send my bounce, complaint, and delivery notifications?
Delivery notifications are available through Amazon SNS. Bounces and complaints can be sent to you by email, through Amazon SNS, or both. If you choose to receive bounce and complaint notifications by email, Amazon SES will send you your bounce and complaint notifications based on the following logic:
If you used the SMTP interface to send the message, then notifications go to the address specified in SMTP's required MAIL FROM command, which overrides any Return-Path header specified in the SMTP DATA.
If you used the SendEmail API action to send the message, then:
- If you specified SendEmail's optional ReturnPath parameter, then notifications go to the specified address.
- Otherwise, notifications go to the address specified in SendEmail's required Source parameter, which populates the From: header of the message.
If you used the SendRawEmail API action to send the message, then:
- If you specified SendRawEmail's optional Source parameter, then notifications go to that address, overriding any Return-Path header specified in the raw message.
- Otherwise, if the Return-Path header was specified in the raw message, then notifications go to that address.
Otherwise, notifications go to the address in the From: header of the raw message.
Q. What actions should I take if I receive a bounce or a complaint?
You will need to analyze each bounce and complaint email or Amazon SNS JSON object that you receive to determine the cause. Bounces are usually caused by attempting to send to a nonexistent recipient; complaints arise when the recipient indicates that they do not want to receive your message. In either case, we recommend that you stop sending to these email addresses.
Q. Is there an additional cost to use Amazon SNS to receive bounce, complaint, and delivery notifications?
You will incur normal Amazon SNS expenses if you use it for bounce, complaint, and/or delivery notifications. Please see Amazon SNS Pricing for information about their free tier and full details about their pricing.
Q. When can I expect to be notified of bounces, complaints, and deliveries?
After an ISP sends a bounce or complaint to Amazon SES, we will usually pass it to you within a few seconds via Amazon SNS or email. However, we may not receive the bounce or complaint notification from the recipient’s ISP for a period of time ranging from seconds to weeks or longer, depending on how quickly the ISP notifies us. Delivery notifications are published as soon as Amazon SES delivers an email to a recipient’s mail server. In most cases, email sent through Amazon SES is delivered within seconds, but occasionally it might take longer.
Q: Will I be affected by any bounces or complaints that are caused by other Amazon SES users?
Even if other Amazon SES users cause bounces or complaints, your ability to send email should remain unchanged.
There is one exception. Whenever a recipient address generates a hard bounce for any Amazon SES user, Amazon SES considers that address to be invalid, and adds the address to the Amazon SES suppression list. In the next 14 days, any email sent by any Amazon SES user to that address is treated like a hard bounce. Like any hard bounce, suppression list bounces count towards your sending quota and your bounce rate. For details, go to the Amazon SES Developer Guide.
Q: What if I’m sure that a recipient address on the Amazon SES suppression list is valid?
You can submit a suppression list removal request using the Amazon SES console. For more information, see the Amazon SES Developer Guide.
Q: Are there limits as to whom I can send emails to?
As described in the AWS Customer Agreement (including the AWS Acceptable Use Policy), each user is responsible for remaining compliant with applicable laws and regulations. Further, each user is responsible for sending only email that recipients want and expect to receive. AWS may suspend any accounts identified as sending spam or other unwanted low-quality email, or take other action as AWS deems appropriate.
Q: Can I send emails from any source email address?
Yes. You can specify any "From" address in the email messages that you send using Amazon SES, but to prevent phishing, you must demonstrate your ownership and control of each email address or domain that you send from. Otherwise, your email will not be accepted for delivery. You can verify ownership and control of email addresses and domains by using either the Amazon SES console or the Amazon SES API. For details on address verification and domain verification, see the Amazon SES Developer Guide.
You can verify a total of up to 1000 email addresses and domains, in any combination.
Q: Is there a limit on the size of emails Amazon SES will deliver?
Amazon SES will accept email messages up to 10 MB in size. This includes any attachments that are part of the message.
Q: Is there a limit on the number of recipients per email message?
Amazon SES lets you specify a maximum of 50 recipients for every message you send. In other words, the combined number of To:, CC:, and BCC: recipients must not exceed 50. If you need to send an email message to more than 50 recipients, then you need to send multiple messages, each addressed to 50 recipients or fewer.
Q: Are there any limits on how many emails I can send?
Every Amazon SES sender has a unique set of sending limits, which are calculated by Amazon SES on an ongoing basis:
Sending quota — the maximum number of emails you can send in a 24-hour period.
Maximum send rate — the maximum number of emails that Amazon SES can accept from your account per second.
Note: The rate at which Amazon SES accepts your messages might be less than the maximum send rate.
New Amazon SES users start in the Amazon SES sandbox, which is a test environment that has a sending quota of 200 emails per 24-hour period, at a maximum rate of 1 email per second. To request an increase in these limits, you can submit an SES Sending Limits Increase case at any time.
Sending limits are based on recipients rather than on messages. You can check your sending limits at any time by using the Amazon SES console.
Note that if your email is detected to be of poor or questionable quality (e.g., high complaint rates, high bounce rates, spam, or abusive content), Amazon SES might temporarily or permanently reduce your permitted send volume, or take other action as AWS deems appropriate.
Q: Why are these sending limits in place?
Using these limits to steadily "ramp up" your sending activity helps you improve your deliverability. This approach helps Amazon SES adapt to your particular sending needs. As you continue to send high-quality email, Amazon SES adjusts to your particular usage patterns, and gradually increases your sending limits. You can also submit an SES Sending Limits Increase case at any time if you anticipate needing to raise your sending limits.
Q: How can I monitor the email I send using Amazon SES?
Use the Amazon SES console to proactively identify and monitor your sending activity. The console displays the number of emails you've sent, the maximum number of emails you can currently send per 24-hour period, and the per-second rate at which you can send them.
The Amazon SES console also lets you view the number of bounces, complaints, and emails rejected due to spam filtering events. The data is aggregated over the past two weeks, and is divided into 15-minute intervals. If these numbers are increasing, they can signify problems with the quality of your email. In the case of a dramatic decline in quality, Amazon SES may be forced to suspend sending your emails without prior notice, or take other action as AWS deems appropriate.
Q: How do I get set up to receive mail using Amazon SES?
You must first verify your domain with Amazon SES to prove that you own it by using the procedure described in the documentation. This process is identical to the domain verification process Amazon SES uses for sending mail. If you are already using your domain to send mail with Amazon SES, you do not need to verify it again. Once you have successfully verified your domain, the next step is to publish a DNS mail exchanger (MX) record for your domain that points to the regional Amazon SES endpoint that you want to use to receive email. Publishing the MX record is not required to receive mail through Amazon SES, but you must do so if you want your incoming mail to be automatically routed to Amazon SES, rather than route it yourself. The final step is to create a receipt rule using Amazon SES's console or API. A receipt rule tells Amazon SES what you'd like done with the mail received on your behalf. A basic rule would simply write all of your mail to an Amazon S3 bucket you own.
Q: What happens when Amazon SES receives my mail?
When Amazon SES receives a message, it references your active receipt rule set to determine whether or not you have any rules that match any of the incoming message's recipients. If there aren't any matches, or if the mail was sent from an IP address on your IP address block list, Amazon rejects the mail synchronously in the SMTP conversation. Otherwise, Amazon SES accepts the mail. After Amazon SES accepts the mail, it evaluates your active receipt rule set, and all of the receipt rules that apply to the message are applied in the order that they are defined.
Amazon SES's next steps are determined by the actions you defined in your receipt rules. You can set up your receipt rule to have Amazon SES deliver your messages to an Amazon S3 bucket, call your custom code via an AWS Lambda function, or publish notifications to Amazon SNS. You can also configure Amazon SES to drop or bounce messages you do not want to receive.
Q: How do I access my mail in Amazon S3?
When you set up a receipt rule to specify that Amazon SES should write your messages to an Amazon S3 bucket, you have the option of setting up Amazon SNS notifications as well. The notifications, which contain general information about the message and the action taken on it, will include the unique message ID of the message. Use this message ID to retrieve the corresponding message from Amazon S3.
Q: How can I process emails I receive?
There are two ways to process mail that you receive. You can either write an application that listens for Amazon SNS notifications from Amazon SES, retrieves the mail from Amazon S3, and processes it. Alternatively, you can write a custom AWS Lambda function. The AWS Lambda event contains all of the metadata about the message that was received, but does not include the actual message content. If you need access to the message content from within the AWS Lambda, then you need to first write the message to Amazon S3 using an Amazon S3 action before your AWS Lambda action is evaluated. AWS Lambda actions can be executed synchronously or asynchronously, depending on whether or not the AWS Lambda function needs to return a result that influences how other actions are executed. We recommend that you use asynchronous unless synchronous is absolutely necessary for your use case.
Q: Can multiple different AWS accounts receive mail on the same domain?
Yes. It is valid for more than one AWS account to receive mail for the same domain. This means that for each email that arrives on the shared domain, a copy of the message is processed by each account's receipt rule set independently.
Q: How can I encrypt my emails?
Amazon SES integrates with AWS Key Management Service (KMS) to optionally encrypt the mail that it writes to your Amazon S3 bucket. You can either use the default Amazon SES KMS master key in your account for encryption, which does not require additional setup, or you can set up a new master KMS key that grants the Amazon SES service principal permission to generate data keys. Amazon SES uses client-side encryption to encrypt your mail prior to writing it to Amazon S3. This means that it is necessary for you to decrypt the content on your side after retrieving the mail from Amazon S3. The AWS Java SDK and AWS Ruby SDK provide a client that is able to handle the decryption for you.
Q: What can I do about incoming email that was sent over an unencrypted connection?
Within the receipt rules you set up, you can specify for Amazon SES to reject mail from connections that don't use Transport Layer Security (TLS).
Q: What spam protections are in place?
Amazon SES has a number of different spam protection measures in place. It uses block lists to prevent mail from known spammers from even entering the system. Every email Amazon SES accepts undergoes virus and spam scanning. Amazon SES makes the verdicts available to you, enabling you to ultimately decide whether or not you trust the message. In addition to the spam and virus verdicts, Amazon SES provides the DKIM and SPF check results.
Q: Am I billed for spam?
You are not billed for any mail that's rejected during the SMTP conversation, so it's to your advantage to reject as much unwanted mail as possible at that time. Currently, Amazon SES exposes two different mechanisms that enable you to control whether or not mail is accepted during the SMTP conversation. The first way is to use custom IP address allow lists and block lists. By adding the IP addresses that the spam is coming from to your IP address block list, you cut off the flow, which prevents you from being charged for the unwanted mail. The second mechanism is to set up receipt rules. Amazon SES only accepts messages if there is at least one receipt rule that matches a recipient of the message. Additionally, Amazon SES maintains its own IP address block list (subject to change) and will block mail from the IP addresses in that list without your intervention. If you want to enable delivery from one of those addresses, you can add it to your allow list.
Q: Is there any size limit to the messages that I can receive through Amazon SES?
If you choose for your messages to be stored in an Amazon S3 bucket, the maximum message size (including headers) is 30 MB. If you choose to receive your messages through Amazon SNS notifications, the maximum message size (including headers) is 150 KB.
Q: Is there a limited throughput at which I can receive messages through Amazon SES?
Q: Does Amazon SES put any restrictions on AWS Lambda functions in addition to the restrictions imposed by AWS Lambda?
Yes. There is a 30-second timeout on RequestResponse invocations
Q: How does Amazon SES integrate with Amazon WorkMail?
Amazon WorkMail uses Amazon SES to send and receive mail. When you set up Amazon WorkMail, Amazon WorkMail creates two items within your Amazon SES configuration settings: 1) a sending authorization policy that allows Amazon WorkMail to send mail through your domain, and 2) a receipt rule with a WorkMail action that delivers your domain’s incoming mail to Amazon WorkMail. Do not remove these items.
Q: Who, if anyone, has access to my email content?
We take our privacy and data protection responsibilities very seriously. Amazon SES uses in-house anti-spam/anti-virus technologies to filter email messages containing poor-quality content and prevent them from being sent. We will only access email content under very limited circumstances, such as system troubleshooting, or investigating fraudulent or abusive activity. Furthermore, other Amazon SES customers do not have access to your email content.
Q: How much does Amazon SES cost?
Pay only for what you use. There is no minimum fee. In addition, Amazon EC2 users can get started with Amazon SES for free. You pay only low charges for messages sent, attachments, and data transfer. Please refer to Amazon SES Pricing for more information on pricing, data transfer costs, and free usage.
Q: How will I be charged and billed for my use of Amazon SES?
There are no set-up fees to begin using the service. At the end of the month, you will be charged for that month's usage. You can view your charges for the current billing period at any time on the Amazon Web Services web site. To view your charges for the current billing period, log into your Amazon Web Services account, click "My Account/Console," and then click "Account Activity."
Q: When does billing of my Amazon SES use begin and end?
Your Amazon SES billing cycle begins on the first day of each month and ends on the last day of each month. Your monthly charges will be totaled at the end of each month.
Q: How do I get started with the Amazon SES free tier?
To benefit from Amazon SES free tier pricing, you need to call Amazon SES from within Amazon EC2 or AWS Elastic Beanstalk. If you do this, then your AWS bill will reflect your free tier usage.
Q: Can I take advantage of Amazon SES free tier pricing if I'm in the Amazon SES sandbox?
Yes. However, to take full advantage of the Amazon SES free tier, you should request higher sending limits for Amazon SES.
Q: Where can I track my Amazon SES usage?
You can track your usage on your AWS Account Activity page.