CodeDeploy deployment group not reflecting instance

Question

Created CodeDeploy Application and deployment group for a single EC2 instance, the deployment group has AWSCodeDeployRole and EC2 instance has AmazonEC2RoleforAWSCodeDeploy I manually installed codedeploy agent on instance and it is up and running, codedeploy logs has: [Aws::CodeDeployCommand::Client 200 45.496785 0 retries] poll_host_command(host_identifier:arn__), Still CodeDeploy I am in same region using correct tag and a valid session and have relevant permissions still 
Deployment Group show: 
Resource not available
The resource that you are trying to view either doesn’t exist in this AWS Region, or you are signed in without the permission required to view it.
Make sure that you are viewing resources in the AWS Region where that resource was created. Use the region selector to change regions.
Make sure that you have spelled the resource name correctly. Try searching for the resource by name
Make sure that your session has not expired. Try signing in again and then searching for the resource. Refresh
Make sure that you are signed in with a user or role that has permission to view resources for this service

M Zubair Bin Ramzan · Answer

It looks like you're running into a couple of potential issues related to AWS CodeDeploy not recognizing your EC2 instance within the deployment group. Here are some steps to troubleshoot and resolve the problem:

1. Verify Region
Ensure you're in the correct region: Double-check that the CodeDeploy application and deployment group were created in the same AWS region as your EC2 instance.
Sometimes the AWS Management Console can show different regions, and it's easy to overlook that you’re in a different region than where the deployment group was created.

Confirm region consistency across both the CodeDeploy resources and EC2 instance.

2. Verify EC2 Tagging
Check that the EC2 instance has the correct tags:
Ensure that the EC2 instance is tagged with the same tag that is referenced in the deployment group’s tag-based deployment targeting.
The tags on the EC2 instance should match exactly with the tags specified in the CodeDeploy deployment group. Tags are case-sensitive, so ensure they are an exact match.

3. Verify Permissions
IAM Role Permissions:
Ensure the AmazonEC2RoleforAWSCodeDeploy has the correct permissions for interacting with CodeDeploy.
AWSCodeDeployRole should also be properly configured with the necessary permissions to interact with the EC2 instance.
Make sure that both roles have trust relationships set up correctly, allowing them to interact with each other as needed.

4. Check CodeDeploy Agent on EC2
Ensure CodeDeploy Agent is Running:
Check if the CodeDeploy agent on the EC2 instance is running properly. You can run the following command to verify its status:

sudo service codedeploy-agent status
If it’s not running, start it using:
                                                                                            sudo service codedeploy-agent start
Check Logs:
Review the CodeDeploy agent logs on the EC2 instance. You can find the logs in /var/log/aws/codedeploy-agent/:

tail -f /var/log/aws/codedeploy-agent/codedeploy-agent.log
Check for any errors or clues as to why the instance isn’t being recognized in the deployment group.

5. Confirm Instance Registration with CodeDeploy
Confirm Instance is Registered:

In the AWS Management Console, navigate to the EC2 instance and verify that it appears as an available instance in the deployment group.

If the instance is not listed under the deployment group, try refreshing or re-tagging the instance and ensuring that it matches the deployment group’s criteria.

You can also check using the CLI to confirm the instance is available to the CodeDeploy deployment group:

aws codedeploy list-deployment-groups --application-name 
                                                   aws codedeploy list-deployments --deployment-group-name 
6. Check CodeDeploy Deployment Group Configuration
Deployment Group Configuration:
Double-check the configuration of the CodeDeploy deployment group. Ensure that the deployment group type is set correctly (e.g., EC2/On-premises).
If you're using automatic deployment with tags, ensure that the tags used to target the EC2 instances are configured correctly.

7. Recheck Session and Permissions
IAM Permissions for the User:
Ensure that the IAM user or role you’re signed in with has the necessary permissions to access the CodeDeploy application and deployment group.
Ensure that the user has permission for actions like codedeploy:ListDeploymentGroups, codedeploy:DescribeApplications, etc.
If you're unsure, you can attach the AWSCodeDeployReadOnlyAccess policy to your IAM user to troubleshoot.

8. Check Deployment Group Availability
Verify the Resource Exists:
Sometimes the "Resource not available" message can be misleading. It could happen if the deployment group was deleted or corrupted.
Try creating a new deployment group and see if the EC2 instance gets recognized there.

9. Troubleshooting with AWS CLI
List Instances in the Deployment Group:
Use the AWS CLI to list the instances in the deployment group and verify the instance appears:
                                                aws codedeploy list-deployment-instances --deployment-group-name  -

CodeDeploy deployment group not reflecting instance

Relevant content