Atlassian Bitbucket to Aws Codecommit Using Bitbucket Pipelines​

Introduction​

Short Description on Steps We Will Be Following​

1. Creating a new and empty CodeCommit Repository where we are going to sync the data of the bitbucket repository.
2. Creation of IAM Group which will have the access permissions which will allow us to commit the changes in the Codecommit repository.
3. Creation of IAM User through which we will commit the changes from the bitbucket to the CodeCommit.
4. Creation of SSH Keys and adding in the Security Credentials of the user.
5. Configure Bitbucket Pipelines which will help us to create the replication from the bitbucket repository to the CodeCommit and which will be helpful to maintain the sync on timely basis.

Procedure

1. Creation of CodeCommit RepositoryFirst we will create an empty repository by selecting the region where we want the CodeCommit repository to be .Following will be the steps to create a new repository.
2. We will create an empty repository to commit the changes from Bitbucket.
3. Open up AWS CodeCommit and select your region.
4. Once you’ve created a repository, select the repository, click the “Connect” button, and choose the SSH option which we’ll be using later on, this is where you’ll find your connection information, and some instructions that you can refer back to later.

Creation of Iam Group​

• Create a new IAM CodeCommit-Contributor.
• Assign the AWSCodeCommitPowerUser policy to this group.

Creation of Iam User

• Create a new IAM user with a login of Bitbucket-User.
• Assign the CodeCommit-Contributor group to it.
• After creation we will add the SSH public key to the user which we will do below.

Creation of SSH Keys and adding in the Security Credentials of the User

• Open your IAM Bitbucket-User, and under “Security credentials”, click Upload SSH Key under “SSH keys for AWS CodeCommit”, and paste in your public key.
• Once your public key is created, there will be an SSH key ID associated with it.
• This will be used as your CodeCommit username when accessing repositories.

Set Up GIT and Validate Your Connection

• Create your ~/.ssh/config, and associate your IAM user’s SSH key ID and new private key with the CodeCommit hosts.Write the below details in the config file which we will create.
  Host git-codecommit.*.amazonaws.com 
  User Your-IAM-SSH-Key-ID-Here [which is created in Security credentials when we uploaded the SSH key in iam user] IdentityFile ~/.ssh/codecommit_rsa
• Now we will initialize the connection as below
  ssh git-codecommit.us-east-1.amazonaws.com 
  The authenticity of host ‘git-codecommit.us-east-1.amazonaws.com (72.21.203.185)’ can’t be  established. 
  RSA key fingerprint is SHA256:XXX/XXXXXX. 
  Are you sure you want to continue connecting (yes/no)? yes 
  Warning: Permanently added ‘git-codecommit.us-east-1.amazonaws.com,72.21.203.185’ (RSA) to the list of known hosts.
• We should get the below response : You have successfully authenticated over SSH. You can use Git to interact with AWS CodeCommit. Interactive shells are not supported. Connection to git-codecommit.us-east-1.amazonaws.comclosed by remote host.

Configure Bitbucket Pipelines

• In order to use Bitbucket Pipelines, it needs to be enabled for the repository first. Under your repository settings, choose Pipelines and enable pipelines in bitbucket.
• Now Pipelines is enabled, and before configuring that bitbucket-pipelines.yml file, lets initialize some Pipelines environment variables. 
• Under your repository settings, choose Repository Variables under Pipelines. We’re going to create 5 environment variables as below.

• CodeCommitConfig: The base64 encoded version of the SSH config we added to our ~/.ssh/config earlier that specifies the Host, User and IdentityFile.
• We can create the base64 encoding below

• CodeCommitHost: The host and region of your CodeCommit instance
   
• CodeCommitKey: The base64 encoded version of your SSH private key that we generated (node that it’s hidden and encrypted in the above screenshot because Secured was selected, make sure you do this as well).We can create base4 encoding like

• CodeCommitRepo: The host, region and repository path of your repository.
• CodeCommitUser: The SSH key ID associated with the public key on your AWS IAM user.[This is the SSH keyID which we will get in the Security Credentials in the IAM]
• Lets create that bitbucket-pipelines.yml file, either add it using your favourite editor, or click “Configure bitbucket-pipelines.yml” and edit it directly on bitbucket.org.

• Creates temporary files for $CodeCommitKey and $CodeCommitConfig then decodes them into place.
• Adjusts the permissions on your primary key (some SSH clients require more secure privileges on this file)
• Initializes the SSH connection to the CodeCommit host. It’s worth noting here that this command will “appear to fail”, so we need to disable error checking (set +e) on this script and let it fail silently and then re-enable error checking (set -e). -o StrictHostKeyChecking=no will prevent the service from needing to manually accept the remote host.
• Add the CodeCommit repository as a remote and push the current ($BITBUCKET_BRANCH) branch

Notes

• We will require CodeCommit Repository as empty everytime

Benefits of Atlassian Bitbucket and Aws Codecommit in Your Business

How Complere Can Help?