> For the complete documentation index, see [llms.txt](https://docs.finopscenter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finopscenter.com/amazonq/finops-centers-installation-components.md). # FinOps Center's Installation Components ## FinOps Center's Installation Components FinOps Center's Installation requires configuration of your AWS Cloud Estate within the Management Account and the Delegated Admin Account where the application will be installed. **Tasks in Management Account** * Create Cost and Usage Report * Create S3 Bucket for Cost and Usage Report * Create IAM Role for S3 Bucket Replication * S3 Management setup of Bucket Replication and Batch Operation (optional) Assess Requirement 1. Admin - creating IAM Role **Tasks in Designated Admin** 1. Create S3 Bucket for Bucket Replication and Frontend Application 2. Configure S3 Buckets 3. Launch and Configure QuickSight 4. Run/Configure RLS CUDOS CloudFormation Installation 5. Create IAM Profile for FinOps Center Installation 6. Subscribe and install FinOps Center Marketplace offering 7. Launch EC2 to copy FinOps Center code to S3 Bucket 8. Install FinOps Center from CloudFormation **Access Requirement** 1. Admin - creating IAM Role --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.finopscenter.com/amazonq/finops-centers-installation-components.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.