Inside the AWS connector (Beta): what we read, and the key you create

EC2, RDS, S3, IAM, ACM, Secrets Manager, GuardDuty and more — what we read, what we never touch, and an honest note on how far it has been tested.

The AWS connector is in Beta. Its scanners are verified against emulated AWS APIs; they have not yet been validated on a live customer account. Treat the list below as what the code reads, not as a track record.

Today the connector authenticates with an access key for a dedicated IAM user that you create, carrying a metadata-only policy (shown in full in the onboarding wizard) or the AWS-managed SecurityAudit policy. A cross-account role with an external ID is the pattern we want to move to; role assumption is not implemented yet. The key is encrypted at rest, and you can rotate or delete it in IAM at any time.

1. Compute

2. Data

3. Identity

IAM — access key age, MFA posture, root account usage and general credential hygiene. The classic finding: a console user with an old access key and no MFA. We do not compute effective permissions or privilege-escalation paths.

4. Networking & edge

Security groups open to 0.0.0.0/0 on a sensitive port (or every port), unused security groups, default-VPC use, VPC Flow Logs disabled. Load balancers, CloudFront distributions, API Gateway, WAF, and SQS/SNS each get configuration checks. Route 53: registered-domain expiry, CNAMEs that point at something deleted, health-check coverage.

5. Security services

6. Backups and quotas

AWS Backup and RDS automated snapshots: each protected resource's newest recovery point against how often its plan runs, failed backup jobs in the last seven days, and databases nothing backs up. Service Quotas: usage against your applied quotas, flagged at 80% and 95%.

7. Cost

The AWS Cost Explorer page reads Cost Explorer when an account admin refreshes it, and caches the result. A nightly spend check — a day well above the week before it, and AWS Budgets reaching 75, 90 and 100% or forecast to pass them — is off unless it is switched on for your account, because each Cost Explorer request is billed to your AWS account (about a cent; roughly 30 cents a month per connection).

What the AWS connector does NOT do

GuardDuty, Security Hub and AWS Health findings — things AWS has already raised — are read every 5 minutes on a paid plan (every 15 during a trial). Exposure scans — public S3 access, world-open security groups, unauthenticated API Gateway routes, ECS tasks with public IPs — run every hour. Expiry and posture scans — ACM certificates, IAM access key age, Secrets Manager rotation, Route 53 domain expiry, backups and quotas — run once a night. An account administrator can ask for a fresh scan of a connection, at most once every 15 minutes per account; it runs with the next hourly scan, and while CloudMonitor is pre-launch nothing scans during the part of each day the service is powered down (see the Terms). Setup steps and the policy are on the Connectors page.

← Back to all posts