Prerequisites
- Organization Admin role in Kestrel
- AWS account with permissions to create IAM roles and policies
- AWS CLI or access to the AWS Console
Connection Types
When connecting an AWS account, you select a connection purpose:| Purpose | Description |
|---|---|
| EKS | Connect for Kubernetes cluster discovery and monitoring |
| VPC Flow Logs | Enable VPC Flow Log collection and analysis |
| Cloud Ingestion | Full cloud resource inventory and security monitoring |
You can create multiple connections to the same AWS account with different purposes, or use a single Cloud Ingestion connection for comprehensive coverage.
Setup Steps
Step 1: Start the Connection
- Navigate to Integrations → Cloud in your Kestrel dashboard
- Click Connect AWS Account
- Select your AWS region
- Select the connection purpose
- Click Generate CloudFormation Template
Step 2: Deploy the CloudFormation Stack
Kestrel generates a CloudFormation template that creates a cross-account IAM role with the minimum permissions required. You can deploy it using either method: Option A: AWS Console (One-Click) Click the Launch Stack link provided in the setup dialog. This opens the AWS Console with the template pre-loaded. Review the parameters and click Create Stack. Option B: AWS CLI Copy the provided AWS CLI command and run it in your terminal:Step 3: Verify the Connection
- Once the CloudFormation stack reaches
CREATE_COMPLETE, copy the Role ARN from the stack outputs - Paste the Role ARN into the Kestrel verification dialog
- Click Verify Connection
VPC Flow Logs
After connecting an AWS account with VPC Flow Logs capability:- Navigate to the connected account in the Cloud Integrations page
- Expand the VPC Flow Logs section
- Click Enable to start collecting flow logs across your VPCs
- Kestrel creates the necessary log groups and flow log configurations automatically
Managing Connections
- Refresh: Re-sync the connection status and resource inventory
- Delete: Remove the connection. This does not delete the IAM role in AWS - you should clean up the CloudFormation stack separately.
Permissions
The IAM role created by the CloudFormation template includes read-only access to services like:- EC2 (instances, security groups, VPCs, subnets, flow logs)
- S3 (bucket policies, public access settings)
- RDS (instances, clusters, security)
- IAM (roles, policies, users - metadata only)
- CloudTrail (event history)
- EKS (clusters, node groups)
- Lambda, ECS, and other compute services