SOA-C02 Reviews Questions

In AWS, each subnet has a fixed CIDR block, and the number of available IP addresses is determined by this block. For example, a /28 subnet provides 16 IP addresses, but 5 are reserved by AWS, leaving 11 usable IPs.

Since the subnet is already at capacity:

Create a New Subnet:

Choose a CIDR block that doesn't overlap with existing subnets.

Ensure it's within the VPC's CIDR range.

Launch additional EC2 instances in this new subnet.

This approach allows for the deployment of more instances without modifying existing subnets.

The MixedInstancesPolicy feature in Auto Scaling groups allows for the configuration of both On-Demand and Spot Instances within a single Auto Scaling group, balancing cost savings and high availability:

MixedInstancesPolicy: Enables configuration to maintain a minimum of three On-Demand Instances and add Spot Instances when prices drop, without the need to create separate launch templates.

Setting Maximum Spot Price: Ensures that additional Spot Instances are launched only when within the defined budget.

This solution offers the least management overhead, as it combines both On-Demand and Spot instances seamlessly in one configuration.

To host a static website on Amazon S3, the SysOps administrator needs to configure the bucket for public access and set up the static website hosting. Here's how to complete this process:

Turn off "Block all public access": Amazon S3 buckets have "Block all public access" settings enabled by default for security. Since the webpage needs to be accessible publicly, this setting must be disabled. This step is crucial to allow public read access to the web content.

Set a bucket policy: After disabling "Block all public access," set a bucket policy that explicitly allows public read access to the S3 bucket. This policy should allow the s3:GetObject action for everyone, which can be set by specifying "Principal": "*". This policy ensures that anyone can view the webpage but does not grant permissions to modify or delete the content.

Create an index.html document and configure static website hosting: The next step is to create an index.html file, which will serve as the entry point of the website. After creating this file, upload it to the bucket. Then, configure the bucket for static website hosting through the S3 management console. This setting enables the S3 bucket to serve the webpage directly from the index.html file.

Combining these actions, the S3 bucket will be properly configured to host and serve the static website with minimal operational overhead and maximum accessibility.

To resolve DNS names for on-premises resources from EC2 instances in a VPC, you use Amazon Route 53 Resolver outbound endpoints to forward DNS queries to on-premises DNS servers.

From the Route 53 Resolver documentation:

Resolver outbound endpoints allow DNS queries from resources in your VPC to be forwarded to DNS servers in your on-premises network over Direct Connect or VPN.