1 Answer
- Newest
- Most votes
- Most comments
0
Judging from what you wrote up here, it seems that you are capable of troubleshooting yourself already.
So I actually suspect it might be an internal bug that you might want to report to AWS?
Or maybe you can check if a chosen subnet is indeed a public subnet?
(It has Internet Gateway and route configured for it)
answered a year ago
Relevant content
- asked 10 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago