Once you’ve integrated with AWS CloudWatch, you have access to all metrics for AWS SES, which is an email platform that provides an easy, cost-effective way for you to send and receive email using your own email addresses and domains.
You can create a pre-built dashboard for this integration when you add the integration to Cloud Observability or from the Dashboard list view.
To verify metrics are reporting, search for the metrics on the Metric details page in Settings.
The following table shows the SES metrics ingested by Cloud Observability.
| Metric Name | Unit | Description |
|---|---|---|
| aws.ses.send | count | The send request was successful and Amazon SES will attempt to deliver the message to the recipient’s mail server. (If account-level or global suppression is being used, SES will still count it as a send, but delivery is suppressed.) |
| aws.ses.rendering_failure | count | The email wasn't sent because of a template rendering issue. This event type can occur when template data is missing, or when there is a mismatch between template parameters and data. (This event type only occurs when you send email using the SendTemplatedEmail or SendBulkTemplatedEmail API operations.) |
| aws.ses.reject | count | Amazon SES accepted the email, but determined that it contained a virus and didn’t attempt to deliver it to the recipient’s mail server. |
| aws.ses.delivery | count | Amazon SES successfully delivered the email to the recipient's mail server. |
| aws.ses.hard_bounce | count | The recipient's mail server permanently rejected the email. (Soft bounces are only included when Amazon SES fails to deliver the email after retrying for a period of time.) |
| aws.ses.complaint | count | The email was successfully delivered to the recipient’s mail server, but the recipient marked it as spam. |
| aws.ses.delivery_delay | count | The email couldn't be delivered to the recipient’s mail server because a temporary issue occurred. Delivery delays can occur, for example, when the recipient's inbox is full, or when the receiving email server experiences a transient issue. |
| aws.ses.subscription | count | The email was successfully delivered, but the recipient updated the subscription preferences by clicking List-Unsubscribe in the email header or the Unsubscribe link in the footer. |
| aws.ses.open | count | The recipient received the message and opened it in their email client. |
| aws.ses.click | count | The recipient clicked one or more links in the email. |
See also
Updated Dec 14, 2022