Step 4 on this page
For example, run the following command to create a default AWS CLI profile that you use to access AWS resources in AccountA in US East (Ohio) (us-east-2):
The bold section above should be AccountB

When using double quotes on command git config --global credential.helper "!aws codecommit credential-helper --profile MyCrossAccountAccessProfile $@" bash will expand [1] !aws to the last command ran starting with "aws". Replacing it with single quotes fixes the command.

References:
[1] Bash history expansion - https://www.gnu.org/software/bash/manual/html_node/History-Interaction.html#History-Interaction

Please explain the seeming discrepancy relating to branch permissions using git:

Git is restricted by policy
https://github.com/awsdocs/aws-codecommit-user-guide/blob/master/doc_source/how-to-conditional-branch.md

By default, any CodeCommit repository user who has sufficient permissions to push code to the repository can contribute to any branch in that repository. This is true no matter how you add a branch to the repository: by using the console, the command line, or Git.
...
From the terminal or command line, create a commit on the branch where the restrictions apply, and then push that commit to the CodeCommit repository. You should see an error message. Commits and pushes made from other branches should work as usual.

Git not restricted by policy
https://github.com/awsdocs/aws-codecommit-user-guide/blob/master/doc_source/auth-and-access-control-permissions-reference.md#aa-branches

The following permissions allow or deny actions on branches in CodeCommit repositories. These permissions pertain only to actions performed in the CodeCommit console and with the CodeCommit API, and to commands performed using the AWS CLI. They do not pertain to similar actions that can be performed using the Git protocol.

Migrating from github to codecommit is successfully migrated codes and branches but not pull request.
Do we have any other way to migrate everything?

The "Possible fixes" within the troubleshooting guide for Access Error User is not authorized for the KMS default master key for CodeCommit 'alias/aws/codecommit' in your account no longer seems to be valid for the current UI. There's no "Encryption Keys" reference within the IAM console.

Following the link at the end of the Possible fixes is enough to guide the user in the right direction for fixing the issue.

Hi guys,

Is it possible to get a simple raw (i.e. yaml file) from an ec2 instance via curl?

I followed the guide but still have an issue, the connection reset after "SSH2_MSG_KEXINIT sent" without any reason
Spend two days on this so..
Any help would be appreciated ?!

here is a screenshot of the problem

We currently have a number of troubleshooting topics to help users. You can find a list of them here. If you have ideas about any troubleshooting guidance that is missing, could be improved/expanded upon, or have some tips and tricks when using CodeCommit that you'd like to share, we'd love to hear from you.

Please submit a pull request following the guidelines here: https://github.com/awsdocs/aws-codecommit-user-guide/blob/master/CONTRIBUTING.md

Thank you for helping improve the documentation!

https://docs.aws.amazon.com/codecommit/latest/userguide/how-to-notify-lambda-cc.html#how-to-notify-lambda-create-function-perm

current:
aws lambda add-permission - -cli-input-json file://AllowAccessfromMyDemoRepo.json

There is an extra space between the dashes.
"- -cli-input-json" should be "--cli-input-json"

I have a account integrated with the MFA,I am unable to clone the repo even though I add the public key to the my user id.Can you please help out me with this issue and I have admin privileges for this account

Update the path for CLI v2.

[credential] helper = !"\C:\\Program Files\\Amazon\\AWSCLI\\bin\\aws.cmd\" codecommit credential-helper $@ UseHttpPath = true

The current steps for setting up the AWS CLI credential helper here involve setting this value for all hosts, when this is not necessary. Furthermore, it is possible to reset the credential helper list by configuring the option to the empty string. This avoids issues for users also using other credential helpers such as osxkeychain or Git Credential Manager, that cannot access any repository after the temporary credentials expire. I would recommend the following setup steps:

git config --global credential."https://git-codecommit.*.amazonaws.com".helper ''
git config --global --add credential."https://git-codecommit.*.amazonaws.com".helper '!aws codecommit credential-helper $@'
git config --global credential."https://git-codecommit.*.amazonaws.com".UseHttpPath true

This will apply the configuration only for CodeCommit hosts, while also bypassing any other credential helpers. With the setup above, there is no need for any of the workarounds described in the documentation. After running the commands, the .gitconfig file should contain this section:

[credential "https://git-codecommit.*.amazonaws.com"]
	helper =
	helper = !aws codecommit credential-helper $@
	UseHttpPath = true

For users using git-remote-codecommit, the following configuration could be applicable:

git config --global credential."https://git-codecommit.*.amazonaws.com".helper ''

This avoids the issue that Windows users have mentioned in this issue as well as here, which results in these messages being displayed:

fatal: Failed to write item to store. [0x6c6]
fatal: The array bounds are invalid

Additionally, the temporary credentials will not be stored in the Keychain anymore for macOS users. In all of the commands above, Windows users should replace single quotes with double quotes.

The AWS CodeCommit User Guide has a number of policy examples included that are intended to help solve common problems or requests. For example:

• Limit Pushes and Merges to Branches
• Customer Managed Policy Examples

However, we'd love to add more, and more real-world-scenario-based examples to the guide. If you have ideas, examples, or suggestions to share, please do!

Please submit a pull request following the guidance here: https://github.com/awsdocs/aws-codecommit-user-guide/blob/master/CONTRIBUTING.md

Thanks for helping improve the examples!

We have guidance for setting up cross account access to AWS CodeCommit repositories. You can find the topics here. However, this content seems to be getting mixed reviews; some users find it really helpful, while others have trouble with it. We'd love to get your suggestions on how this could be improved.

Please submit a pull request according to the instructions here:https://github.com/awsdocs/aws-codecommit-user-guide/blob/master/CONTRIBUTING.md

Thanks for helping improve the docs!