1 Answer
- Newest
- Most votes
- Most comments
0
I found the answer, it appears that it created a private DNS endpoint to the EC2 instance by default when creating the VPC endpoints. I deleted that private DNS name and it is working now.
answered 6 months ago
Relevant content
- asked a year ago
- asked a year ago
- asked 3 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
If you have vpc endpoints you’ll want private dns names. S3 gateway endpoint behaves differently.