AWS: How to Remove Port 25 Email Restrictions

Select Language:

If you’re trying to send emails from an AWS EC2 instance or Lambda function, you might run into a common problem: AWS blocks outbound traffic on port 25, which is the standard port used to send emails through SMTP. This restriction is in place to prevent spam. Even if you’ve already submitted a request to lift this block, it can take up to 48 hours for a response. Waiting eight days is quite long, and it suggests you need some alternative solutions in the meantime.

First, consider following up on your initial support request by opening a new support ticket with AWS. Make sure to reference your original case number, so they can easily find your request and give it priority.

While waiting for the restriction to lift, you can switch to other methods to send emails. Here are some options:

Use AWS Simple Email Service (SES). It’s specifically built to send emails securely from AWS, making it a reliable choice.
Change your application’s settings to use different SMTP ports, such as port 587 (which uses TLS) or port 465 (which uses SSL). These ports are not blocked by AWS.
Use a third-party email relay service. Many services support sending emails through alternative ports, which can help you avoid AWS restrictions.

It’s important to note that AWS often denies requests to open port 25, especially if the purpose seems related to testing. The process to get approval can be strict, and many users find it easier and more reliable to stick with SES or alternative ports for email delivery.

If you really need access to port 25 and there’s a delay in approval, the best course of action is to escalate your support case with AWS. This way, you might be able to get a faster resolution.

Here are some helpful links for further guidance:

Following these steps should help you maintain email functionality while you work on getting port 25 access approved.