What are Best Practices to Protect my SMTP Credentials on AWS SES?

Posted on | updated:
You Asked, We Answered

This article is enhanced from the original “SMTP on AWS SES – Limit IP Addresses – Best Practice”. If you would prefer to view the original article, click here.

If you’re a business using a website or app that uses Amazon Web Service’s (AWS) Simple Email Service (SES,) there’s nothing worse than losing your Simple Mail Transfer Protocol (SMTP) credentials and not being able to send emails from your account. There are simple things that you can put in place, however, that could protect your SMTP credentials and prevent that from happening. These include the following:

  1. Setting up strong passwords for yourself and your clients.
  2. Limiting the IP addresses that can send email with your credentials
  3. Limiting the number of emails that guest accounts can send.

This article will answer the following questions:

What can compromise my SMTP credentials?

Your SMTP credentials can be compromised for any number of reasons: 

  • Connecting to your SMTP server over an unencrypted or poorly encrypted connection. By doing so or by storing your credentials in plain text such as in a configuration file or a database, your credentials could potentially be accessed by malicious actors.
  • Suspicious activity or unauthorized access to your account. This could include accessing your SMTP credentials from a suspicious IP address.
  • If your credentials are used to send large amounts of email without permission or to send out email with malicious intent such as phishing email or malware.

How can I set up strong passwords?

Strong passwords can go a long way to keeping your SMTP account and the personal information of your users safe. Commonly recommended guidelines for password creation for both you and your users include the following:

  • Passwords should be at least 8 characters long. Ideal passwords are 12 characters or more.
  • Use upper and lower case letters in addition to numbers and special characters in passwords.
  • Do not put personal information in passwords. This includes names, addresses, and birthdates.
  • Avoid putting anything in a password that could be easily guessed including common words, phrases, or sequences.
  • Do not use the same password for multiple accounts.
  • Don’t write down passwords. Instead, use a password manager.

In addition to yourself, you should set higher password standards for your users. For more helpful tips regarding passwords and password security, check out “As an App Founder, What Do I Need to Know about Passwords?”

How can I limit the IP addresses that can send emails from SMTP credentials?

One way to protect your SMTP credentials from being compromised is to reduce the number of IP addresses that can send email from your credentials. This involves allowing the sending of email from your networks and the networks of anyone you deem as necessary, and then locking down any other Identity and Access Management (IAM) SMTP users.

You do that by setting up an IPAddress Condition which will restrict sending of email to only your Allowed IP Addresses.

Here is how to do it in the AWS Console, which can be found at https://console.aws.amazon.com/iam/home. The console will look similar to this:

(With AWS constantly in transition, your page could differ slightly from the below pictures.)

Once you bring up your AWS Console, follow these directions:

  1. Goto IAM > Users 
  2. Select [user]
  3. Go to the Permissions tab
  4. Click the arrow to expand the AmazonSesSendingAccess
  5. Click “Edit Policy”
  6. Update the JSON to add the Condition:IPAddress (below) for the IP Addresses you want to restrict email access to.

Here is an example of a full policy with multiple allowed IP Addresses:

This condition can be applied to many of your other IAM users as well.

Why might I limit the number of emails guests can send?

If the code of your website or app allows users to set up free accounts that give them email access, they could potentially take advantage of it. Your users could use the email to spam or to send out malicious emails to others with no adverse consequences to themselves. This action, however, could compromise your SMTP credentials. AWS may even strip away your credentials which would prohibit you from sending email to anyone.

One possible way to prevent this from happening is by limiting the amount of emails that a guest can send from their account. In addition, you can choose to be notified when a user is getting close to reaching that limit.  When you are notified, you can confirm what the questionable emails say, determine what is going on, and intervene if necessary.

How can I limit the number of emails that guests can send?

One possible way of limiting the number of emails that guests can send is to use Amazon Simple Notification Service (SNS). SNS is an API that allows applications to receive notifications from other applications and can, in turn, send out notifications. To set this up, the app founder will need to create the Amazon SNS topic (similar to an email list) and subscribe it to an email address. Once the topic is set up, the app founder can use the AWS SES API to configure a “sending quota” for a guest account. This quota will determine how many emails the guest account can send in a given time period. 

If the guest account reaches the quota, the app founder will be notified via the Amazon SNS topic subscription. With this set up, the app founder can be alerted when a guest account is close to its quota so they can take any necessary steps to prevent the account from exceeding the quota.

Amazon may charge for this service, and it is only one way to potentially put limits on emails sent from guest accounts. This may be a topic to discuss with the app developer or to do further research in.



Matraex is a premier app development company located in Boise, Idaho. Our mission is to provide consumers with information about app and software development so they can be informed and make the right decisions for their business. Feel free to call us at (208) 344-1115, contact us, or leave a question on our Google Business Profile. We look forward to hearing from you.