AWS CodeCommit is a git host service by Amazon Web Services to store and manage source code, related files and private Git repositories in the cloud.
The permissions detailed in the connect/autoconnect wizard are necessary for specific features to work.
We recommend that the following AWS IAM policies are configured beforehand based on what features that will be used:
|show commits, process smart commits, show branches||
|show pull requests||
|create pull request||
|configure webhooks automatically||
CodeCommit doesn't have webhooks but it has SNS triggers requiring a subscription confirmation.
For more information on Amazon SNS, see Amazon SNS: Getting Started.
This process requires an AWS account with existing CodeCommit repositories.
To connect your repository to Jira thru the Git Integration for Jira Server add-on, open the Connect to Git Repository wizard:
ON, will require users to provide PAT specific for branch and pull requests creation/deletion (via the developer panel on the Jira issue page). For more information on this feature, see Integration Settings: Require User PAT .
The Git Integration for Jira Server add-on supports tracked folders for AWS CodeCommit git repositories. The connected git host is scanned for existing repository folders. The found repositories can then be added to the Git Repositories configuration.
There are two ways to configure the git repository connection using tracked folders with Git for Jira Server:
If the connected git host has newly added repositories, the Git add-on will automatically add them to the git repositories configuration on the next reindex. For the deleted git repositories, these will be removed from the Git add-on repositories configuration on the next reindex.
Connect a single AWS CodeCommit repository manually to Jira via HTTP/HTTPS connection.
http://git-codecommit.us-east-1.amazonaws.com/v1/repos/test-repoand paste it on the Connect to Git Repository screen.
Connect a single AWS CodeCommit repository manually to Jira via SSH connection.
SSH connections are handled automatically if the PUBLIC KEY was added in the AWS IAM console and the associated PRIVATE KEY was added/uploaded on the Jira side (Git Integration for Jira > SSH Keys > Add SSH Key).
If authentication issues are encountered during connecting an AWS repository to Jira, modify the original URL by inserting the SSH Key ID as the username. The SSH Key ID is an alphanumeric sequence provided by AWS IAM when importing a PUBLIC KEY for a particular user account in IAM.
For example, the original URL is:
If the SSH Key ID 1a2b3c4d5e is applied to the original SSH URL, the resulting URL would be:
The modified URL can now be used as a valid repository URL via Git Integration for Jira > Connect to Git Repository.
Perform a commit to the newly-created branch to be ready for merge.
The pull request feature works the same as merge request.
To create a pull request and pull it to the main source (master):
If the Require User PAT option is enabled and a user PAT isn't configured yet for the selected repository via Repository Browser, the dialog below is displayed instead:
If an invalid PAT was configured for the selected repository, the pull request creation process will fail.
The pull request is listed on the developer panel of the Jira issue page.
The pull request is also ready for approval by the reviewers in your AWS CodeCommit web portal.