Amazon SES Resources

Today, Simple Email Service (SES) Mail Manager announces the addition of a Debug logging level for Mail Manager traffic policies. This new logging level provides more detailed visibility on incoming connections to a customer’s Mail Manager ingress endpoint and makes it easier to troubleshoot delivery challenges quickly, using familiar event destinations such as Cloudwatch, Kinesis, and S3.

With Debug level logs, customers can now log every possible evaluation and action within a Mail Manager traffic policy, along with envelope data for the email message being evaluated for traffic permission. This enables customers to determine whether their traffic policy is working as expected or to isolate incoming message parameters which are not covered by the current configuration. When used in conjunction with rules engine logging, debug logging for traffic policies charts a full picture of message arrival into Mail Manager and its disposition by the rules engine. Debug logging for traffic policies is intended to be used during active troubleshooting but otherwise left disabled, as its output can be verbose for high-volume Mail Manager instances. While SES does not charge an additional fee for this logging feature, customers may incur costs from their chosen event destination.

Debug logging for traffic policies is available in all 17 AWS non-opt-in Regions within the AWS commercial partition. To learn more about Mail Manager logging options, see the SES Mail Manager Logging Guide.

Today, Amazon Simple Email Service (SES) launched support for connecting to SES outbound sending endpoints over IPv6. Customers can now specify their preference for IPv4 or IPv6 endpoints when using the AWS SDK or CLI. This makes it easy to switch from using IPv4 addresses to IPv6 addresses when communicating with the SES services for outbound sending.

Previously, customers could use the AWS SDK or CLI to connect with SES endpoints for outbound sending. These connections always used IPv4 addresses when creating TCP/IP connections for communication with the SES service. Now customers can specify their preference for dual-stack using an environment variable or command line argument. The AWS SDK and CLI will use this information to specify the address type when connecting to the SES service API endpoint.

SES supports IPv6 addresses when connecting to SES endpoints for outbound sending in all AWS Regions where SES is available.

For more information, see the documentation on using dual stack endpoints with AWS services.
 

Amazon Simple Email Service (SES) announces that its Mail Manager email modernization and infrastructure features now have a rule action which enables messages to be published using an Amazon Simple Notification Service (SNS) notification. The notification includes the complete email content, and has options for SNS Topic and Encoding.

Amazon SNS is a fully managed service that provides message delivery from publishers (producers) to subscribers (consumers). Publishers communicate asynchornously with subscribers by sending messages to a topic, which is a logical access point and communication channel. Subscribers can choose to receive these notifications through a variety of endpoints, including email, SMS, and Lambda. By centralizing notification preferences within SNS, customers enhance messaging between applications and users while gaining advantages of high availability, durability, and flexibility. Using the Publish to SNS rule action within Mail Manager increases the number and type of delivery destinations available to customers as part of their larger ruleset configuration.

Mail Manager’s Publish to SNS rule action is available in all 17 AWS Regions where Mail Manager is launched. There is no additional fee from SES to make use of this feature, though charges from AWS for SNS and destination channel activity may apply. Customers can learn more about SES Mail Manager by clicking here.

Today, Amazon Simple Email Service (SES) launched support for logging email sending events through AWS CloudTrail. Customers can maintain a record of email send actions performed using the SES APIs, including actions taken by a user, role, or an AWS service in SES.

Previously, customers could use SES event destinations to route sending event notifications to custom data stores they created and managed themselves. This required custom solutions for data storage and data indexing, including development costs and operational oversight costs. Now, customers can configure event logging to AWS CloudTrail without any custom solution development. Customers can search for events, view the events, and download lists of events for processing in their private workflows. This gives customers a turn-key solution for event history management.

SES supports AWS CloudTrail data events for sending events in all AWS Regions where SES is available.

For more information, see the documentation on logging sending API calls with AWS CloudTrail.

Amazon Simple Email Service (SES) announces that its Mail Manager email modernization and infrastructure features now accept incoming connections from customer-provisioned Virtual Private Clouds (VPCs) to Mail Manager Ingress Endpoints. This makes use of PrivateLink connectivity features already provided by AWS.

