- Más nuevo
- Más votos
- Más comentarios
Hello,
You could still use port 465 or 587 to connect to SMTP using Amazon SES: https://repost.aws/knowledge-center/ses-set-up-connect-smtp
I've seen these denied in the past if you don't offer an explanation on how you will ensure the setup will not result in spam messages.
The advice offered by others is accurate, but I'd like to add that the best way to send emails in AWS is with SES (as also others suggested) and specifically, using the SES API instead of SMTP: https://docs.aws.amazon.com/ses/latest/dg/send-email-api.html
If you're sending emails from your own, custom code, I would recommend switching from SMTP to the Amazon SES API. The SMTP interface only supports authenticating with a username and password that are derived from static access keys associated with an IAM user (https://docs.aws.amazon.com/ses/latest/dg/send-email-concepts-credentials.html), meaning that it doesn't support temporary credentials. The Amazon SES API and SES API v2 interfaces support temporary credentials issued for an IAM role, such as an EC2 instance role or Lambda execution role, and don't require setting up long-term static credentials at all, making creating a secure setup much more straightforward.
Contenido relevante
- OFICIAL DE AWSActualizada hace 9 meses
- OFICIAL DE AWSActualizada hace 8 meses
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 2 años
hey thanks for your answer, is it possible to do an SMTP check with 465/587? Our goal is to do it in bulk so that our users can verify email at scale, can we scale with this in based on your experience?
Hi,
It's possible to connect to AWS SES with port 465 or 587 and send bulk emails without issues.