AWS Tutorial AWS Solutions Architect and SysOps Administrator - Network ACLs Versus Security Groups

This lecture explains the differences between Network ACL and Security Group in AWS. Security Groups operate at the instance level and are stateful, meaning inbound rules automatically apply to outbound traffic. Network ACLs operate at the subnet level and are stateless, requiring explicit rules for both inbound and outbound traffic. The video also demonstrates how to create and manage Network ACLs using the AWS Management Console.

What level do Security Groups operate at in AWS?

• VPC level

• Instance level

• Region level

• Subnet level

Which of the following is true about Network ACLs?

• They operate at the instance level.

• They are stateful and have only allow rules.

• They are mandatory for all EC2 instances.

• They are stateless and can have both allow and deny rules.

How are rules evaluated in a Security Group?

• Collectively, before making a decision

• Only the first rule is evaluated

• Randomly

• In numerical order

What happens if you do not create a custom Network ACL?

• All traffic will be allowed by default.

• No traffic will be allowed in the subnet.

• The subnet will use the default Network ACL.

• The subnet will not be created.

What is the first step in creating a custom Network ACL in AWS?

• Specify the inbound rules

• Select the VPC

• Specify the outbound rules

• Choose the protocol type

When configuring a custom Network ACL, what must be done to allow a port in both directions?

• Specify the port in the inbound rules only

• Specify the port in the outbound rules only

• Specify the port in both inbound and outbound rules

• No need to specify, it is allowed by default

What is the purpose of associating a Network ACL with a subnet?

• To allow all traffic by default

• To ensure all instances in the subnet follow the ACL rules

• To automatically create security groups

• To create a new VPC