2 Answers
- Newest
- Most votes
- Most comments
0
Do you currently have an IAM role attached to your EC2 Instance? One possible issue is that your EC2 instance does NOT have permissions to write data to CloudWatch, which is one of the reasons that the Memory metric would be stuck in the Insufficient state. If you don't currently have a Role assign,
- Go to IAM and click on Roles.
- click on Create Role
- Select type of trusted entity 'AWS service, EC2, Lambda and others'
- For Choose the service that will use this role, click on 'EC2'
- Click on button Next: Permissions
- In Filter policies, enter 'CloudWatchFull'
- Click the checkmark box next to 'CloudWatchFullAccess'
- Click Next: Tags
- Click Next: Review
- In Role name, enter 'EC2_CloudWatch'
- Click on Create Role
- Go back to your EC2 Dashboard
- Select your Running Instance
- Select 'Actions->Instance Settings->Attach/Replace IAM Role'
- Select the newly created IAM role
- Hit Apply button
Hope this helps
Edited by: rtakeshi on Jul 31, 2019 11:26 AM - Removed the brackets which were causing formatting issues
answered 5 years ago
0
Its name space issue, we have to exact name space which AWS provides. I changed name space, now its working fine
answered 4 years ago
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 5 months ago