Security & Compliance
Lynx Compliance - AWS Connector
Pulls compliance evidence from AWS — EC2 instances, security groups, IAM users/roles, S3 buckets, KMS keys, CloudTrail, RDS — via boto3. For Patrii Cloud customers running hybrid AWS workloads.
lynx_compliance_connector_aws
· v19.0.1.0.0
· Premium
What this solves
Lynx Compliance - AWS Connector
Pull compliance evidence from AWS - EC2, IAM, S3, KMS, CloudTrail, RDS, VPC flow logs - and aggregate it with on-prem and Patrii Cloud evidence in a single register.
Hybrid customers run real workloads in AWS; their compliance scope does too. This connector implements the connectors-framework pattern with boto3, exposes nine resource types as evidence pulls, and ships a seeded collector pack for the controls AWS auditors examine first - public S3 buckets, IAM users without MFA, untracked access keys, KMS keys missing rotation, CloudTrail trails not multi-region.
Key Features
AWS connector type - configure with an access key + secret; supports IAM-role-assume on top.
Nine resource pulls - EC2 instances, security groups, IAM users (with MFA + access-key state), IAM roles, S3 buckets, KMS keys, CloudTrail trails, RDS instances, VPCs (with flow-log state).
Pre-seeded collectors - control evidence for the most-audited AWS misconfigurations ready to run on install.
Multi-account ready - one connector record per AWS account; collectors aggregate across accounts in the same evidence register.
Hybrid view - combined with the Patrii Cloud connector, evidence from both clouds lives in one auditor-visible list.
Integrates With
lynx_compliance_connectors - registers under the connector framework.
lynx_compliance_evidence_collectors - shipped collectors use the standard schedule.
AWS via boto3.
Try Lynx Compliance - AWS Connector on your team.
Free trial, no credit card. Talk to sales when you're ready.