Amazon CodeCatalyst is no longer open to new customers. Existing customers can continue to use the service as normal. For more information, see [How to migrate from CodeCatalyst](migration.md).

# Viewing the deployment logs
<a name="deploy-deployment-logs"></a>

You can view logs related to specific deploy actions to troubleshoot problems in Amazon CodeCatalyst.

You can view logs starting from a [workflow](workflow.md), or an [environment](deploy-environments.md).

**To view the logs of a deploy action starting from a workflow**

1. Open the CodeCatalyst console at [https://codecatalyst.aws/](https://codecatalyst.aws/).

1. Choose your project.

1. In the navigation pane, choose **CI/CD**, and then choose **Workflows**.

1. Choose the name of your workflow. You can filter by the source repository or branch name where the workflow is defined, or filter by workflow name or status.

1. Choose **Runs**.

1. Choose the workflow run that deployed your application.

1. In the workflow diagram, choose the action whose logs you want to view.

1. Choose the **Logs** tab and expand the sections to reveal the log messages.

1. To view more logs, choose the **Summary** tab, and then choose **View in CloudFormation** (if it's available) to view more logs there. You may need to sign in to AWS.

**To view the logs of a deploy action starting from an environment**

1. Open the CodeCatalyst console at [https://codecatalyst.aws/](https://codecatalyst.aws/).

1. Choose your project.

1. In the navigation pane, choose **CI/CD**, and then choose **Environments**.

1. Choose the environment into which your application was deployed.

1. In **Deployment activity**, find the **Workflow Run ID** column, and choose the workflow run that deployed your stack.

1. In the workflow diagram, choose the action whose logs you want to view.

1. Choose the **Logs** tab and expand the sections to reveal the log messages.

1. To view more logs, choose the **Summary** tab, and then choose **View in CloudFormation** (if it's available) to view more logs there. You may need to sign in to AWS.