AWS CodeCommit - fatal: repository 'https://git-codecommit.us-east-1..' not found
I have an AWS account. I created a repository in us-east-1 region. When I try to access it from my Mac's terminal I get an error
fatal: repository 'https://git-codecommit.us-east-1.amazonaws.com/v1/repos/demo/' not found. I was able to access this repository using SourceTree GIT client.
I create another repository in California region and I was able to access that repository from the terminal itself.
Why my Mac's terminal can't find repositories in a particular AWS region?
I followed the link that both VonC and Uzair mentioned and I was able to get to the CLI git command to work after just entering:
git config --global credential.UseHttpPath true
Thanks VonC. PS: Make sure you have a current version of git installed. CodeCommit supports Git versions 1.7.9 and later.
I am prompted for a user name when I connect to a CodeCommit , When you connect to a CodeCommit repository for the first time, you typically clone its contents to your local machine. You can also add files to and edit files in a Git error: Git cannot find the CodeCommit repository or does not have permission to access the repository Problem: A trailing slash in the connection string can cause connection attempts to fail. Possible fixes: Make sure that you have provided the correct name and connection string for the repository, and that there are no trailing slashes.
If you are using AWS profiles, then adding credential helper without profile, will use the default profile of your AWS CLI setup. To make sure you are using the same profile/AWS account where your CodeCommit repository is located, you need to specify profile in
credential-helper use like this:
git config --global credential.helper '!aws --profile HERE_YOUR_CLI_PROFILE_NAME codecommit credential-helper $@'
Connect to an AWS CodeCommit repository, I am able to see the repo through AWS Management console when the user logs in. But when I tried to issue the command git clone https://git- You must have a location on your local machine to store a local copy of the CodeCommit repository you connect to. (This local copy of the CodeCommit repository is known as a local repo.) You then switch to and run Git commands from that location.
Check if SourceTree has a Git config different from your Git command line: this answer points out to setting:
[credential] helper = /usr/local/bin/aws codecommit credential-helper $@ UseHttpPath = true
Ie: The credential helper for AWS might not have been set for that particular repository in command line, while the Git used by SourceTree (which can be an embedded one) would be correctly set.
AWS CodeCommit: Fatal Error 403, I followed the link that both VonC and Uzair mentioned and I was able to get to the CLI git command to work after just entering: git config To create a repository, see Create an AWS CodeCommit Repository or follow the steps in the Getting Started with Git and CodeCommit tutorial. At the terminal or command prompt, clone the repository with the git clone command, and providing the clone URL you copied in the previous step.
I agree with first trying out VonC's suggestion above. Here's the link for setting up the credential helper for further reference:
AWS CodeCommit - fatal: repository 'https://git , because AWS CodeCommit uses the same url per region for all git repositories, if you are using fatal: repository 'https://git-codecommit. To create a repository, see Create an AWS CodeCommit Repository or follow the steps in the Getting Started with Git and CodeCommit tutorial. Open a command prompt run the git clone command with the HTTPS URL you copied.
Watch out: this error can be returned even if the repository is found, but the credentials provided are not correct.
In my case, since i have 2 aws accounts, i was using profile A to access account of profile B, and this gave me this error.
AWS CodeCommit Multiple Accounts, Facing Problem with Cloning the reepository in AWS Code Commit !!! Hi Thomas 2) command to clone the git repository git clone fatal: unable to access For more information about HTTPS, SSH, Git, git-remote-codecommit, and remote repositories, see Setting Up , Connecting to AWS CodeCommit Repositories with Rotating Credentials, or consult your Git documentation.
Facing Problem with Cloning the reepository in AWS Code Commit , fatal: unable to access 'https://git-codecommit.us-east-1.amazonaws.com/v1/ Ensure when you open your repo in AWS it has the region set the same as in AWS CodeCommit is a fully-managed source control service that hosts secure Git-based repositories. It makes it easy for teams to collaborate on code in a secure and highly scalable ecosystem. CodeCommit eliminates the need to operate your own source control system or worry about scaling its infrastructure.
Create a Pull Request - AWS CodeCommit, set up each local CodeCommit repository clone to use a specific cross-account IAM role with git clone --config and aws codecommit To replicate your repository, you’ll first need to set up a repository in AWS CodeCommit to use as your backup/replica repository. After replicating the contents in your source repository to the backup repository, we’ll demonstrate how you can set up a scheduled job to periodically sync up your source repository with the backup/replica.
Setup Steps for HTTPS Connections to AWS CodeCommit , Aws codecommit fatal repository not found. Troubleshooting Git Clients and AWS CodeCommit, I am able to see the repo through AWS Management console The local Git repository is configured to use the temporary credentials to assume an IAM role that has access to the AWS CodeCommit repository. Here again, STS provides temporary credentials, but they are valid for a maximum of one hour. When Git is calling AWS CodeCommit, the credentials retrieved in step 2 are used to authenticate the requests.