1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
It's hard to help you with such a low amount of details - for starters, you should check your logs ("journalctl" is the command you're after, look up online for some guides and parameters) for what happens immediately before it goes unreachable.
beantwortet vor 2 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 7 Monaten
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
This sounds like something is happening on the OS of the instance. Have you performed any kind of scan to detect if the instance has been compromised? Consider scanning using Amazon Inspector. https://docs.aws.amazon.com/inspector/latest/user/what-is-inspector.html
Can you provide additional details such as
Instance type OS