New: Become a sponsor via GitHub Sponsors!

This template creates a malware scanner cluster for S3 buckets. Connect as many S3 buckets as you like.

bucketAV - Antivirus for Amazon S3 with additional features is available at AWS Marketplace.

• Uses ClamAV to scan newly added files on S3 buckets
• Updates ClamAV database every 3 hours automatically
• Scales EC2 instance workers to distribute the workload
• Publishes a message to SNS in case of a finding
• Can optionally delete compromised files automatically
• Logs to CloudWatch Logs

• Reporting capabilities
• Dashboard
• Scan buckets at regular intervals / initial bucket scan
• Quarantine infected files
• Enhanced security features (e.g., IMDSv2)
• Regular Security updates
• Multi-Account support
• AWS Integrations:
  • CloudWatch Integration (Metrics and Dashboard)
  • Security Hub Integration
  • SSM OpsCenter Integration
• S3 -> SNS fan-out support
• Support

bucketAV - Antivirus for Amazon S3 with additional features is available at AWS Marketplace.

Visit the template's repository for installation instructions: aws-s3-virusscan

This template creates an account password policy for your IAM users. You can:

• set IAM user passwords to be valid for only the specified number of days.
• prevent IAM users from reusing a specified number of previous passwords.
• specify the minimum number of characters allowed in an IAM user password.
• require that IAM user passwords contain at least one lowercase character from the ISO basic Latin alphabet (a to z).
• require that IAM user passwords contain at least one uppercase character from the ISO basic Latin alphabet (A to Z).
• require that IAM user passwords contain at least one numeric character (0 to 9).
• require that IAM user passwords contain at least one nonalphanumeric character.
• permit all IAM users in your account to use the IAM console to change their own passwords.
• prevent IAM users from choosing a new password after their current password has expired.

Or just use the suggested defaults.

1. 
2. Click Next to proceed with the next step of the wizard.
3. Specify a name and all parameters for the stack.
4. Click Next to proceed with the next step of the wizard.
5. Click Next to skip the Options step of the wizard.
6. Check the I acknowledge that this template might cause AWS CloudFormation to create IAM resources. checkbox.
7. Click Create to start the creation of the stack.
8. Wait until the stack reaches the state CREATE_COMPLETE

This template describes a highly available authentication proxy that forwards request to a upstream http(s) endpoint if the user is authenticated against your GitHub Organization.

1. This template depends on one of our vpc-*azs.yaml templates.
2. 
3. Click Next to proceed with the next step of the wizard.
4. Specify a name and all parameters for the stack.
5. Click Next to proceed with the next step of the wizard.
6. Click Next to skip the Options step of the wizard.
7. Check the I acknowledge that this template might cause AWS CloudFormation to create IAM resources. checkbox.
8. Click Create to start the creation of the stack.
9. Wait until the stack reaches the state CREATE_COMPLETE

• vpc/vpc-*azs.yaml (required)
• vpc/vpc-*-bastion.yaml (recommended)
• operations/alert.yaml (recommended)

• By default, only one EC2 instance is managed by the ASG. In case of an outage the instance will be replaced within 5 minutes. You can change this in the ASG configuration!

This template enables CloudTrail to records AWS API calls across all regions in your AWS account. API calls are archived in S3 and also pushed CloudWatch Logs. If new API calls are available in S3 a SNS topic is notified.

1. 
2. Click Next to proceed with the next step of the wizard.
3. Specify a name and all parameters for the stack.
4. Click Next to proceed with the next step of the wizard.
5. Click Next to skip the Options step of the wizard.
6. Check the I acknowledge that this template might cause AWS CloudFormation to create IAM resources. checkbox.
7. Click Create to start the creation of the stack.
8. Wait until the stack reaches the state CREATE_COMPLETE

If you want to use an external S3 bucket, the bucket needs to have the following S3 bucket policy:

