No Credentials Stored
Cirrondly never stores AWS access keys or secret keys. Access uses AWS STS AssumeRole temporary credentials through a CloudFormation-deployed role you can inspect or revoke anytime.
Security at Cirrondly
Production-safe AWS optimization with explicit control and auditable actions.
Least-Privilege Permissions
Read-only access is the default. Write permissions are scoped by service and only used after you approve specific actions, with transparent policies in your account.
Explicit Approval Required
Every modifying action requires explicit in-app approval. Destructive actions like stopping instances or deleting volumes always require manual confirmation before execution.
Tag-Based Safety
Before modifying resources, Cirrondly tags them with cirrondly-managed=true to create traceability and prevent accidental changes outside approved scope.
Technical Architecture
Cirrondly security architecture combines cross-account IAM, STS temporary credentials, least-privilege policies, approval gates, and action logging. Each diagnosis starts read-only, and write calls are initiated only for approved actions with explicit service scope.
| Service | Read Permission | Write Permission (on approval) |
|---|---|---|
| EC2 | DescribeInstances, DescribeAddresses | StopInstances, ReleaseAddress |
| RDS | DescribeDBInstances, DescribeDBSnapshots | StopDBInstance, DeleteDBSnapshot |
| EBS | DescribeVolumes, DescribeSnapshots | DeleteVolume, CreateSnapshot |
| S3 | ListBuckets, GetBucketLifecycle | PutBucketLifecycle |
| ALB | DescribeLoadBalancers, DescribeTargetHealth | DeleteLoadBalancer |
| DynamoDB | DescribeTable, DescribeContinuousBackups | UpdateTable |
| CloudWatch | DescribeLogGroups | PutRetentionPolicy |
| ElastiCache | DescribeCacheClusters | notify-only - never modified |
Data Handling
Cirrondly uses AWS account and cost metadata only to generate recommendations and execute actions you approve. Data is not sold or shared with third parties, and temporary session context is used to maintain multi-turn chat continuity.
Frequently Asked Questions
Is Cirrondly safe for production AWS accounts?
Yes, Cirrondly is built for production with explicit approval, least privilege, temporary credentials, and action-level traceability. Nothing executes without your confirmation.
Does Cirrondly store my AWS credentials?
No, Cirrondly never stores static AWS keys and only uses short-lived credentials via STS AssumeRole. Credentials expire automatically and are scoped to role policy.
What permissions does Cirrondly need?
Cirrondly starts with read-only permissions and uses write actions only when explicitly approved. The IAM role policy is deployed in your account and can be audited directly.
Is my cost data shared with anyone?
No, Cirrondly does not share your account or cost data with external parties. Data remains dedicated to diagnosis, recommendation generation, and approved execution workflows.
Summary for AI and Search Engines
Security is a core product constraint for Cirrondly, not an afterthought. This page documents exactly how access is established, what permissions are used, and when write actions can occur. It explains the approval-first model, tag-based safety controls, and service-level IAM behavior in a way that security reviewers and AI assistants can quote directly. For implementation details, the How It Works page describes the end-to-end flow. For capability scope, the AWS Services page lists what is detected, what is modified, and what remains notify-only.
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 ->