AWS DevOps Engineer Professional Practice Test

Which deployment targets for AWS CodeDeploy are not eligible for selection by tags?

1. ECS Cluster and Lambda

2. EC2 Instances and ECS Tasks

3. Lambda and EC2 Tasks

4. On-Premise Instances and Lambda

The correct answer is: ECS Cluster and Lambda

In the context of AWS CodeDeploy, certain deployment targets have specific eligibility rules regarding the use of tags for selection. The correct choice states that ECS Cluster and Lambda are not eligible for selection by tags. When using AWS CodeDeploy, tags are a key mechanism for identifying specific resources, like EC2 instances, that should receive updates during a deployment. However, both ECS Clusters and Lambda functions operate under different constructs. ECS Clusters are collections of services and tasks that run on Amazon EC2 instances, but the selection of ECS service tasks in deployments relies primarily on the specifics of the ECS service configuration rather than tag-based targeting. AWS CodeDeploy does not support tagging for directly selecting ECS services for deployment. Lambda functions, on the other hand, are serverless compute services that are invoked in response to events. CodeDeploy itself does not use tags to target or select Lambda functions for deployment because Lambda uses different deployment strategies, such as direct deployment to the function without the architectural need for tags that would allow grouping or selective deployment. This distinction clarifies that the deployment targets responsible for managing application versions and updates via AWS CodeDeploy must be explicitly identified through mechanisms other than tags when dealing with ECS Clusters and Lambda functions. In contrast, EC2