1 Answer
- Newest
- Most votes
- Most comments
0
configuring my instance to have same security group as my eb-env fixed the issue (instance config security group was on default and eb-env's was on a generated group)
answered 5 years ago
Relevant content
- asked 3 years ago
- asked 8 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 4 months ago