Master AWS Certifications with Confidence

When an application hosted in an on-premises data center requires temporary access to AWS services

When the company needs to provide AWS access via access keys for a third-party application that does not support role assumption

When granting permissions to an AWS Lambda function to interact with Amazon S3

When enabling cross-account access for users from another AWS account

When users are authenticated via AWS Single Sign-On (SSO) and require federated access

Encrypting data stored in the RDS database instance.

Ensuring the physical security of the RDS database servers and facilities.

Managing database user accounts and access permissions.

Configuring database backup retention policies.

Deploy the application as an AWS Lambda function using the container image. Configure Amazon EventBridge to trigger the Lambda function every 15 minutes.

Use AWS Batch with AWS Fargate compute resources. Schedule the job using Amazon EventBridge to run every 15 minutes.

Run the application on Amazon Elastic Container Service (Amazon ECS) using AWS Fargate. Configure a scheduled task to execute the container every 15 minutes.

Deploy the application on Amazon EC2 instances using the container image. Use a cron job on the EC2 instance to trigger the task every 15 minutes.

Configure security groups and NACLs to restrict access to the application and database.

Deploy AWS WAF to protect the application and use Aurora parameter groups to enforce security settings.

Implement AWS Shield Advanced for DDoS protection and use IAM policies to control database access.

Utilize separate database roles in the application code for each function, limiting privileges strictly.

Configure the SCP for Account X to permit the action.

Configure the resource-based policies in Account Y to permit the action.

Configure the identity-based policy on the user in Account X to permit the action.

Configure the identity-based policy on the role in Account Y to permit the action.

Configure the trust policy on the target role in Account Y to permit the action.

Configure a session policy to delegate permissions via the GetFederationToken API operation.

Create a private ECR repository. Apply a resource policy allowing ECR actions with a condition specifying aws:PrincipalOrgID matching the organization's ID. Configure a lifecycle policy to expire untagged images beyond the last three.

Create a public ECR repository. Define an IAM role with permissions for ECR access, allowing assumption by accounts within the organization via aws:PrincipalOrgID. Add a lifecycle rule to remove untagged layers exceeding three.

Set up a private ECR repository with a resource policy permitting ECR operations for organization account IDs. Schedule an AWS Lambda function triggered by EventBridge to delete untagged layers beyond three.

Use a public ECR repository with a VPC endpoint policy restricting access to organization accounts. Implement a daily Lambda function to manage untagged layer retention.

Add a Retry field in the Step Functions state machine definition, configuring it to retry on the Throttled error type with a maximum number of attempts.

Add a Throttle field in the Step Functions state machine definition, setting the maximum retry attempts.

Modify the Lambda function's configuration to increase its concurrency limit and set up a Dead Letter Queue for failed invocations.

Update the state machine to route throttled invocations to an Amazon SQS queue and configure a Lambda function to process messages from the queue with retries.

Create a new resource in the existing REST API. Configure a POST method for the new resource linked to the updated Lambda version. Deploy the changes to the existing stage.

Create a new stage for the REST API. Define a stage variable referencing the updated Lambda version. Configure the API Gateway Lambda integration to use the stage variable. Deploy the API to the new stage.

Build a new REST API. Add a resource with a POST method integrated with the updated Lambda version. Deploy the new API and test it independently.

Modify the existing POST method's Lambda integration to point to the updated Lambda version. Deploy the changes to the current stage.