79403160

Date: 2025-01-31 15:11:16
Score: 1
Natty:
Report link

Having done a bit more digging , I appear to have found the solution. The default port number was incorrect which is why the error was appearing and after changing it to the same port number I used locally, it worked. I would also suggest for others that encounter is to double check that your lambda is configured to the correct vpc.

Reasons:
  • Whitelisted phrase (-1): it worked
  • No code block (0.5):
  • Self-answer (0.5):
  • Single line (0.5):
  • Low reputation (0.5):
Posted by: bardsleyta