AWS Code Commit

AWS Code commit is a service that allows us to manage a git repository in the cloud that is providing the same service as GIT Hub or bit bucket. Since it exists inside your AWS account, it has more capabilities to integrate with your AWS resource which is one advantage you will get selecting AWS code commit. Other than that, it is a managed service so you will not have to work on taking backups, managing the service so literally, your operational burden to manage a version controller server will become zero with AWS code commit.

All you have to do is go to the AWS Code commit console and click create a repository.

Once the repo is created we will get two options to connect with the repo. You can pick SSH or HTTPS as the mode of connecting with the repo but if you are the root user of the account, using any of those under root is not recommended, so create a separate IAM user with relevant permission.

Under the security credential of your new IAM user, you will see options to generate an SSH credential to access the AWS Code commit or you can generate the HTTPS Git credential to access via HTTPS.

Now we are all set up to use the repository with the IAM user, so it is time to take a clone of the repository.

You can take a local copy of your repository with the clone URL, since I have created a dedicated IAM user with HTTPS credentials I can select the HTTPS link for the clone.

How the AWS code commit looks like after my first commit.

Now I have a fully functioning Git repository so I can try out all the capabilities offered by Git with AWS code commit such as pull requests, code merging, code tagging, branching, etc, etc.

As per the GIT Flows, we will have two major branches, master which is the equivalent code for what we running on the production, and development which contains upcoming changes to the production. The Master branch is the one we should protect from unnecessary involvements, usually, limited people have access to commit or merge a pull request to the master branch but most of the developers work on the development branch.

So can create two IAM groups with the required permissions to access my code commit repository and assign users to the correct group.

Sample IAM policy to impose AWS CodeCommit restrictions.

Getting notified on events occured in the code repository and triggering an action on an event is a common usecase when we deal with a source code.

First we need to define a notificaition rule, there we can define on which repository event we should notify.We can select specific or all events based on the use case.

The next step is selecting an appropriate notifcation target.We have two options here, we can pick an SNS topic which mean you will get full spectrum of notifcation capabilities offered by the SNS or you can select AWS Chatbot to notify to yout IM(ex, Slack ).

Triggering a Lambda function for reposritory event is a few clicks configuration.

If you interested in reading more on aws code commit please have a look on below.

Related posts:

Have you found tips or tricks that make living with diabetes less challenging, easier to manage or more predictable? Share your ideas with us to help make others lives with diabetes a little easier.

Ten years ago in Valencia myself and my good friend from college approach the bullfighting arena. The parallels between this age old pregame scene and our division 1 NCAA football experiences are…

Storytelling as an art. From history to impact of storytelling in business, cultures, behaviors, we explore the importance of storytelling in everyday life.