You can also generate static credentials for CodeCommit ( ) and put them on your EC2 instance in something like a. You will also need to figure out a way to distribute your public and private key pair to the EC2 instances that you are trying to scale up, this can be quite troublesome. You do, however, need to upload a public key to IAM (instructions here: ) I am sorry if that was not clear in the documentation. In Option 2, you do not need to use the credential helper at all. The CLI needs to be installed for the git config lines you've posted to work because its going to call "aws codecommit credential-helper" to get a temporary username and password based on the instance role credentials. Though its unclear from the output whether the AWS CLI is installed. This is provided that you have set up EC2 instance roles correctly and that your AWS CLI is able to get the EC2 instance role credentials from EC2 metadata to call AWS APIs. Git config credential.helper '!aws codecommit credential-helper config credential.UseHttpPath true you can switch the order of the lines to: Though the option doesn't need to be global, e.g. When you are setting the global git config, it will go into the home directory's.
In Option 1, it looks like the home directory wasn't created yet. Please make sure you have the correct access rightsĬan someone please hep me understand where I am going wrong? Git remote set-url origin ssh:///v1/repos/reponameįatal: Could not read from remote repository. Tried this option as well with SSH (although haven't tried any further fixes for this) #!/bin/bash gitįatal: could not read Username for '': No such device or address Git config -global credential.helper '!aws codecommit credential-helper config -global credential.UseHttpPath trueįatal: Not a git repository (or any of the parent directories). However on launch, the script always throws error and does not pull changes (I intentionally kept a file in repo to test) To achieve this, I placed below code in User data (cloud-init) script and selected a IAM role that has full permissions over all EC2 and codecommit as well as IAM:Passrole permission. I want to base/modify my launch config AMI every month or so to ensure the AMI itself has recent updated code and so newly launched instances (thru auto scaling) can just pull latest changes from codecommit repo on launch - resulting in reduced launch time. I have created an AMI for one of my running Ubuntu instance in AWS and created a launch configuration using this AMI along with an auto scaling group. There seem to be lot of discussion around this topic however nothing precisely for my situation and hasn't resolved it for me so far.
0 kommentar(er)
