Skip to main content
Sponsor @cloudposse

Decide on Email Address Format for AWS Accounts

When creating AWS accounts, you need to decide on the email address format. Each AWS account requires a unique email address that cannot be reused across multiple accounts. The chosen format should align with your organization’s email management strategy and ensure proper delivery and handling of AWS notifications.

Every AWS account needs a unique email address. Email address cannot be reused across multiple AWS accounts.

Disambiguation:

we are referring AWS accounts that contain resources, not individual user accounts

Use Plus Addressing​

We'll use + addressing for each account (e.g. [email protected])

info

Office 365 has finally added support for https://docs.microsoft.com/en-us/exchange/recipients-in-exchange-online/plus-addressing-in-exchange-online.

Use Slack Email Gateway​

  • Create email group/alias for AWS accounts e.g. [email protected]

  • Ideally set up to forward to a shared slack channel like #aws-notifications

Follow this guide to set up slack forwarding.

Use Mailgun​

Mailgun supports plus addressing and complex forwarding rules. It’s free for 5,000 emails.

Use Google Group - Recommended​

Google Groups are probably the most common solution we see. It works very well with plus addressing.

Use OpsGenie Email Integration​

OpsGenie is nice, but it does not support plus addressing. That means we’ll need to provision one integration for each account.

Use AWS SES with Lambda Forwarder (catch-22)​

Provisioning AWS SES is nice, but we need an email address even for the root account, so it doesn’t solve the cold-start problem.

https://github.com/cloudposse/terraform-aws-ses-lambda-forwarder