SES Connectivity issue

0

I am triggering email using ses from a lambda, SES was fast initially and it got slower and now it is throwing connectivity issues, can someone help me how to fix this

Error: connect ETIMEDOUT 52.8.242.19:443
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16) {
  errno: -110,
  code: 'TimeoutError',
  syscall: 'connect',
  address: '5X.8.2.19',
  port: 443,
  time: 2023-07-20T17:04:01.713Z,
  region: 'us-west-1',
  hostname: 'email.us-west-1.amazonaws.com',
  retryable: true
}
Anser
asked 9 months ago363 views
1 Answer
0

Hello,

Kindly note that ETIMEDOUT error generally indicates that your Lambda service was unable to reach out to your downstream service endpoint. .

If you are experiencing intermittent TCP connection timeout with a working public endpoint then it’s also something that we need to troubleshoot from the Lambda service itself. Because this may be due to packet fragmentation. Lambda functions cannot handle incoming fragmented TCP requests, since Lambda does not support IP fragmentation for TCP or ICMP.

Please refer the below Lambda documentation which is stating the timeout error that you have experienced.

Reference: https://docs.aws.amazon.com/lambda/latest/dg/troubleshooting-networking.html#troubleshooting-networking-cfn:~:text=Error%3A%20Error%3A%20connect%20ETIMEDOUT%20176.32.98.189%3A443

If you still face the same issue, I would recommend you to create a Support case with the AWS Lambda Support team for assistance as additional information will required to troubleshoot your issue further.

The concerned team will be happy to help you further.

AWS
SUPPORT ENGINEER
answered 9 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions