I host www.foo.com for a client. The website sends emails via postfix which has my Amazon SES SMTP Credentials configured and my SES has foo.com as a verified domain and this all works fine.

Now the client wants to send emails from her gmail account as sally@foo.com (using gmail's "add another email address that you own" feature) so she has asked for the SMTP credentials. Other than hitting the sending limits of my SES account, what are the other risks if I share the smtp credentials of my SES account with her? Anyone know a better way to satisfy her request?

Possible dupe of If my SES SMTP credentials are compromised can my SES API usage (using access key+secret) be affected but I'm really looking for a list of other risks and ways to avoid them.


Set up a separate AWS account for your client, preferably billed directly to them. Problem solved.

  • 2
    Agreed. I would never give a client my credentials for my services. – joeqwerty Aug 31 '15 at 2:51

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.