A logistics firm runs a vehicle tracking application on Amazon EC2 instances within a specific subnet in a Virtual Private Cloud (VPC). The security team must implement a solution that allows incoming HTTPS traffic to the EC2 instances from a trusted corporate partner's IP address range. Additionally, they must block all inbound traffic from a known malicious IP range at the subnet boundary. Which combination of AWS network security actions will meet these requirements? (Select TWO.)
- Create an inbound rule in the Security Group associated with the EC2 instances to allow HTTPS traffic from the partner's IP address rangeCevap
- Create an inbound deny rule in the Network Access Control List (Network ACL) associated with the subnet to block the malicious IP rangeCevap
- CCreate an inbound deny rule in the Security Group associated with the EC2 instances to block the malicious IP range
- DConfigure Amazon GuardDuty to block traffic from the malicious IP range before it reaches the Virtual Private Cloud (VPC)
- EDeploy Amazon Inspector to monitor network routing tables and drop packets originating from the malicious IP range
Cevap
The correct actions are to create an inbound allow rule in a Security Group for the trusted partner's IP range, and to create an inbound deny rule in a Network ACL for the malicious IP range.
To allow traffic to specific EC2 instances, you configure an inbound allow rule in a Security Group, which operates at the instance level. To block a malicious IP range at the subnet boundary, you configure an inbound deny rule in a Network ACL, which operates at the subnet level and supports explicit deny rules.
Adım Adım Çözüm
Anahtar Kavram
The difference between instance-level stateful Security Groups and subnet-level stateless Network ACLs in AWS VPC architecture.
Tahmini Süre:1m 30s