Master AWS Certifications with Confidence

AWS Lambda

AWS Batch

AWS Application Composer

AWS App Runner

AWS Config

AWS Organizations

AWS Budgets

Cost Explorer

Create an S3 bucket lifecycle policy to transition files from S3 Standard to S3 Glacier 15 days after creation. Delete the files 3 years after creation.

Create an S3 bucket lifecycle policy to transition files from S3 Standard to S3 One Zone-Infrequent Access (S3 One Zone-IA) 15 days after creation. Delete the files 3 years after creation.

Create an S3 bucket lifecycle policy to transition files from S3 Standard to S3 Standard-Infrequent Access (S3 Standard-IA) 15 days after creation. Delete the files 3 years after creation.

Create an S3 bucket lifecycle policy to transition files from S3 Standard to S3 Standard-IA 15 days after creation. Move the files to S3 Glacier 3 years after creation.

Use Amazon ECR as the container registry. Enable automated scanning on image push and configure a scheduled scan for existing images using ECR's built-in features.

Store images in an Amazon S3 bucket. Use Amazon Inspector to scan images upon upload via S3 Event Notifications and set up an AWS Lambda function to trigger weekly scans.

Migrate the container workloads to AWS Fargate. Use Amazon ECR with enhanced scanning enabled to automatically scan images on push and perform recurring scans.

Implement a third-party image scanning tool integrated through AWS Lambda. Configure Amazon EventBridge to trigger scans on image push events and weekly rescans.

In the production account, create an IAM policy that grants read and write access to the S3 bucket.

In the development account, create an IAM policy that grants read and write access to the S3 bucket.

In the production account, create an IAM role. Attach the policy to the role and specify the development account as a trusted entity.

In the development account, create an IAM role. Attach the policy to the role and specify the production account as a trusted entity.

In the development account, create an IAM group for the analytics team members. Attach a policy that allows the sts:AssumeRole action on the role in the production account.

In the development account, create an IAM group for the analytics team members. Attach a policy that allows the sts:AssumeRole action on the role in the development account.

Create an S3 Multi-Region Access Point and update the application to use it for object access

Configure bidirectional S3 Cross-Region Replication (CRR) between the two S3 buckets

Modify the application to write objects to both S3 buckets simultaneously

Implement an S3 Lifecycle policy to automatically transfer objects between the buckets

Enable S3 Versioning on both S3 buckets

Set up S3 event notifications to trigger AWS Lambda functions for cross-bucket object replication

Modify the application to publish a custom metric to CloudWatch. Set up a CloudWatch alarm with an SNS topic for notifications.

Create a Lambda function that checks CloudWatch Logs every 10 minutes for AUTH_FAILURE. Configure it to trigger SNS notifications.

Use CloudWatch Logs to create a metric filter for AUTH_FAILURE. Create an alarm on this metric (threshold >=1) linked to an SNS topic.

Install the CloudWatch agent on EC2 to collect custom metrics for AUTH_FAILURE errors and send notifications via SNS.

Separately package the machine learning library with each Lambda function in individual .zip files, maintaining independent deployments.

Create a shared Lambda layer containing the machine learning library and attach it to both Lambda functions.

Merge both Lambda functions into a single function with conditional logic, deployed as one .zip archive.

Store the machine learning library in an S3 bucket and configure Lambda functions to download it during execution.