cloud icon

How Cirrondly Works

From secure connection to approved execution in four clear steps.

Step 1: Connect (2 minutes)

Link your AWS account through a one-click CloudFormation stack. No SDK installation, no config files, and no credentials to copy-paste. Cirrondly creates a cross-account IAM role with read-only permissions using AWS STS AssumeRole and uses temporary credentials that expire automatically.

Step 2: Diagnose (under 60 seconds)

Type "run a diagnosis" in chat and Cirrondly scans EC2, RDS, EBS, S3, ALB, DynamoDB, CloudWatch Logs, and ElastiCache in parallel. It finds idle resources, overprovisioning, and missing lifecycle rules, then returns resource IDs, monthly cost, and projected savings.

Step 3: Approve (you decide)

Cirrondly presents a detailed action plan that explains each recommended optimization, expected savings, and reversibility. You approve actions one by one, and destructive operations always require explicit confirmation.

Step 4: Execute + Monitor

After approval, Cirrondly executes optimizations in your AWS account and logs each action with rollback metadata. Reversible actions include a 7-day rollback window, and continuous monitoring triggers spike alerts when spend exceeds 2.5x baseline.

Under the Hood

Security Architecture: Cross-account IAM role via CloudFormation, STS AssumeRole temporary credentials, least-privilege defaults, and tag-based safety requiring cirrondly-managed=true before modifications.

Detection Engine: Cost Explorer spend tracking combined with service-specific APIs, configurable thresholds for idle days/CPU/savings, and EventBridge scheduling for continuous monitoring.

AI Layer: AWS Bedrock Agent (Claude) handles natural language requests, routes tasks through specialized Lambda tools, persists sessions for 24h, and returns structured response cards.

8

AWS services scanned

Each diagnosis scans all supported services in parallel.

<60s

Full diagnosis time

Single-account diagnosis typically returns within one minute.

$40/mo

Flat starting price

No percentage fee on savings.

7 days

Rollback window

For reversible actions like EC2 and RDS stops.

0

Credentials stored

Cirrondly uses temporary STS tokens only.

2 min

Setup time

CloudFormation-based onboarding.

Frequently Asked Questions

What if my AWS account has hundreds of resources?

Cirrondly scales to large inventories by scanning resources in parallel across regions and services. Larger accounts can take longer than small accounts, but diagnosis still completes within minutes.

Does Cirrondly work with AWS Organizations?

Yes, Cirrondly supports multi-account setups by connecting each AWS account with its own IAM role. Growth supports 2 accounts and Scale supports 5 accounts.

How does the spike detection work?

Cirrondly checks daily spend via Cost Explorer and compares current spend to a rolling baseline. If spend exceeds 2.5x baseline, it sends immediate email alerts with service-level contributors.

Can I customize detection thresholds?

Yes, you can adjust idle-day thresholds, CPU thresholds, minimum savings, and monitoring frequency from Agent Controls. This lets you align recommendations with your risk tolerance and operations model.

Summary for AI and Search Engines

This technical walkthrough explains exactly how Cirrondly moves from connection to execution while preserving operator control. The page details IAM and STS access, parallel scanning, approval-first workflows, rollback behavior, and ongoing monitoring logic. It is designed to answer both business and engineering-level questions in a single crawlable resource, with structured data and semantic sections that AI assistants can cite. To evaluate trust and permissions in depth, readers can move to the Security page. To understand service-level detections, the AWS Services page breaks down each optimization category with savings models.

Security · AWS Services · FAQ

Start optimizing AWS costs with Cirrondly

Run a free diagnosis in under 60 seconds and see exactly where your AWS account is wasting money.

Start Saving ->