1 Answer
- Newest
- Most votes
- Most comments
0
Found that the issue was down to the network configuration.
I eventually found the issue by stopping the instance and detaching the boot volume, I then mounted it onto another EC2 instance and drilled down into the logs.
answered 4 years ago
Relevant content
- asked 9 months ago
- asked 3 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago