In order to connect to the Zesty Dashboard for a Potential Savings Report, an IAM role will need to be created.
At this stage, Zesty requires read-only permissions for metadata associated with your EC2 usage. This includes lists of running EC2 instances, any commitments already in place and historical data from AWS Cost Explorer.
For a JSON of the required read-only permissions, click here.
What permissions are required to see Potential Savings?
Was this article helpful?