Hey everyone! I'm trying to deploy the Cloud Intelligence Dashboards for my AWS account, but I've hit a snag. The instructions suggest deploying two CloudFormation templates in separate accounts: one for data collection and another for management. Since I only have one AWS account for all production infrastructure, I ran into issues when trying to execute the second template; it caused errors related to S3 creation because I was attempting this in the same account.
I asked for help and was told to go to AWS > Billing and Cost Management > Data Exports, where I set up a data export for the Cost and Usage Dashboard. I created a QuickSight profile since it was required, and I now see a Cost & Usage Dashboard (v1.0.1) in QuickSight. I'm not sure if this is what I need since the latest version seems to be v2.
Additionally, trying to access data fill back through AWS Support led to a message stating that they can't provide account or billing details directly since I'm linked to a Solution Provider. It looks like my AWS deployment is connected to an organization I'm not able to access.
My main question is: can I deploy CUR 2.0 successfully in a single AWS account using these templates? If so, I'd appreciate any guidance on how to set up the CUDOS, CID, and KPI Dashboards in my account. Any links or resources would be super helpful too! I've used these dashboards before, and they were great for FinOps stuff, so I'm eager to get them running in my new organization. Thanks a lot!
2 Answers
I hear you! It might seem tricky at first, but you can actually get CUR 2.0 to work in a single account setup. The best approach is to treat your current account as both the source and destination account in your configurations. Just follow the instructions to set it as the first element and skip to bypass the second step. More details can often be found in AWS documentation if you get stuck!
Sounds like you're having quite a challenge! If your AWS account is indeed linked to a reseller, that might be causing some of the deployment issues. Typically, when dashboards are deployed in a single linked account, you'll want to make sure your current account ID is included in both the source and destination account settings, then just skip the second step during the setup. This should help you bypass the errors you're encountering. Also, check with your reseller because sometimes they can create the necessary CUR setups for you, or they might have specific policies in place that could affect your deployment options.
Thanks for the tip! I’ll double-check the settings and talk to my reseller about the CUR creation.