Question 1

Is associate_public_ip_address enforced for AWS Well-Architected Framework v10?

Accepted Answer

Yes, Manage access to the AWS Cloud by ensuring AWS Elastic Compute Cloud (AWS EC2) instances cannot be publicly accessed.

Question 2

Is ebs_volumes enforced for AWS Well-Architected Framework v10?

Accepted Answer

Yes, Because sensitive data can exist and to help protect data at rest, ensure encryption is enabled for your AWS Elastic Block Store (AWS EBS) volumes.

Question 3

Is iam_instance_profile enforced for AWS Well-Architected Framework v10?

Accepted Answer

Yes, Ensure that an AWS Elastic Compute Cloud (AWS EC2) instance has an Identity and Access Management (IAM) profile attached to it. This rule is non-compliant if no IAM profile is attached to the AWS EC2 instance.

Question 4

Is metadata_options enforced for AWS Well-Architected Framework v10?

Accepted Answer

Yes, Ensure the Instance Metadata Service Version 2 (IMDSv2) method is enabled to help protect access and control of AWS Elastic Compute Cloud (AWS EC2) instance metadata.

Question 5

Is security_group_ingress_rules enforced for AWS Well-Architected Framework v10?

Accepted Answer

Yes, This control checks whether the VPC security groups allow ingress from 0.0.0.0/0 or ::/0 to cassandra ports 7199 or 9160 or 8888. This control passes when none of the rules in a security group allow ingress traffic from 0.0.0.0/0 from ports 7199 or 9160 or 8888.

AWS EC2 Instance Terraform module

Terraform Module Source