AWS. EC2, Lambda, ECS, RDS, S3, and more.
Connect your AWS account to give agents full visibility into your infrastructure. Agents can discover resources, monitor CloudWatch metrics, analyze costs, and help you understand your architecture across EC2, Lambda, ECS, RDS, and more.
Join the waitlistWhat Polylane does with AWS.
74 resource types in one graph
Lambda, ECS, RDS, DynamoDB, SQS, EventBridge, EKS, VPCs and everything wired into them, with their edges, config, and history.
CloudWatch read for you
Agents comb metrics, logs, and X-Ray traces on a cadence and judge them against how each resource normally behaves. No thresholds to tune.
Alarms that investigate themselves
Point your CloudWatch Alarms at Polylane and an agent picks each one up as it fires, so the alarm arrives with an explanation attached.
Change intelligence
Each sync records what appeared, changed, or disappeared across the account. When something breaks minutes after a change, the investigation starts there.
How it works.
One CloudFormation stack
Review the open template and create the stack. It provisions an IAM role with the AWS-managed ReadOnlyAccess policy, assumable cross-account only.
Sync
Your resources land in the graph within minutes, with edges, config, and history.
Agents take the watch
Telemetry is combed on a cadence, alarms get investigated as they fire, and code fixes arrive as pull requests for your review.
In the graph.
The AWS resource types Polylane syncs, with their edges, config, and history.
Lambda Function Lambda Layer 
EC2 Instance 
VPC Subnet Security Group Internet Gateway NAT Gateway Route Table Network ACL EBS Volume Elastic IP 
S3 Bucket 
DynamoDB Table 
RDS Instance 
CloudFront Distribution 
API Gateway REST API API Gateway v2 API API Gateway Custom Domain 
SQS Queue 
SNS Topic 
ECS Cluster ECS Service ECS Task Definition 
ElastiCache Cluster 
App Runner Service App Runner Connection 
IAM Role 
KMS Key 
Kinesis Stream ElastiCache Replication Group RDS Cluster RDS Proxy Service Discovery Service 
Secrets Manager Secret 
EventBridge Rule EventBridge Bus 
Step Functions State Machine 
Redshift Cluster 
Kinesis Firehose 
Neptune Cluster 
Cognito User Pool Cognito Identity Pool 
Athena Workgroup 
Glue Database Glue Crawler Glue Job 
Batch Job Queue Batch Compute Environment 
Amazon MQ Broker 
MSK Cluster 
DocumentDB Cluster MemoryDB Cluster 
CloudTrail Trail GuardDuty Detector 
WAF Web ACL 
ACM Certificate 
EKS Cluster EKS Node Group EKS Fargate Profile EKS Addon EKS Access Entry EKS Identity Provider EKS OIDC Provider 
Elasticsearch Domain OpenSearch Domain EventBridge Pipe 
Amplify App 
Application Load Balancer Network Load Balancer Gateway Load Balancer Target Group Load Balancer Listener Listener Rule Glue Table The tools agents get.
What an agent can do with AWS mid-investigation. Every call lands in the thread transcript, cited.
awsApi Read any AWS API via a SigV4-signed request (read-only escape hatch)
awsCloudWatchAlarms Read or manage CloudWatch alarms (list, get, getHistory, create, acknowledge, enableActions)
awsCloudWatchDashboards Read or manage CloudWatch dashboards (list, get, create)
awsCloudWatchLogs Read CloudWatch logs (listGroups, describeStreams, getEvents, filter, query)
awsGetCloudWatchQueryResults Get results of a CloudWatch Insights query
awsCloudWatchMetrics Read CloudWatch metrics (list available metrics, get data points)
awsXRayTraces Read X-Ray traces (list summaries, get full trace)
awsXRayInsights Read X-Ray insights (list, get, getEvents)
awsXRayServices Read X-Ray service topology and time-series statistics (graph, timeseries)
awsGetXRayGroups List X-Ray groups
awsEksKubectl Read and operate on Kubernetes resources on an EKS cluster (get/list/describe/logs/events/top/rollout, plus scale, restart, patch, delete, apply)
Questions.
Is Polylane an AI SRE for AWS?
It's what most people mean by the term: agents that keep your AWS resources in one context graph, watch them, investigate issues and fix what they can, with a human approving anything that changes production. We call it self-operating software rather than an AI SRE: the point is that your software looks after itself, not that a bot joins the on-call rotation.
Can Polylane change anything in AWS?
Only if you let it. Connected read-only, agents investigate and explain, and changes only ever land as pull requests for you to review. With write access, every write pauses for your approval first, with the method, path and reason on screen. Rollbacks are off by default: you enable them per automation and can turn them off at any time.