Changed SOA-C02 Exam Questions

To identify who is creating the Elastic IP addresses, the following steps should be taken:

Enable CloudTrail Logging:

Ensure AWS CloudTrail is enabled to log all API activities in your AWS account.

When setting up an AWS managed VPN connection and creating a customer gateway resource, if the customer gateway device resides behind a NAT device, you should use the public IP address of the NAT device. This is because the VPN connection from AWS will be established to the public IP address that AWS can reach.

Identify the Public IP Address of the NAT Device:

Determine the public IP address assigned to the NAT device in front of the customer gateway.

Create Customer Gateway Resource:

Navigate to the VPC console in the AWS Management Console.

In the navigation pane, choose "Customer Gateways" and then click "Create Customer Gateway".

Enter a name for the customer gateway.

For the "IP Address", enter the public IP address of the NAT device.

Configure VPN Connection:

Create a VPN connection by navigating to the "VPN Connections" section and clicking "Create VPN Connection".

Select the created customer gateway and complete the VPN setup wizard.

Update Routing and Configuration:

Ensure that the routing configurations on both the AWS side and the on-premises side are updated to route traffic through the VPN connection.

Configure the customer gateway device (behind the NAT) to accept traffic from the NAT device and route it appropriately.

References:

AWS Managed VPN Connections

Customer Gateway Resource

Cookies.html

You can configure each cache behavior to do one of the following: Forward all cookies to your origin – CloudFront includes all cookies sent by the viewer when it forwards requests to the origin. loadbalancing/latest/application/sticky-sessions.html

By default, an Application Load Balancer routes each request independently to a registered target based on the chosen load-balancing algorithm.

AWS WAF (Web Application Firewall) helps protect your web applications from common web exploits and bots. A rate-based rule allows you to control the rate of requests to your application.

Create a Global-Scoped AWS WAF Web ACL:

Navigate to the AWS WAF console.

Create a new Web ACL and choose "Global" for the scope.

Set the default action to "Allow".

Configure a Rate-Based Rule:

Within the Web ACL, add a new rule and select "Rate-based rule".

Define the rate limit (e.g., 2000 requests per 5 minutes).

Set the action to "Block".

Associate Web ACL with CloudFront Distribution:

After creating the Web ACL and rule, go to your CloudFront distribution settings.

In the "General" tab, associate the Web ACL with your CloudFront distribution.

Review and Confirm:

Review the configuration and ensure the Web ACL is correctly associated with the CloudFront distribution.

References:

AWS WAF Rate-Based Rules

Associating AWS WAF with CloudFront