FinOps na AWS: configurando o FinOps Agent e integrando com o Slack

Article discussing the configuration of the AWS FinOps Agent and its integration with Slack. The FinOps Agent was launched in June 2026 with the goal of investigating costs within an AWS account. It can be integrated with Slack and Jira tools commonly used in corporate environments. Typically, AWS cost data is consulted in native tools like Cost Explorer, Compute Optimizer, and Cost Optimization Hub, which are mostly accessed by FinOps or infrastructure teams.

Development teams provisioning resources often don't consult these tools. Without active monitoring, issues can take longer to identify. Integrating the FinOps Agent with Slack or Jira helps address this by consolidating insights from the three tools and publishing the results in a channel or ticket where the working team resides daily.

This approach brings cost information closer to the resource provisioners and reduces the chance of anomalies going unnoticed.

The AWS FinOps Agent is built on Amazon Bedrock and offers four main features: natural language cost queries using real cost and usage data; anomaly investigation triggered by events; consolidation of Cost Optimization Hub and Compute Optimizer recommendations; and scheduled recurring reports in HTML, PDF, or PPT formats. To achieve this, the agent reads data from five services: Cost Explorer, Cost Anomaly Detection, Cost Optimization Hub, Compute Optimizer, and CloudTrail logs.

To implement the FinOps Agent, certain prerequisites are needed: an AWS account with administrative access or permission to create IAM roles; a console in the us-east-1 region; both Cost Optimization Hub and Compute Optimizer enabled; a Slack workspace with permissions to authorize applications; and a sufficient cost volume to generate recommendations.

Note that Cost Optimization Hub and Compute Optimizer must be enabled before creating the agent, as otherwise it is created normally but returns empty optimization recommendations.

The implementation steps are as follows:

1. Enable Cost Optimization Hub and Compute Optimizer. Both are free services, but the AWS may take a few hours to generate recommendations upon first activation, resulting in potentially empty dashboards initially.

2. Create the FinOps Agent. First, change the console region to us-east-1 as the service isn't listed in other regions during the public preview. Next, search for the AWS FinOps Agent service and click "Get started". Define a name and description. Configure permissions, where the recommended option "Auto-create a new FinOps Agent role" automatically creates the role the agent uses to read cost data from the account.

Also, configure the FinOps Operator role permission for the application web access, which can be automatically created as well.

3. Integrate with Slack. Select the "Connect with Slack" option and click "Add integration". Follow the prompts to authorize the FinOps Agent to access your Slack workspace.