Original Articles：
https://zenn.dev/mob_engineer/articles/skack-finops-agent
Thank you for reading this article.
I'm Mob Engineer (@mob_engineer).
AWS FinOps Agent was released as a public preview on June 10, 2026. I tried setting up the Slack integration and wrote down my thoughts with an eye toward using it in real-world operations.
Target Audience
This article is primarily aimed at those who want to know what you can do through AWS FinOps Agent. In particular, I'd like to highlight the benefits of Slack integration.
Key Takeaways
Building the AWS FinOps Agent itself takes just 4 clicks, and the Slack integration isn't particularly difficult either. However, the information sent to Slack is essentially an access link to the FinOps Agent, so you might not get the information you expected directly in Slack.
About AWS FinOps Agent
The release blog describes it as follows:
FinOps (short for financial operations) brings together finance, engineering, and business teams to maximize the business value of cloud investments through shared financial responsibility and data-driven tradeoffs between cost, speed, and quality. FinOps is shifting from periodic dashboard-driven reviews to continuous workflows operated jointly by engineering, finance, and FinOps teams. This transition requires specialized cost expertise, execution at scale across many accounts and workloads, and integration with the tools engineering teams already use. AWS FinOps Agent is designed to address each of these needs. It brings specialized cost expertise to engineering, finance, and FinOps practitioners and fits into how teams already work in Jira and Slack. It also runs at whatever cadence the work demands—on a regular schedule, when anomalies are detected, or when engineers have cost questions.
Announcing the public preview of AWS FinOps Agent
Building the AWS FinOps Agent
Based on the documentation, setup is currently only supported through the AWS Management Console. The workflow is: Set a name > Configure role > Set up Slack or Jira integration — and you're done.
For detailed step-by-step instructions, I found the article written by umitsu-san to be very clear, so please refer to that.
Slack Integration
Details are in the official AWS documentation, but the overall workflow is: Register the AWS FinOps Agent app to your Workspace > Create a notification channel > Add the app to the channel — and you're done.
Enable Slack with AWS FinOps Agent
Personally, I find it easy to miss the step of adding the app to the channel, so be careful. The official documentation also marks it as Important, so if you follow the guide you should be fine.
Before creating a connection, add the AWS FinOps Agent Slack app to the channel. Open the channel in Slack, select the channel name, select the Integrations tab, and add the AWS FinOps Agent app. If the app is not added to the channel, the agent cannot post messages to that channel.
FinOps Report
Here are the results of running an analysis on my test environment:
There's only one configured channel, so I'll send it there. Here's the message I'll post — shall I go ahead?
EC2 Rightsizing Analysis — June 11, 2026
No rightsizing opportunities found at this time.
| Source | Result |
|---|---|
| Cost Optimization Hub (all regions) | $0 savings — no recommendations |
| Compute Optimizer (us-east-1) | 1 instance analyzed (mob-test-server, t4g.micro) — OPTIMIZED
|
Notes:
- Compute Optimizer was queried for us-east-1 only — other regions may need separate analysis
- Verify Cost Optimization Hub enrollment in the Cost Management Console
- Re-run as the EC2 fleet grows (Compute Optimizer needs 14 days of metrics per new instance)
The output is in English, so you'll need to translate it if you want Japanese. Also, the Slack integration doesn't happen automatically — you need to execute a prompt like "Please send this to Slack".
You can also run prompts in Japanese, but there are cases where you'll get a message saying "Only English is supported", so I recommend using English prompts.
Ideas for Business Use
After a quick hands-on exploration, here's what I noticed:
- If your company uses Slack for internal communication, this is easy to adopt
- If you outsource cost optimization, you can share just the Agent dashboard (separation of permissions)
- The output content feels hard to read for non-technical staff
It also supports IAM integration, so if you have an AWS account, you should be able to manage authentication and authorization. (There doesn't seem to be integration with IAM Identity Center though.)
An automation feature also appears to be available, so I'd like to test that in the future. Thank you for reading to the end.
Top comments (0)