- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hello @MVR-060709, Thanks for your input. I have checked again the configuration and nothing has change from my side:
And as I said before, is happening in several accounts accros several regions.
Kind regards.
Hello! There are a number of different permissions which are required for Compute Optimizer to access the metrics and then also for those recommendation to be viewable to you. To view EC2 metrics in Compute Optimizer, the user/role you are logged in with would need the ec2:DescribeInstances
permission. To view CloudWatch metrics in Compute Optimizer, you would need the cloudwatch:GetMetricData
permission. (Source: https://docs.aws.amazon.com/compute-optimizer/latest/ug/security-iam.html)
From a Compute Optimizer perspective, I recommend you leverage a service-linked role (if you aren't already). This will ensure that Compute Optimizer has all of the permissions it requires to interact with other services. I've included a link to how to recreate the role if it has been inadvertently removed. https://docs.aws.amazon.com/compute-optimizer/latest/ug/using-service-linked-roles.html
Hope this is helpful!
Contenus pertinents
- demandé il y a 7 mois
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
It is now showing the Memory metric, definitely it was something inside AWS.