CodePipeline not running and no logs visible in execution details in us-east-1 region

Question

Hello AWS Support Team,

I’m facing an issue with my pipeline in the US East (N. Virginia) region.
The pipeline is not running any stages when triggered, and under Pipeline execution details → Logs, both CloudWatch and S3 log fields are blank.

Here’s what I have observed:
around 1h ago my pipeline is working but now no pipeline is working.

No stages show as “In Progress” or “Failed”; the pipeline simply remains idle.

CloudWatch log group and stream names are not being populated.

I verified that my CodeBuild and CodePipeline service roles have appropriate permissions.

I have also confirmed that the pipeline definition and source stage are configured correctly.

When I trigger the pipeline manually, nothing executes and there are no logs generated.
codebuild stuck
![codebuild issue](/media/postImages/original/IMMQA97rouR8iubILE3bzMTw)

Could you please help investigate why the pipeline execution is not starting and why no logs are being generated or linked in the AWS console?

re:Post Agent · Answer

When your CodePipeline isn't running and no logs are visible in the execution details, there are several potential causes to investigate:

1. **IAM Permissions Issue**: Your console role might be missing the required permissions to view compute logs. Specifically, you need the `logs:GetLogEvents` permission. Make sure your role has a policy statement that allows this action for your pipeline's log group:
```
{
"Effect": "Allow",
"Action": [
"logs:GetLogEvents"
],
"Resource": "arn:aws:logs:*:YOUR_AWS_ACCOUNT_ID:log-group/aws/codepipeline/YOUR_PIPELINE_NAME:*"
}
```

2. **Region Mismatch**: Verify that the log group is in the same region as your pipeline (us-east-1). The console can only display logs from CloudWatch Logs groups in the same region as the pipeline.

3. **Log Configuration**: Check if your task definitions have the correct log configuration. The log driver should be set to 'awslogs' for CloudWatch Logs integration.

4. **Log Group Existence**: Confirm that the specified log group exists in CloudWatch. If you're using a new log group name, make sure it's being created correctly.

5. **Console Display Issues**: Sometimes the AWS Management Console can have caching issues. Try clearing your browser cache and cookies, or use a different browser.

6. **Disk Space**: If you're using Jenkins with CodePipeline, check if there's sufficient disk space on the Jenkins EC2 instance.

7. **Pipeline Stuck**: If the pipeline is stuck, you may need to manually intervene. Look for options like "Try again" or "Repeat failed action" in the CodePipeline console.

To troubleshoot further, I recommend:
- Check CloudWatch Logs directly to see if logs are being written there
- Verify IAM permissions for all relevant service roles
- Review your pipeline configuration for any errors
- Try creating a new log group and see if it appears in the console  
**Sources**  
[Permissions required to view compute logs in the CodePipeline console - AWS CodePipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/security-iam-permissions-console-logs.html)  
[AWS Blu Age Devops Pipeline : Failed | AWS re:Post](https://repost.aws/questions/QU8tZLkvjnQwG7cvSSeo2UCA/aws-blu-age-devops-pipeline-failed)  
[New deployed Services/Tasks do not show logs anymore | AWS re:Post](https://repost.aws/questions/QUL8LRsnRYSXOGyEzq_h43pQ/new-deployed-services-tasks-do-not-show-logs-anymore)  
[CloudWatch no log groups | AWS re:Post](https://repost.aws/questions/QUaXhzgl5WQyC0W5qnV4QQDw/cloudwatch-no-log-groups)

CodePipeline not running and no logs visible in execution details in us-east-1 region

Add your answer

Relevant content