No permissions are required.
CodeCommit booster only requires codecommit:GitPush
and codecommit:GitPull
. You have to set these two allowed actions in the policy attached to your IAM role. (see Policies and permissions in IAM)
No. You have to create your repositories and branches directly in CodeCommit.
CodeCommit Booster will create a default branch for your empty repository. Other than that, if the branch doesn't exist, you will have the error "Remote origin did not advertise Ref for branch..." when pushing.
Check your IAM role configuration by clicking on Try to connect in the booster.
Make sure the target repository and branch exist and the booster is synchronized with them.
Make sure the pushing elements differ from the last commit of the target branch.
You may encounter a reference error "Remote origin did not advertise Ref for branch..." when the booster is out of synchronization with your repository. You can delete the booster and create a new one in this case.
All the members of the Transformation Center project.
Within the proposed configuration (based on the unique ExternalID context key), only Blu Insights can access your repository (See AWS External ID).
We use UUID-4 to generate the External ID.
With CodeCommit booster, you only need to create it once in your project, and leverage it afterwards to push your outputs. This will release users from manual download, unzip, import, etc. and add efficiency in the whole process.
For now, only AWS CodeCommit is supported.
You can download your outputs.