AWS integration: connect Lambda, EC2, S3 and CloudWatch to Polylane
Connect AWS resources, CloudWatch logs and alarms to Polylane. Trace incidents across services with an infrastructure graph and deployment history.
Get started for freeHow to set up AWS
The console describes stack deployment as taking a few minutes and displays a troubleshooting message after ten minutes without confirmation. That timeout is not a setup SLA.
- Choose AWS in Settings → Cloud accounts. Enter the 12-digit account ID and the region for the connection stack.
- Open Deploy stack on AWS, review the generated CloudFormation template and acknowledge its IAM resources before creating the stack.
- Return to Polylane while the stack reports back. The console waits for confirmation and opens the connected account when registration succeeds.
Permissions and access
The shipped role is not strictly read-only: it attaches ReadOnlyAccess and AWSLambdaBasicExecutionRole plus an inline policy. It explicitly denies application S3 object reads outside the Polylane bucket and DynamoDB/DAX data reads. Additional grants manage polylane-prefixed Lambda functions and SNS topics, the connection CloudTrail and S3 bucket, the connection stack, tagging, CloudWatch alarms and dashboards, EventBridge rules, metric publishing and a constrained EKS access entry with AmazonEKSAdminViewPolicy. Cross-account sts:AssumeRole uses an ExternalId. This flow has no separate read-only/full-access switch; review the exact generated policy before deploying.
Discovery, refresh and the connected view
The initial scan maps the connected account’s supported services, networking and dependencies. Later scans are triggered by AWS change events rather than a fixed scheduled full scan. Resource pages expose configuration and history; investigation tools read CloudWatch logs, metrics, alarms and X-Ray traces.
Disconnect and revoke access
Disconnect in Polylane. The API attempts deletion of the owned connection stack; if cleanup fails, delete it in CloudFormation. The role and inline policy have Retain deletion policies, so inspect and remove retained IAM resources to revoke access completely.
Provider credentials and Polylane’s access mode are separate. Where write-capable tools exist, the connected account’s Settings page offers a Read-only switch. Turning it off permits writes subject to review and confirmation, but cannot add permissions to the provider credential. Agent-connected Kubernetes clusters stay read-only.
Exact additional IAM Allow actions
These inline actions supplement the two managed policies. The resource boundaries described above still apply; review the generated template for every ARN and condition.
lambda:CreateFunctionlambda:AddPermissionlambda:DeleteFunctionlambda:UpdateFunctionConfigurationlambda:UpdateFunctionCodecloudformation:DeleteStacktag:GetResourcestag:GetTagKeystag:GetTagValuestag:TagResourcestag:UntagResourcescloudtrail:*s3:*sns:*lambda:InvokeFunctionce:GetCostAndUsageWithResourcesce:GetCostAndUsageiam:PassRoleevents:PutEventscloudwatch:DescribeAlarmscloudwatch:DescribeAlarmHistorycloudwatch:ListDashboardscloudwatch:GetDashboardcloudwatch:ListMetricscloudwatch:GetMetricDatacloudwatch:PutMetricAlarmcloudwatch:DeleteAlarmscloudwatch:DisableAlarmActionscloudwatch:EnableAlarmActionscloudwatch:PutDashboardcloudwatch:DeleteDashboardscloudwatch:PutMetricDataevents:PutRuleevents:PutTargetsevents:DeleteRuleevents:RemoveTargetseks:CreateAccessEntryeks:AssociateAccessPolicyeks:DeleteAccessEntryeks:AccessKubernetesApieks:DescribeAccessEntryeks:ListAccessEntrieseks:ListAssociatedAccessPolicies
In the graph.
Every AWS resource Polylane picks up sits in the graph with its connections, config and history.
Tools for the investigation.
What Polylane can do with AWS while it investigates. Every call is recorded in the transcript.
-
awsApiRead any AWS API via a SigV4-signed request (read-only escape hatch) -
awsCloudWatchAlarmsRead or manage CloudWatch alarms (list, get, getHistory, create, acknowledge, enableActions) -
awsCloudWatchDashboardsRead or manage CloudWatch dashboards (list, get, create) -
awsCloudWatchLogsRead CloudWatch logs (listGroups, describeStreams, getEvents, filter, query) -
awsGetCloudWatchQueryResultsGet results of a CloudWatch Insights query -
awsCloudWatchMetricsRead CloudWatch metrics (list available metrics, get data points) -
awsXRayTracesRead X-Ray traces (list summaries, get full trace) -
awsXRayInsightsRead X-Ray insights (list, get, getEvents) -
awsXRayServicesRead X-Ray service topology and time-series statistics (graph, timeseries) -
awsGetXRayGroupsList X-Ray groups -
awsEksKubectlRead and operate on Kubernetes resources on an EKS cluster (get/list/describe/logs/events/top/rollout, plus scale, restart, patch, delete, apply)
AWS setup and troubleshooting
Docker context deadline exceeded
Common questions.
How does Polylane connect to my AWS account?
Choose AWS in Settings → Cloud accounts. Enter the 12-digit account ID and the region for the connection stack. Open Deploy stack on AWS, review the generated CloudFormation template and acknowledge its IAM resources before creating the stack. Return to Polylane while the stack reports back. The console waits for confirmation and opens the connected account when registration succeeds.
What AWS resources does Polylane sync?
The initial scan maps the connected account’s supported services, networking and dependencies. Later scans are triggered by AWS change events rather than a fixed scheduled full scan. Resource pages expose configuration and history; investigation tools read CloudWatch logs, metrics, alarms and X-Ray traces.