Stack Configuration

FinOps Center creates IAM Roles and Policies. The Engineer deploying must have Administrative Privileges. (DO NOT INSTALL USING ROOT USER)

Upon Selecting Next you will be taken to the YAML form to complete the FinOps Center Installation.

Name Stack: No Requirements

Stack Parameter:

• Bucket to CUR - cid-(CUSTOMERDELEGATEDADMINACCOUNT)-data-exports

• Path to CUR Date - cur2/CustomerManagementAccount/cid-cur2/data

• Athena DB Name - cid_data_export

• Athena Table Name - cur2

• Athena DataCalog - AwsDataCatalog

• Athena WorkGroup - primary

Roles aligned to Busienss Requirements

Enviornment Parameters

• Static Website - S3 Bucket Name Created for Frontend Bucket

• From CloudFront - Distribution Name

• Create your First Admin User and Email

Cost Optimization Hub

• Bucket to CUR - cid-(CUSTOMERDELEGATEDADMINACCOUNT)-data-exports

• Path - coh/(CustomerManagementAccount)`/cid-coh/data/

Launch through EC2

Click to Zoom

Click to Zoom

Configure Instance to your companies standards. As note previously, the EC2 instanced provisioned is used to copy files to S3 for the FinOps Center deployment. We recommend a small instance (T3 Small) be used and can be shut down once the files are copied to S3.

Click to Zoom

Prior to Launch → the IAM Instance Profile much have a Role with Policy to S3 Create Bucket and S3 Write Access for FinOps Center Installation Bucket. Add your AWS Account Number to below Policies.

Navigate to IAM and follow below Steps

Step 1: Create a New Role for EC2 or Validate an Existing Role has above Policy.

Click to Zoom

JSON Policy - add account number of installed account.

Step 2: Create a Role

Click to Zoom

Step 3: Add Policy to Role

Click to Zoom

and Create Role

Click to Zoom

Return to EC2 to Launch Instance

No Key is Required as the Instance can be delete upon Install

Launch Instance

Navigate to S3

As the EC2 starts up, a bucket will appear beginning with cdk (see below)

Once you see the cdk Bucket is created navigate back to the Marketplace Listing to Launch CloudFormation.

Launch CloudFormation

Click Next

Note: All environment installation are “ Fresh Installs”. There is no separate installation pipeline between SDLC environment.

Functional:

Release 25.2.0 is primarily around the inclusion of the Amazon Q in QuickSight Framework with UI Updates and Changes the CUDOS Framework embedding from Anonymous to User-Based.

FinOps Center Enterprise (Annual or Monthly)

FinOps-In-a-Box (Annual or Monthly)

FinOps-in-a-Box (Hourly)

Enterprise

​https://finops-cf-templates.s3.us-east-1.amazonaws.com/25.6.0/ami-06a823dbc5e7a16a0-FinOps-Center-Enterprise-25.6.0.template.json​

FinOps-In-a-Box

​https://finops-cf-templates.s3.us-east-1.amazonaws.com/25.6.0/ami-0bb8211379fda513f-FinOps-In-a-Box-25.6.0.template.json

Hourly

https://finops-cf-templates.s3.us-east-1.amazonaws.com/25.6.0/ami-0112c9a73d1210b43-FinOps-In-a-Box-Hourly-25.6.0.template.json

Each Release has the Features in the Release the CloudFormation Script to use with the Marketplace AMI.

Navigate to the Release of your FinOps Center

Stack Configuration

FinOps Center creates IAM Roles and Policies. The Engineer deploying must have Administrative Privileges. (DO NOT INSTALL USING ROOT USER)

Upon Selecting Next you will be taken to the YAML form to complete the FinOps Center Installation.

Name Stack: No Requirements

Environment Parameter:

FinOps Center is major Update with new User Experience and the integration of Cost Optimization Hub Approval Process.

While the prior UI was simplier that the AWS Console, we thought we could do better and are very happy to launch the New UI in 25.8.0.

The New U1 continues to have both Light and Dark Mode.

Another Major enhancement is the Process that leverages AWS Cost Optimization Hub Data Exports.

Workload Resource Start Date

To assist users identify Workload Resource for Claiming for Workload and/or specialized MAP Workload, Resources will have Start Date. Note: this capability will identify Resource Start date from Day 2 or FinOps Center installation.

(We recommend that you keep instances with previous AMI until the upgraded installation is confirmed to be working properly. If recovery is required - you can restart the EC2 instance with the prior AMI which will update the CDK bucket with that version. Follow below instruction.)

Marketplace customers will receive an email that their is a new version of the FinOps Center AMI available. The AMI will be available in their EC2 Console for launch leveraging the same IAM Profile used during initial installation. The launched instance will update the FinOps Center cdk bucket with the updates. Select the FinOpsCenterStack.template.json and update the CloudFormation Stack with the object URL.

Click to Zoom

Click to Zoom

Validate the Parameters and advance through the next few screens and hit update.

This is the initial Release of Amazon Q in QuickSight FinOps Center Framework

Topics Created

• AWS Product

• AWS Portfolio

• AWS Department

Release 25.6.0

• Updated Admin Screens for Financial Admins for Account Allocation

• Update Month Close to run Final Cards based on seeing Invoice Number to Run Final Cards vs Manual Running Cards once Invoice is Recieved

• Updated Budget Screen for all Users

• Adding Resource Launch Date to Resource Table to assist with Workload Allocation

FinOps Center Enterprise

FinOps Center FinOps-in-a-Box

FinOps Center FinOps-in-a-Box Hourly

Amazon Q in QuickSight Backend Framework

Amazon Q in QuickSight Topics Components