AWS rolled out the FinOps Agent in public preview, letting cloud-cost data and optimization tips appear directly in Slack channels. Developers and operations teams can now spot spend spikes and get rightsizing suggestions without leaving their chat workflow.

Why cost data ends up hidden

Most organizations rely on AWS Cost Explorer or similar dashboards to track usage. Those tools sit in a separate console that developers rarely open, creating a disconnect between the people who spin up resources and the people who pay the bill.

The FinOps Agent’s answer

The new agent plugs five AWS services into a conversational interface powered by Amazon Bedrock. When a user asks in Slack—“What did we spend on EC2 last week?”—the agent pulls the answer from Cost Explorer, surfaces any anomalies flagged by Cost Anomaly Detection, and adds recommendations from Cost Optimization Hub and Compute Optimizer. CloudTrail logs let the bot point to the exact IAM user or role responsible for a cost spike, turning vague alerts into actionable insight.

Core capabilities

  • Natural-language queries – Type a question and get a concise reply.
  • Automatic anomaly investigations – When Cost Anomaly Detection triggers, the agent posts a summary in the designated channel.
  • Consolidated optimization tips – Rightsizing suggestions from Compute Optimizer and savings recommendations from Cost Optimization Hub arrive together, reducing the need to jump between consoles.
  • Scheduled reports – Teams can ask the agent to post HTML, PDF, or PPT reports.

Getting it running

The preview is limited to the us-east-1 region and requires a few pre-steps:

  1. Enable services – Turn on Cost Optimization Hub and Compute Optimizer in the billing console first; otherwise the agent returns empty recommendation lists.
  2. Create the agent – In the us-east-1 console, select “Get Started” for the FinOps Agent. The wizard can auto-create the required IAM roles (FinOps Agent role and FinOps Operator role) if the user has permission to create roles.
  3. Connect Slack – Authorize the integration, add the bot to a channel, and paste the channel’s ID (the string that starts with “C”) into the setup screen.
  4. Validate data – Because the service is still in preview, cross-check the bot’s answers against Cost Explorer to ensure accuracy.

Only channels where the bot is a member receive messages, preventing unwanted noise elsewhere. If the required optimization services are not enabled before the agent is created, the bot posts “no recommendations” messages until the services are turned on.

Takeaway: Teams that wrestle with invisible cloud spend can pilot the FinOps Agent to bring cost signals into daily conversation, but they should treat the bot’s output as a supplement—not a replacement—for the full suite of AWS cost-management tools until the preview matures.