Menu
AWS CodeStar
User Guide

Troubleshooting AWS CodeStar

The following information might help you troubleshoot common issues in AWS CodeStar.

Project creation failure: A project was not created

Problem: When you try to create a project, you see a message that the creation failed.

Possible fixes: The most common reasons for failure are:

  • A project with that ID already exists in your AWS account, possibly in a different region.

  • The IAM user you used to sign in to the AWS Management Console does not have the permissions required to create a project.

  • The AWS CodeStar service role is missing one or more required permissions.

  • You have reached the maximum limit for one or more resources for a project (such as the limit on customer managed policies in IAM, Amazon S3 buckets, or pipelines in AWS CodePipeline).

Before you create a project, verify that you have the AWSCodeStarFullAccess policy applied to your IAM user. For more information, see AWS CodeStar Access Permissions Reference.

When you create a project, make sure that the ID is unique and meets the AWS CodeStar requirements. Be sure you selected the AWS CodeStar would like permission to administer AWS resources on your behalf check box.

To troubleshoot other issues, open the AWS CloudFormation console, choose the stack for the project you tried to create, and choose the Events tab. There might be more than one stack for a project. The stack names will start with awscodestar-, followed by the project ID. Stacks might be under the Deleted filter view. Review any failure messages in the stack events and correct the issue listed as the cause of those failures.

Project creation: I see an error when I try to edit Amazon EC2 configuration when creating a project

Problem: When you edit the Amazon EC2 configuration options during project creation, you see an error message or greyed-out option, and cannot continue with project creation.

Possible fixes: The most common reasons for an error message are:

  • The VPC in the AWS CodeStar project template (either the default VPC, or the one used when the Amazon EC2 configuration was edited) has dedicated instance tenancy, and the instance type is not supported for dedicated instances. Either choose a different instance type or a different Amazon VPC.

  • Your AWS account has no Amazon VPCs. You might have deleted the default VPC, and not created any others. Open the Amazon VPC console at https://console.aws.amazon.com/vpc/, choose Your VPCs, and make sure that you have at least one VPC configured. If not, create one. For more information, see Amazon Virtual Private Cloud Overview in the Amazon VPC Getting Started Guide.

  • The Amazon VPC does not have any subnets. Choose a different VPC, or create a subnet for that VPC. For more information, see VPC and Subnet Basics.

Project deletion: An AWS CodeStar project was deleted, but resources still exist

Problem: An AWS CodeStar project was deleted, but resources created for that project still exist. By default, AWS CodeStar deletes project resources when the project is deleted. Some resources, such as Amazon S3 buckets, are retained even if the user selects the Delete associated resources along with AWS CodeStar project check box, as the buckets might contain data.

Possible fixes: Open the AWS CloudFormation console and find one or more of the AWS CloudFormation stacks used to create the project. The stack names will start with awscodestar-, followed by the project ID. The stacks might be under the Deleted filter view. Review the events associated with the stack to discover the resources created for the project. Open the console for each of those resources in the region where you created the AWS CodeStar project, and then manually delete the resources for that deleted project.

Project resources that might remain include:

If your project uses resources outside of AWS, for example a GitHub repository or issues in Atlassian JIRA, those resources are not deleted, even if the Delete associated AWS resources along with CodeStar project box is selected.

Team management failure: An IAM user could not be added to a team in an AWS CodeStar project

Problem: When you try to add a user to a project, you see an error message saying that the addition failed.

Possible fixes: The most common reason for this error is that the IAM user has reached the limit of managed policies that can be applied to a user in IAM. You might also receive this error if you are not a member of the Owner role in the AWS CodeStar project where you tried to add the user, or if the IAM user does not exist or was deleted.

Make sure you are signed in as an IAM user who is an owner in that AWS CodeStar project. For more information, see Add Team Members to an AWS CodeStar Project .

To troubleshoot other issues, open the IAM console, choose the user you tried to add, and check how many managed policies are applied to that IAM user.

For more information, see Limitations on IAM Entities and Objects. For limits that can be changed, see AWS Service Limits.

Service role issue: The service role could not be created

Problem: When you try to create a project in AWS CodeStar, you see a message prompting you to create the service role. When you choose the option to create it, you see an error.

Possible fixes: The most common reason for this error is that you are logged into AWS with an account that does not have sufficient permissions to create the service role. To create the AWS CodeStar service role (aws-codestar-service-role), you must be logged in as an administrative user or with a root account. Log out of the console, and log back in with an IAM user that has the AdminstratorAccess managed policy applied.

Service role issue: The service role is not valid or missing

Problem: When you open the AWS CodeStar console, you see a message indicating the AWS CodeStar service role is missing or not valid.

Possible fixes: The most common reason for this error is that an administrative user edited or deleted the service role (aws-codestar-service-role). If the service role was deleted, you will be prompted to create it. You must be logged in as an administrative user or with a root account to create the role. If the role was edited, it is no longer valid. Log in to the IAM console as an administrative user, find the service role in the list of roles, and delete it. Switch to the AWS CodeStar console and follow the on-screen instructions to create the service role.

Project role issue: A project role is not valid or missing

Problem: When you try to add a user to a project, you see an error message saying that the addition failed because the policy for a project role is either missing or not valid.

Possible fixes: The most common reason for this error is that one or more project policies was edited in or deleted from IAM. Project policies are unique to AWS CodeStar projects, and cannot be recreated. The project cannot be used. Create a new project in AWS CodeStar, and migrate data to the new project. Clone project code from the unusable project's repository, and push that code to the new project's repository. Copy team wiki information from the old project to the new project. Add users to the new project. When you are sure you have migrated all data and settings, delete the unusable project.

Project extensions: Can't connect to JIRA

Problem: When you use the Atlassian JIRA extension to try to connect an AWS CodeStar project to a JIRA instance, the following message displays: "The URL is not a valid JIRA URL. Verify that the URL is correct."

Possible fixes:

  • Make sure the JIRA URL is correct, and then try connecting again.

  • Your self-hosted JIRA instance may not be accessible from the public Internet. Contact your network administrator to make sure your JIRA instance can be accessed from the public Internet, and then try connecting again.

GitHub: Can't access a repository's commit history, issues, or code

Problem: In the dashboard for a project that stores its code in GitHub, the Commit history and GitHub Issues tiles display a connection error, or choosing Open in GitHub or Create issue in these tiles displays an error.

Possible causes:

  • The AWS CodeStar project may no longer have access to the GitHub repository.

  • The repository may have been deleted or renamed in GitHub.