DOP-C02 Exam Dumps : AWS Certified DevOps Engineer - Professional

Using CodePipeline + CodeConnections Git repo provides version control, automated deployment, and rollback. Each template includes AWS::ControlTower::EnableControl for OU-level guardrails. AWS Control Tower documentation recommends this GitOps automation model.

Activate Amazon Macie on the Production S3 Bucket:

Macie can identify and protect sensitive data such as PII.

Create a Step Functions state machine to automate data discovery and redaction before copying it to the development environment.

Example Step Functions state machine:

{

" Comment " : " Anonymize PII and copy data " ,

" StartAt " : " MacieDiscoveryJob " ,

" States " : {

" MacieDiscoveryJob " : {

" Type " : " Task " ,

" Resource " : " arn:aws:states:::macie:startClassificationJob " ,

" End " : true

}

}

}

Create a Development Environment from CloudFormation Template:

Deploy the development environment in a new account using the existing CloudFormation template.

Schedule an EventBridge rule to start the Step Functions state machine on a weekly basis.

EventBridge rule example:

{

" ScheduleExpression " : " rate(7 days) " ,

" StateMachineArn " : " arn:aws:states: < region > : < account-id > :stateMachine:AnonymizeAndCopyData "

}

By using Macie for data anonymization and Step Functions for automation, you ensure PII is properly handled before data transfer between environments.

When using the awslogs log driver with Amazon ECS on EC2, CloudWatch Logs permissions must be granted to the ECS container instance IAM role , not the task definition or infrastructure role. The ECS agent running on the EC2 instances is responsible for creating log streams and pushing log events to Amazon CloudWatch Logs on behalf of the containers.

In this scenario, the task definition is correctly configured to automatically create the log group (awslogs-create-group: true) and send logs to the specified Region. However, the error occurs because the EC2 container instances do not have sufficient IAM permissions to perform the required CloudWatch Logs API calls. As a result, ECS cannot place the task, and it reports that no container instance meets the requirements.

According to AWS documentation, the container instance IAM role must include the following permissions when using the awslogs driver:

logs:CreateLogStream

logs:PutLogEvents

(and, when creating log groups automatically) logs:CreateLogGroup

Option C correctly addresses the root cause by updating the container instance IAM role . Option A is incorrect because the ECS infrastructure or service role is not used to write logs. Option B is unrelated to permissions and does not resolve the issue. Option D would fail because the log group does not already exist, causing task startup to fail.

Therefore, modifying the container instance IAM role is the correct solution.