Master AWS Certifications with Confidence

Ensure the physical security of the data centers.

Manage the encryption keys used for database storage.

Install and maintain the server hardware.

Apply patches to the RDS database engine.

Program and project management

Workforce planning

Observability

Change and release management

Migrate all video files to Amazon S3. Configure the applications to access files directly from S3 using API calls.

Create a new EBS volume and copy all files to it. Attach the volume to multiple EC2 instances simultaneously.

Mount an Amazon Elastic File System (EFS) file system to all EC2 instances. Direct editors to access files via the shared EFS mount point.

Create an Amazon Machine Image (AMI) with the video files stored on an instance store. Launch new instances from the AMI for editors to access files.

Store the datasets in Amazon S3 and use Amazon Redshift to execute complex JOIN queries for finding connections.

Utilize Amazon Neptune to model the data as a graph with nodes and edges, then traverse the graph to find mutual followers.

Store the datasets in Amazon DynamoDB tables and use batch operations to recursively search for connections.

Use Amazon OpenSearch Service to index the datasets and perform search queries to discover connections.

Create IAM policies with explicit Allow conditions for approved Regions and attach them to all IAM roles and users in each account.

Use AWS Organizations to create IAM groups with Deny policies for non-approved Regions and assign users to these groups across accounts.

Establish an AWS Organizations structure, create a Service Control Policy (SCP) that denies actions in non-approved Regions, and attach it to the organization's root Organizational Unit (OU).

Deploy AWS Config aggregators in a central account and define rules to flag resources in unapproved Regions, triggering automated remediation.

Use AWS Resource Groups to identify untagged resources. Create cost allocation tags for cost center and project ID, then use AWS Lambda to retroactively tag resources. Rely on CloudFormation stack policies to enforce tagging for new resources.

Deploy AWS Organizations tag policies to enforce tagging standards. Use AWS Config to remediate non-compliant existing resources and apply cost allocation tags. Allow 48 hours for tags to appear in cost reports.

Use Tag Editor to apply missing tags to existing resources. Create cost allocation tags for cost center and project ID. Implement SCPs to block resource creation without required tags across all accounts.

Enable AWS Cost Explorer to analyze untagged resources. Create a cross-account IAM role to tag existing resources via CLI. Modify CloudFormation templates to include tags and enforce via code reviews.

Apply a CloudFormation Deletion Policy with the Retain value to the database resource.

Implement a stack policy that blocks updates to the database resource.

Configure the database to use Provisioned IOPS storage.

Use a CloudFormation stack set to manage deployments across environments.

Enable versioning for the CloudFormation template to track changes.

Replicate the customer managed KMS key from Account A to Account B. Specify Account A in the key policy.

Create a new customer managed KMS key in Account B. Specify Account A in the key policy.

Create a new AWS managed KMS key for Amazon S3 in Account B. Specify Account A in the key policy.

Replicate the default AWS managed KMS key for Amazon S3 from Account A to Account B. Specify Account A in the key policy.