1 Answer
- Newest
- Most votes
- Most comments
2
Hello, do you have the NAT Gateway created in the public subnet but added as a route in the private subnet?
Relevant content
- Accepted Answerasked a year ago
- asked 15 days ago
- asked 5 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
No. It is created in public subnet and linked to private.
What is the error that you are getting? Is it timing out?
Yes, that was a connected timedout exception. We were able to solve it by whitelisting the studio's outbound request in the organization firewall. Thank you very much for your valuable suggestion.