A DevOps engineer deploys a new application version with AWS CodeDeploy to EC2 instances. The deployment later fails; all events for the deployment ID show Skipped and no code was applied to the instances in the deployment group. Which of the following are valid causes? (Choose two.)

The correct answers are that the instances cannot reach the internet and the EC2 instances do not have an instance profile attached. If instances cannot reach the CodeDeploy service endpoint (e.g., due to missing internet or NAT gateway), they cannot receive deployment commands, leading to a "Skipped" status. Similarly, if the EC2 instances lack an instance profile with permissions for CodeDeploy to interact with them, the service cannot perform actions on those instances, resulting in skipped deployments. The IAM user who started the deployment lacking permissions would prevent the deployment from being initiated at all, not just skipped on the instances. EC2 instances not being properly registered with CodeDeploy would typically result in them not being part of the deployment group, or the deployment failing with a different error, not "Skipped" on all events. An omitted appspec.yml file would cause a deployment failure during the lifecycle events, not a "Skipped" status before any code is applied.