Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Send email via SES VPCEndpoint
See original GitHub issueIs your feature request related to a problem? Please describe.
VPC Endpoints for SES were announced recently.
However, if you try to send an email via boto3 SES, the client will use the default URL (email.eu-west-1.amazonaws.com), which doesn’t connect to the VPC Endpoint (it will time out because there is no route to it in the private subnet)
To connect to the VPC Endpoint, we have to use a URL like ‘email-smtp.eu-west-1.amazonaws.com’ (the private DNS name of the endpoint)
However, if you specify this URL in the endpoint_url param to the Boto3 constructor, it will fail with:
Invalid endpoint: email-smtp.eu-west-1.amazonaws.com
Describe the solution you’d like
I would like to be able to send email via the VPC Endpoint, which I suspect will mean being able to override the endpoint_url.
If I have misunderstood anything regarding usage of boto3, then please do clarify.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hello,
is there any progress in the implementation of SES Endpoint using SDK? Or SES VPC Endpoint is still only for SMTP?
Thank you!
I think this should be a feature request to the service team as @swetashre mentioned. So I created a new issue in our shared SDK repository to track this: https://github.com/aws/aws-sdk/issues/181
I reached out to the SES team and will update that issue when I hear back.