Memory metric showing in insufficient state after creation of memory metric

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,

1. Go to IAM and click on Roles.
2. click on Create Role
3. Select type of trusted entity 'AWS service, EC2, Lambda and others'
4. For Choose the service that will use this role, click on 'EC2'
5. Click on button Next: Permissions
6. In Filter policies, enter 'CloudWatchFull'
7. Click the checkmark box next to 'CloudWatchFullAccess'
8. Click Next: Tags
9. Click Next: Review
10. In Role name, enter 'EC2_CloudWatch'
11. Click on Create Role
12. Go back to your EC2 Dashboard
13. Select your Running Instance
14. Select 'Actions->Instance Settings->Attach/Replace IAM Role'
15. Select the newly created IAM role
16. Hit Apply button
    Hope this helps

Edited by: rtakeshi on Jul 31, 2019 11:26 AM - Removed the brackets which were causing formatting issues

Its name space issue, we have to exact name space which AWS provides. I changed name space, now its working fine