Changelog

AWS compliance defaults

What Alien creates in a customer's AWS account now meets the checks their security tools run, such as AWS Security Hub and CIS, with no change to your stack:

  • Alarms: CloudWatch alarms on each load balancer (unhealthy hosts, response time, 5xx), each Aurora writer (CPU, memory, disk queue), and each Auto Scaling group (CPU). They have no actions, so they never page anyone or change anything.
  • VPC flow logs: every VPC Alien creates records its traffic to a CloudWatch log group. Default VPCs and VPCs you bring are left alone.
  • Logs kept a year: CloudWatch log groups keep 365 days.
  • DynamoDB: point-in-time recovery is on for every table.
  • S3: every bucket aborts multipart uploads left incomplete for 7 days. Stored objects are never expired, moved, or deleted.
  • TLS: HTTPS listeners use a FIPS policy with TLS 1.2 or later, and HTTP redirects to HTTPS on container and daemon load balancers.
  • Aurora Postgres: pgaudit is loaded, the text of failing statements stays out of the logs, and snapshots carry the cluster's tags.

New deployments get all of these. Existing deployments get the ones Alien manages at runtime with their next release, and the ones initial setup creates, such as flow logs on a setup-created VPC, when initial setup runs again. Until then, a missing permission shows as a warning and the deployment keeps running.