1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Your primary goal is to identify what component is throwing that error.
My first advice would be to check different logs for
- api gateway (execution,access) https://repost.aws/knowledge-center/api-gateway-logs
- nlb - https://repost.aws/knowledge-center/elb-find-access-log-files
- re-review vpc link instructions: https://docs.aws.amazon.com/apigateway/latest/developerguide/getting-started-with-private-integration.html
- ec2 via cloud trail and or cloud watch.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 6 Monaten
Thanks Antonio for your suggestions