View Deployment Details with AWS CodeDeploy
You can use the AWS CodeDeploy console, the AWS CLI, or the AWS CodeDeploy APIs to view details about deployments associated with your AWS account.
You can view deployment logs on your instances in the following locations:
Amazon Linux, RHEL, and Ubuntu Server:
Windows Server: C:\ProgramData\Amazon\CodeDeploy<DEPLOYMENT-GROUP-ID><DEPLOYMENT-ID>\logs\scripts.log
For more information, see Analyzing log files to investigate deployment failures on instances.
View Deployment Details (Console)
To use the AWS CodeDeploy console to view deployment details:
Sign in to the AWS Management Console and open the AWS CodeDeploy console at https://console.aws.amazon.com/codedeploy.
Sign in with the same account or IAM user information you used in Getting Started.
On the AWS CodeDeploy menu, choose Deployments to view a list of deployments and their details.
If no entries are displayed, make sure the correct region is selected. On the navigation bar, in the region selector, choose one of one of the regions listed in Region and Endpoints in the AWS General Reference. AWS CodeDeploy supports these regions only.
To see more details for a single deployment, in Deployments, choose the deployment ID.
View Deployment Details (CLI)
To use the AWS CLI to view deployment details, call the
command or the
batch-get-deployments command. You can call the
list-deployments command to get a list of unique deployment IDs to use
as inputs to the
get-deployment command and the
To view a list of deployment IDs, call the list-deployments command, specifying:
The name of the application associated with the deployment. To view a list of application names, call the list-applications command.
The name of the deployment group associated with the deployment. To view a list of deployment group names, call the list-deployment-groups command.
Optionally, whether to include details about deployments by their deployment status. (If not specified, all matching deployments will be listed, regardless of their deployment status.)
Optionally, whether to include details about deployments by their deployment creation start times or end times, or both. (If not specified, all matching deployments will be listed, regardless of their creation times.)