Since Mail Manager launched in mid-2024, VPC connectivity has become the most-requested new feature from customers. These customers operate large fleets of applications hosted inside AWS, and want to route all their outgoing and incoming mail for those applications via Mail Manager. By adding VPC support via PrivateLink, those customers can now route all their outgoing mail securely entirely within AWS to Mail Manager, using its ‘Send to Internet’ action or by delivering mail to a downstream SMTP relay, hands the message off to its first external destination. The feature is enabled after a customer has created their VPC, by creating a new ‘Network’ Ingress Endpoint type and specifying the VPC’s unique endpoint ID. Customers can also choose whether or not to use authentication to their Ingress Endpoint for connections originating via PrivateLink. All VPC-enabled Mail Manager Ingress Endpoints support dual-stack (IPv4 and IPv6) connectivity by default.

Mail Manager VPC Ingress Endpoints are available in all 17 AWS Regions where Mail Manager is launched. There is no additional fee from SES to make use of this feature, though charges from AWS for VPC and PrivateLink activity may apply. Customers can learn more about SES Mail Manager by clicking here.

Today, Amazon SES announces the availability of the Vade Add On for Mail Manager, a sophisticated content filter that enhances email security for both incoming and outgoing messages. This new Add On, developed in collaboration with HornetSecurity, combines heuristics, behavioral analysis, and machine learning to provide robust protection against evolving communication threats such as spam, phishing attempts, and malware.

Now available as a rule property in Mail Manager, the Vade Add On empowers users with automated, real-time defense against email-based threats for safer communication. Its AI-powered technology employs a multi-layered approach, analyzing messages in real-time using advanced techniques like natural language processing. This integration allows customers to strengthen their email platforms by configuring ongoing protection against evolving cyber threats alongside existing Mail Manager rules, offering flexibility in managing their email security.

The Vade Add On for Amazon SES Mail Manager is available in the following AWS Regions: US East (N. Virginia), US West (Oregon), Europe (Ireland), Europe (Frankfurt), Asia Pacific (Tokyo), and Asia Pacific (Sydney), US East (Ohio), US West (San Francisco), Asia Pacific (Mumbai), Asia Pacific (Osaka), Asia Pacific (Seoul), Canada Central (Montreal), Europe (London), Europe (Paris), Europe (Stockholm), and South America (São Paulo).

To learn more about this new feature and how it can enhance your email security, visit the documentation for Email Add Ons in Mail Manager. You can easily activate the Vade Advanced Email Security Add On directly from the Amazon SES console to start protecting your email communications today.
 

Amazon Simple Email Service (SES) announces that Outbound customers can now specify a Mail Manager archive resource as an additional destination for outbound mail workloads. This enables retention of messages post-DKIM-signature, ensuring that the archive is usable for validating every individual sent message. The Mail Manager archive search interface allows easy discovery of indexed messages and presents search results directly in the AWS console, or makes them available to export to the customer’s chosen S3 bucket.

SES Outbound customers using APIv2 now have access to a new parameter in their configuration set which specifies a Mail Manager archive ARN in the same . Once the necessary role permissions in IAM are configured, the user initiating the Outbound workload will see a copy of each uniquely-signed outgoing message ingested into the destination archive, where it will be indexed and made available for both search and export.

This new feature is billed at the existing Mail Manager Archive price points. This capability is available for Outbound customers in all 17 AWS Regions where Mail Manager is launched. Customers can learn more about SES Outbound and Mail Manager here.

Today, Amazon Simple Email Service (SES) launched a new pricing structure for Virtual Deliverability Manager (VDM), giving customers reduced charges at higher levels of usage. Customers can benefit from lower total VDM charges without the need to change account configuration, sending practices, or billing setup. This can lower customer total cost of ownership for VDM as their usage increases.

Previously, all customers using VDM paid a fixed price per message sent. Customers could turn VDM on or off whenever needed, and they paid only for what they used without any commitment or fixed monthly charges. Now, customers will see their charges per message for VDM decrease as their sending volume exceeds specific thresholds each month. After crossing each threshold in a given billing month, each subsequent message processed by VDM is charged at a lower rate. This reduces the total cost of using VDM for high volume senders.

SES supports tiered pricing for VDM in all AWS regions where SES is available.

For more information, see the documentation for the SES pricing page.