​

Configuring AWS Alternate Contacts

​

Introduction

1. Billing Contact: Notifications about billing and payment issues.
2. Operations Contact: Alerts about operational issues.
3. Security Contact: Security-related notifications.

​

Prerequisites

1. Access to the AWS Management Console as the root user or with appropriate permissions.
2. A configured email alias system, as outlined in your organization’s root email setup:
   • Root account email: root@corp.co
   • Aliases:
     • Billing: root+billing@corp.co
     • Operations: root+operations@corp.co
     • Security: root+security@corp.co

​

Steps to Configure Alternate Contacts

​

Step 1: Navigate to Alternate Contacts

1. Log in to the AWS Management Console as the root user or an IAM user with appropriate permissions.
2. Open the Account Settings page:
   • From the navigation bar, choose your account name or the “My Account” link.
3. Scroll down to the Alternate Contacts section.

​

Step 2: Update Billing Contact

1. Click the Edit button next to the Billing Contact.
2. Enter the following details:
   • Name: Billing Team or another descriptive name.
   • Email Address: root+billing@corp.co
   • Phone Number: Optional, but recommended for urgent issues.
3. Click Save Changes.

​

Step 3: Update Operations Contact

1. Click the Edit button next to the Operations Contact.
2. Enter the following details:
   • Name: Operations Team
   • Email Address: root+operations@corp.co
   • Phone Number: Optional.
3. Click Save Changes.

​

Step 4: Update Security Contact

1. Click the Edit button next to the Security Contact.
2. Enter the following details:
   • Name: Security Team
   • Email Address: root+security@corp.co
   • Phone Number: Optional, but highly recommended.
3. Click Save Changes.

​

Verifying Configuration

1. Test Email Deliverability: Send a test email to each alias (root+billing@corp.co, root+operations@corp.co, and root+security@corp.co) to confirm they are correctly routed to the appropriate inbox.
2. AWS Notifications: Review notifications sent to the alternate contact emails to ensure proper delivery.

​

Best Practices

1. Centralized Inbox Management:
   • Use a shared mailbox or email rules to manage alias-based communications.
   • Ensure that responsible team members monitor and respond to emails promptly.
2. Regular Updates:
   • Periodically review alternate contact configurations to ensure they reflect current organizational structure and responsibilities.
3. Compliance and Security:
   • Regularly audit the alternate contact emails to confirm compliance with internal and external policies.
   • Ensure only authorized personnel have access to these communications.
4. Backup Recovery:
   • Maintain access to the root account email to ensure continuity in case alternate contact emails are inaccessible.

​

Benefits of Using Email Aliases

1. Simplified Management:
   • All alternate contact communications are centralized under the root account, reducing complexity.
2. Enhanced Clarity:
   • Aliases clearly identify the purpose of each email, improving response efficiency.
3. Scalability:
   • New contact roles or categories can be easily added by creating additional aliases.

​

Conclusion