AWS FinOps Agent Preview: Autonomous Cloud Cost Management Arrives

Key Takeaways

• AWS FinOps Agent can query costs, surface optimizations, and open Jira tickets on a defined schedule
• Amazon engineering teams reported 4.5x median productivity gains using AI-native development practices
• Gemma 4 with 256K context window is now available on Amazon Bedrock

AWS Summit NYC kicked off at the Javits Center this week with a clear theme: autonomous agents are moving from demos to production infrastructure. The headline announcement is AWS FinOps Agent, now available in preview, which can query your AWS costs, generate reports, surface optimization recommendations, and open Jira tickets without human intervention.

The agent pulls data from AWS Cost Optimization Hub and AWS Compute Optimizer to identify rightsizing opportunities, idle resources, and Savings Plans recommendations. It can run these workflows on a defined schedule, turning what was previously a manual FinOps review into an automated process.

“The era of stateless LLM calls is fading; we are moving rapidly toward persistent, autonomous agentic workflows that bridge the gap between intent and infrastructure execution.”

— Dr. Swami Sivasubramanian, VP of Agentic AI at AWS

What the FinOps Agent Actually Does

The agent serves two audiences: FinOps practitioners who need to track and optimize cloud spend, and engineering teams who want cost visibility without context-switching to billing dashboards.

• Query AWS costs using natural language
• Generate cost reports formatted for finance and engineering stakeholders
• Surface rightsizing and idle resource recommendations from Cost Optimization Hub
• Pull Savings Plans recommendations from Compute Optimizer
• Open Jira tickets based on optimization findings
• Run recurring FinOps workflows on a schedule you define

The Jira integration is notable. Instead of surfacing recommendations that sit unread in a dashboard, the agent can create tickets assigned to the right team. This closes the loop between identifying waste and actually fixing it.

Community Pushback on Agent Permissions

Hacker News threads on the Summit announcements focused heavily on permissions. Should an autonomous agent have write access to cost management configurations? Can it modify infrastructure, or only observe and report?

AWS has not published detailed IAM guidance for the preview, but the initial feature set suggests the agent operates primarily in read mode for cost data, with write access limited to external systems like Jira. Organizations will need to decide how much autonomy to grant.

AI-Native Development: The Productivity Numbers

Sivasubramanian also published data from experiments across hundreds of Amazon engineering teams. The headline numbers are striking.

A six-engineer team rebuilt the Amazon Bedrock inference engine in 76 days. The project was originally scoped for 30 developers over 12 to 18 months. Perfect Order Experience went from a two-week feature cycle to shipping in an afternoon. WW Grocery cut design document creation from five days to a few hours.

The post outlines five practices that distinguish high-performing teams:

1. Invest in agent context: build steering files, coding standards, and structured repositories before writing production code
2. Expect an initial slowdown while workflows are restructured, and push through it
3. Maintain a steady backlog of well-scoped tasks so agents can run in parallel
4. Make intent explicit through structured specifications before code generation
5. Shift testing left so agents can self-correct before code reaches the pipeline

The data comes with a caveat. Commit velocity is only part of the picture. Sivasubramanian notes that a follow-up post will cover release management, operations, security operations, and end-of-life upgrades.

Gemma 4 Arrives on Bedrock

Google DeepMind's Gemma 4 31B model is now available on Amazon Bedrock with a 256K context window. Reddit's r/aws community is treating this as a viable alternative to closed-source models for sensitive reasoning tasks.

The 256K context window is large enough to process substantial codebases or document sets in a single call. For teams that need to keep data within their own infrastructure, an open-weights model on Bedrock offers more control than API calls to external providers.

OpenSearch Gets Model Context Protocol

The Summit also brought Model Context Protocol (MCP) integration to OpenSearch. This lets agents access operational telemetry directly, enabling them to investigate and resolve production incidents without human intervention.

“By integrating Model Context Protocol directly into OpenSearch, we're allowing agents to finally 'see' the operational telemetry they need to resolve production incidents without human intervention.”

— Chet Kapoor, VP of Security Services and Observability at AWS

This fits the broader theme of the Summit: moving agents from isolated chat interfaces to integrated systems that can observe, reason, and act across production infrastructure.

What Else Happened

The Summit keynote livestream goes live on June 17, featuring Sivasubramanian and Kapoor on developer tools, AI infrastructure, and security. For those tracking AWS sustainability metrics, the company reported a 2025 global water use effectiveness (WUE) of 0.12 liters per kWh, well below the industry average of 0.84.

AWS also announced Kiro Pro Max, though details were limited in the initial roundup. The $2.56 billion "Cumulus" contract with the U.S. Department of Homeland Security continues to move forward.

Frequently Asked Questions

What is AWS FinOps Agent?

AWS FinOps Agent is an autonomous agent that queries AWS costs, generates reports, surfaces optimization recommendations from Cost Optimization Hub and Compute Optimizer, and can open Jira tickets based on its findings. It runs workflows on a defined schedule.

Is AWS FinOps Agent generally available?

No. As of June 2026, AWS FinOps Agent is in preview. AWS has not announced a general availability date.

What is the context window for Gemma 4 on Bedrock?

The Gemma 4 31B model on Amazon Bedrock supports a 256K context window, allowing it to process large codebases or document sets in a single call.

What productivity gains did Amazon teams see with AI-native development?

Amazon Stores teams reported a median 4.5x gain in normalized deployment velocity. Some teams exceeded 10x. A six-person team rebuilt the Bedrock inference engine in 76 days versus an original scope of 30 developers over 12-18 months.

When is the AWS Summit NYC 2026 keynote livestream?

The keynote livestream is available on June 17, 2026, featuring Dr. Swami Sivasubramanian and Chet Kapoor.

Source: AWS News Blog