{
  "Version": "2012-10-17",
  "Statement": [{
    "Sid": "AWSCloudTrailAclCheck",
    "Effect": "Allow",
    "Principal": {
      "Service": "cloudtrail.amazonaws.com"
    },
    "Action": "s3:GetBucketAcl",
    "Resource": "arn:aws:s3:::$ExternalTrailBucket"
  }, {
    "Sid": "AWSCloudTrailWrite",
    "Effect": "Allow",
    "Principal": {
      "Service": "cloudtrail.amazonaws.com"
    },
    "Action": "s3:PutObject",
    "Resource": [
      "arn:aws:s3:::$ExternalTrailBucket/AWSLogs/$AccountId[0]/*",
      "arn:aws:s3:::$ExternalTrailBucket/AWSLogs/$AccountId[1]/*",
      "arn:aws:s3:::$ExternalTrailBucket/AWSLogs/$AccountId[2]/*"
    ],
    "Condition": {
      "StringEquals": {
        "s3:x-amz-acl": "bucket-owner-full-control"
      }
    }
  }]
}

Replace $ExternalTrailBucket with the name of your bucket, and add a row for every account you want to write from $AccountId[*].

This template enables AWS Config to deliver a AWS resource inventory to S3. Allowing you to keep track of infrastructure changes for compliance and debugging of your cloud infrastructure.

1. 
2. Click Next to proceed with the next step of the wizard.
3. Specify a name and all parameters for the stack.
4. Click Next to proceed with the next step of the wizard.
5. Click Next to skip the Options step of the wizard.
6. Check the I acknowledge that this template might cause AWS CloudFormation to create IAM resources. checkbox.
7. Click Create to start the creation of the stack.
8. Wait until the stack reaches the state CREATE_COMPLETE

If you want to use an external S3 bucket, the bucket needs to have the following S3 bucket policy:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "AWSConfigBucketPermissionsCheck",
      "Effect": "Allow",
      "Principal": {
        "Service": [
         "config.amazonaws.com"
        ]
      },
      "Action": "s3:GetBucketAcl",
      "Resource": "arn:aws:s3:::$ExternalConfigBucket"
    },
    {
      "Sid": " AWSConfigBucketDelivery",
      "Effect": "Allow",
      "Principal": {
        "Service": [
         "config.amazonaws.com"
        ]
      },
      "Action": "s3:PutObject",
      "Resource": [
        "arn:aws:s3:::$ExternalConfigBucket/AWSLogs/$AccountId[0]/Config/*",
        "arn:aws:s3:::$ExternalConfigBucket/AWSLogs/$AccountId[0]/Config/*",
        "arn:aws:s3:::$ExternalConfigBucket/AWSLogs/$AccountId[2]/Config/*"
      ],
      "Condition": {
        "StringEquals": {
          "s3:x-amz-acl": "bucket-owner-full-control" 
        }
      }
    }
  ]
}

Replace $ExternalTrailBucket with the name of your bucket, and add a row for every account you want to write from $AccountId[*].

This template provides a KMS customer managed CMK used by AWS services. Access control via IAM is also enabled. In case of a CMK deletion, a event is forwarded to the ParentAlertStack (if specified).

ATTENTION: If you delete a stack based on this template, the KMS CMK is NOT deleted to prevent data loss! Mark the CMK for deletion if you really want to delete the CMK! All resources encrypted with the CMK (including RDS snapshots) are unusable after the deletion!

1. 
2. Click Next to proceed with the next step of the wizard.
3. Specify a name and all parameters for the stack.
4. Click Next to proceed with the next step of the wizard.
5. Click Next to skip the Options step of the wizard.
6. Click Create to start the creation of the stack.
7. Wait until the stack reaches the state CREATE_COMPLETE

If you have an existing KMS customer managed CMK you can wrap it into our required form using a legacy KMS customer managed CMK wrapper:

• operations/alert.yaml (recommended)

This templates provides a WebACL with preconfigured rules.

1. 
2. Click Next to proceed with the next step of the wizard.
3. Specify a name and all parameters for the stack.
4. Click Next to proceed with the next step of the wizard.
5. Click Next to skip the Options step of the wizard.
6. Click Create to start the creation of the stack.
7. Wait until the stack reaches the state CREATE_COMPLETE

If you have an existing WEB ACL, or if you need a WAF for CloudFront in a different region, you can wrap it into our required form using a legacy WAF wrapper: