1 Answer
- Newest
- Most votes
- Most comments
2
Part of what you're seeing is because your t2 instance is burstable, so it accumulates CPU credits for bursts of very high performance. 100% CPU in CloudWatch equates to max burst CPU. So if you've exhausted your credits then despite your VM running at 100% of its current capacity, CloudWatch will show a much lower percentage.
Relevant content
- asked a year ago
- asked 5 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 5 months ago