AWS DevOps Blog

Tag: CodeCommit

Continuous Delivery of Nested AWS CloudFormation Stacks Using AWS CodePipeline

In CodePipeline Update – Build Continuous Delivery Workflows for CloudFormation Stacks, Jeff Barr discusses infrastructure as code and how to use AWS CodePipeline for continuous delivery. In this blog post, I discuss the continuous delivery of nested CloudFormation stacks using AWS CodePipeline, with AWS CodeCommit as the source repository and AWS CodeBuild as a build […]

How to Create an Automated Database Continuous Integration and Release Management Workflow with Datical and AWS

Editors note: This blog post is out of date. For an up-to-date blog post on how to implement CI/CD for your database you can try this post “Deploy, track, and roll back RDS database code changes using open source tools Liquibase and Jenkins.”   Thank you to my colleague Erin McGill for reviewing and providing valuable feedback on this […]

Building a Secure Cross-Account Continuous Delivery Pipeline

Most organizations create multiple AWS accounts because they provide the highest level of resource and security isolation. In this blog post, I will discuss how to use cross account AWS Identity and Access Management (IAM) access to orchestrate continuous integration and continuous deployment. Do I need multiple accounts? If you answer “yes” to any of […]

Introducing Git Credentials: A Simple Way to Connect to AWS CodeCommit Repositories Using a Static User Name and Password

Today, AWS is introducing a simplified way to authenticate to your AWS CodeCommit repositories over HTTPS. With Git credentials, you can generate a static user name and password in the Identity and Access Management (IAM) console that you can use to access AWS CodeCommit repositories from the command line, Git CLI, or any Git tool […]

Integrating AWS CodeCommit with Jenkins

Today we have a guest post written by Emeka Igbokwe, a Solutions Architect at AWS. This post walks you through the steps to set up Jenkins and AWS CodeCommit to support 2 simple continuous integration (CI) scenarios. In the 1st scenario, you will make a change in your local Git repository, push the change to […]