Polylane fixes issues in your AWS account. It finds them, works out the cause, and writes the fix.
Review and deploy one CloudFormation stack to connect your AWS account. Polylane then discovers your resources.
For connection steps, permissions and resource discovery, Set up the AWS integration.
Get started for freeEverything Polylane picks up.
Everything Polylane reads from your AWS account.
Polylane covers the whole account.
- metrics vs usual behaviour
- logs vs usual behaviour
- X-Ray traces vs usual behaviour
- issue something drifted
Reads CloudWatch around the clock
Metrics, logs and X-Ray traces are checked against how each resource usually behaves. When something drifts, you get an issue. No thresholds to tune.
- ALARM it fired
- investigation starts at once
- explanation attached
Investigates your CloudWatch Alarms
Point your alarms at Polylane and each one is investigated the moment it fires, so it arrives with an explanation.
- one graph what a failure affects
Knows what depends on what
Lambda, ECS, RDS, DynamoDB, SQS, SNS, EventBridge, Step Functions, VPCs and EKS sit in one graph, so Polylane knows what a failure affects.
- appeared Lambda Function
- changed ECS Service
- disappeared SQS Queue
Tracks infrastructure changes
Polylane records what appeared, changed or disappeared in the account, and starts there when something breaks.
- cause in your code
- fix repo behind the service
Writes the fix on the right repo
When the cause is in your code, Polylane opens a pull request with the fix on the repo behind the service.
- ReadOnlyAccess AWS managed policy
- additional grants monitoring, tags, EKS view
- template review before deployment
Review the AWS permissions
Inspect the CloudFormation template before you deploy it. The role combines ReadOnlyAccess, AWSLambdaBasicExecutionRole and an inline policy. Extra permissions include connection resources, resource tags, CloudWatch alarms and dashboards, EventBridge rules, and EKS cluster view. AmazonEKSAdminViewPolicy includes Kubernetes Secrets. The role denies application S3 object reads outside the Polylane bucket and DynamoDB/DAX data reads. See the full IAM action list and resource limits.
Use AWS with any coding agent. Polylane connects them.
Connect your agent to Polylane once and it can query AWS alongside the rest of your stack.
Guides for AWS
- Blog Turn your app into a context graph Agents that run software need a context graph of the app: every resource, what it connects to, the repository that deploys it and the team that owns it. How we built one on Durable Objects, keep it fresh across every provider without polling AWS, decide what counts as a change, and delete from it safely.
- Guide Is it safe to give an AI SRE read access to production? Read access for an AI SRE is a sound first step if you scope it. The risks are secrets, customer data and exfiltration. Here are the controls and a checklist.
Common questions.
Is Polylane an AI SRE for AWS?
It does that work, though we call it self-operating software. Polylane keeps your Lambda functions, ECS services and RDS databases in one graph, investigates what breaks and fixes it.
Is the AWS connection read-only?
The IAM role includes read and write permissions. Polylane's read-only mode is separate and starts enabled. When enabled, it blocks agent write calls. A workspace admin can change this mode in the account settings. The mode does not change the IAM role's permissions.
What happens when a CloudWatch alarm fires?
Opt in when you connect and Polylane subscribes to the account's alarms. When one fires, Polylane investigates it against recent changes and everything connected to the resource.
Does it work with my observability provider?
Yes. Polylane supports all the major observability providers, and you can connect any other through MCP. The full list is on polylane.com/integrations.
What does it cost?
Every plan, price and limit is on polylane.com/pricing.