Amazon Web Services Updated SOA-C02 Exam Questions and Answers by may

Objective:

Enforce corporate policy to prevent the creation of EC2 instances in unauthorized AWS Regions.

Using Service Control Policies (SCPs):

SCPs are an AWS Organizations feature that allow centralized control over permissions for all accounts in the organization.

By attaching an SCP to the root level of the organization, you can enforce the restriction across all accounts.

Solution Implementation:

Step 1: Open the AWS Organizations console.

Step 2: Create a new SCP with the following policy:

{

"Version": "2012-10-17",

"Statement": [

{

"Effect": "Deny",

"Action": "ec2:RunInstances",

"Resource": "*",

"Condition": {

"StringNotEquals": {

"aws:RequestedRegion": [

"us-east-1",

"us-west-2"

]

}

}

}

]

}

Replace "us-east-1" and "us-west-2" with the allowed Regions.

Step 3: Attach the SCP to the root level of the organization.

AWS References:

Service Control Policies (SCPs):SCP Best Practices

Restricting EC2 Regions with SCP:SCP Examples

Why Other Options Are Incorrect:

Option A: CloudTrail and EventBridge with Lambda are operationally less efficient and reactive rather than preventative.

Option B: IAM policies applied at the account level require manual configuration for each account, which is less efficient.

Option C: Permissions boundaries are more suited for controlling specific IAM user or role actions, not account-wide restrictions.

The issue of "request timed out" when pinging the public IP address of the EC2 instance could be due to the Network ACL (NACL) inbound rules.

Check NACL Inbound Rules:

Network ACLs act at the subnet level and can explicitly allow or deny traffic to or from a subnet.

Ensure that the NACL associated with the subnet containing the EC2 instance has inbound rules that allow ICMP traffic (which is used for ping).

Example rule to allow inbound ICMP traffic:

Rule Number: 100

Type: ICMP

Protocol: 1

Port Range: N/A (ICMP doesn't use ports)

Source: 0.0.0.0/0 (or specific IP range)

Allow/Deny: ALLOW

https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-restricting-access-to-s3.html

To ensure that users access objects in Amazon S3 by using only CloudFront URLs, the SysOps administrator should create an origin access identity (OAI) and grant it permissions to read objects in the S3 bucket.

Create an Origin Access Identity (OAI):

OAI is a special CloudFront user that you associate with your distribution to restrict access to the S3 bucket.

This ensures that only CloudFront can access the S3 bucket directly, and users must go through CloudFront to access the content.

Steps to Implement:

Open the CloudFront console.

Select your distribution and go to the "Origins and Origin Groups" tab.

Edit the S3 origin and create a new OAI or use an existing one.

Update the S3 bucket policy to grant the OAI read permissions.

Bucket Policy Example:

{

"Version": "2012-10-17",

"Statement": [

{

"Effect": "Allow",

"Principal": {

"AWS": "arn:aws:iam::cloudfront:user/CloudFront Origin Access Identity [OAI_ID]"

},

"Action": "s3:GetObject",

"Resource": "arn:aws:s3:::your-bucket-name/*"

}

]

}

Using an Origin Access Identity to Restrict Access to Your S3 Content

Amazon CloudFront is a global content delivery network (CDN) service that delivers your content with low latency and high transfer speeds. By distributing the static content (images and videos) to CloudFront edge locations, users in the United States and Europe can access the content from the nearest edge location, significantly improving the load times.

Create a CloudFront Distribution:

Open the Amazon CloudFront console at Amazon CloudFront Console.

Choose Create Distribution and select Web.

Specify the S3 bucket as the origin where your static content is stored.

Configure Distribution Settings:

Configure the settings, such as cache behaviors and SSL/TLS settings.

Optionally, configure additional features like geo-restriction and logging.

Update DNS Configuration:

Update your DNS records to point to the CloudFront distribution. This can be done via Amazon Route 53 or your DNS provider.

Monitor Performance:

Use CloudFront reports and logs to monitor the performance and adjust configurations if needed.

Amazon CloudFront Overview

Creating a CloudFront Distribution