FAQ

We have set this up in the most common regions. If your region is not in the list please email costoptimization@amazon.com and we will create this resource for you

Please make sure you enable Compute Optimizer following this guide.

If, when you deployed your StackSets, you chose to deploy to all accounts and you now wish to edit you will need to get your Root ID.

This can be found in your AWS Organizations part of the console.

There are two main reasons for this:

1. We recommend customer avoid deploying workloads to the organization’s management account in general:

“Since privileged operations can be performed within an organization’s management account and SCPs do not apply to the management account, we recommend that you limit access to an organization’s management account. You should also limit the cloud resources and data contained in the management account to only those that must be managed in the management account.” from here

2. As there are lambda function deployed in the account these could benefit from Compute Savings plans. This means that there could be higher savings missed in other accounts because they are used on the lambdas first:

“In a Consolidated Billing Family, Savings Plans are applied first to the owner account’s usage, and then to other accounts' usage. This occurs only if you have sharing enabled.” from Here

We have upgraded the lab to work for multi-payers. For this we added a new partition of payer_id=your_payer_id which can upset the crawler.

To fix please follow the steps below:

1. Ensure your costoptimization bucket does have the new payer_id=your_payer_id folder in your data.

2. Delete your new tables with names that have long hashs attached to them and start with payer or year

3. Run the following python script Link to Code

   python3 s3_files_migration.py <ODC_your_bucket_name>

   This will move all current files into the new format

4. Run your crawlers to update your tables