SOA-C02 Exam Dumps : AWS Certified SysOps Administrator - Associate (SOA-C02)

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

To restrict resource creation in unapproved regions across multiple AWS accounts efficiently, combining SCPs and Control Tower settings is effective:

SCP for Regional Restrictions: Create and apply an SCP that explicitly denies access to AWS services in unapproved regions. This policy will enforce region-based restrictions at the organizational unit or account level.

Control Tower Regional Governance: Adjust the settings in AWS Control Tower's landing zone to include governance for approved regions. This helps in maintaining a standard configuration that aligns with organizational policies regarding AWS regions.

AWS Documentation Reference:

For more information, check the AWS documentation on SCPs and AWS Control Tower:

Service Control Policies

AWS Control Tower.

To automate the process of disabling unused IAM user accounts that have not been active for 90 days, using an AWS Config managed rule with an AWS Systems Manager automation runbook is the most operationally efficient method.

Set Up AWS Config Managed Rule:

Open the AWS Config console.

Create a rule using the managed rule iam-user-no-policies-check.

Configure the rule to trigger when IAM users have not been active for 90 days.

AWS Systems Manager Automation Runbook:

Create a Systems Manager automation document (runbook) to disable the access keys for inactive IAM users.

Use the aws:executeAutomation action to disable access keys and passwords.

Schedule the Automation:

Use Amazon EventBridge (formerly CloudWatch Events) to schedule the automation to run periodically.

AWS Config Managed Rules

AWS Systems Manager Automation

Scheduling AWS Systems Manager Automation