A Cloudhealth weekly report based on environments and cost development is sent to you by email (free of charge).
Cost monitoring/optimization is realized by root360 via Cloudhealth.
Native access to the AWS costs from the dedicated account is not possible, because the costs are globally consolidated via Consolidated Billing (root360 AWS organization).
2) Separate root360 AWS account:
AWS account is billed monthly by root360.
Native access to the AWS costs is possible.
NOT INCLUDED:
free Cloudhealth weekly report based on environments and cost development
Cost monitoring/optimization by root360 via Cloudhealth.
3) Customers AWS account (self-payer):
AWS account is billed directly by the customer (self-payer). For this purpose, an AWS organization as a payer is required on the customer side, into which we can invite the current AWS account. Alternatively, the customer can create an AWS account directly in his own AWS organization and give root360 access with the necessary administrative rights.
free Cloudhealth weekly report based on environments and cost development
Cost monitoring/optimization by root360 via Cloudhealth.
When AWS account is billed directly by the customer (self-payer) it may occur a representative of AWS is contacting you regarding technical information and recommended cost optimizations. Please forward such requests to root360 customer service to support you and define necessary next steps.
Create AWS account access for root360:
To grant root360 access, the following steps are required in the customer AWS account:
Create new IAM role
As "type of trusted identity" select "Another AWS account"
As Account ID set 094110064958 (central root360 account) and leave both options Require external ID and Require MFA unchecked
Select "AdministratorAccess" as Policy
Name new role "Allow_r3_access"
Confirm the creation of the role with [Create Role]
Related Tutorials
Filter by label
There are no items with the selected labels at this time.