2 Answers
- Newest
- Most votes
- Most comments
0
Hi, there,
I understand that when you are getting “failed to find an S3 endpoint or NAT gaetway for the VPC - xxxx in subnet yyyyy” and after adding the s3 endpoint it works.
As per the below article, either adding the S3 VPC gateway endpoint or a route to a NAT gateway in the subnet's route table, should resolve this error. For more details, please refer the below article:
[+] https://repost.aws/knowledge-center/glue-s3-endpoint-validation-failed
0
The reason that this is an issue is because Glue stores its scripts and a temporary files in an S3 bucket.
Either an S3 gateway or a NAT gateway will provide the appropriate access to S3.
Relevant content
- asked 10 months ago
- Accepted Answerasked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
Check if you're disabling the built-in proxy https://docs.aws.amazon.com/glue/latest/dg/connection-VPC-disable-proxy.html