Trouble Shooting
FinOps Center
FinOps Center is a web application that may experience typical issues from users around login issues or page loading (especially updates). Additionally, during the initial 24hrs of installing FinOps Center the application may be awaiting data population from the Cost & Usage Report (CUR).
If users are having issues with their initial logging into FinOps Center it could be an issue with the Cognito temporary password. It is common that the remedy is to delete the users from the Cognito User Pool and Re-Create them in the FinOps Center Configuration.
During initial configuration of the application the AWS CUR Data is not loading you may need to wait until the next cycle to run. Have a member of your technical team navigate to the S3 bucket in the FinOps Center installed account and view when the last CUR was created keeping in mind that the CUR creation time is UCT. If a CUR cycle has run after the time of the upload of the Chart/Budget File, contact support.
Agent Bill Amazon Q in QuickSight
If users are having issues accessing the Amazon Q in QuickSight Topics, validate that the following are configured apppriately:
The FinOps Center application URL has been added to the QuickSight Admin
Validate in the Topic ID has been added to the Configuration Page
Validate that the Topics have been added to the Role from the QuickSight Console
if you can't see the Topics, validate that your Author Pro has the Topics Role
Agent Bill Agentic CFM
Client application cannot reach AgentCore MCP endpoint
Wrong ALB DNS used or not using HTTPS 443
Validate the endpoint using curl -v https://<agentcore-alb-dns>/health — must return 200
AgentCore cannot invoke FinOps Center API
IAM trust misalignment between delegated admin and linked accounts
Validate delegated admin role trust using STS AssumeRole test from AgentCore ECS task execution role
AppSync returns unauthorized
missing JWT validator / wrong signature key
Validate JWT issuer matches AgentCore Identity config. re-rotate token + test via AppSync Console with same token
Lambda invoked but no FinOps process executes
missing FinOps Center permission boundary or missing PK Tenant prefix
Validate Dynamo Partition Key prefix matches defined TenantID for that deployment
Agentcore ECS tasks stuck in provisioning
VPC endpoint missing or SG restricts outbound
Validate required Interface Endpoints (S3, DynamoDB, STS, Secrets Manager, AppSync, Bedrock) exist and SG outbound is not 0.0.0.0/0 denied
Cost Optimization Hub Data
If Cost Optimization Hub Data is not loading in the Cost Optiizatoin Raw Table,, navigate to the Lambda service in the Console (CostOptimizationLambda881C3E41) and run Test to trigger the Lambda.
Last updated