A Step-by-Step Guide to Automating CloudFormation Deployments Using GitHub

It always starts with “just one small change.” Then you’re deep in the AWS Console, re-uploading files, fixing permissions, and wondering how a five-minute update became a deployment marathon.

That’s the everyday friction of managing Infrastructure as Code when automation isn’t fully in place. Manual deployments slow teams down, increase the risk of drift between environments, and make it nearly impossible to execute quick iterations.

So what if your AWS stacks deployed automatically the moment you pushed code to GitHub?

That’s exactly what AWS CloudFormation’s new Git sync feature enables.

In this blog, we’ll explore how to connect your GitHub repository with CloudFormation to create a setup where every commit triggers a deployment, turning your IaC workflow into a smooth, automated pipeline.

Why Automate CloudFormation with GitHub?

If you’ve worked with CloudFormation before, you know the drill. You write a template, upload it manually, wait for deployment, and then fix errors that appear way too late in the process. It works, but it’s far from efficient.

That’s where Git sync changes everything.

Instead of manually pushing updates or juggling scripts, your CloudFormation stack can now stay perfectly aligned with your Git repository. Every time you commit a change, the stack updates automatically.

It’s the kind of integration DevOps teams have been waiting for. Your Git workflow remains the same: versioned, collaborative, and review-friendly. However, your infrastructure now moves in lockstep with your codebase.

Here’s what that really means in practice:

• Zero manual triggers. You don’t need to switch between Git and the AWS Console to deploy changes.
• Instant feedback. Each commit or pull request can trigger a deployment, allowing you to catch errors early.
• Consistent environments. Every stack version matches your repository version, keeping staging, QA, and production in sync.

And the best part is that Git sync isn’t limited to GitHub. You can connect GitHub Enterprise, GitLab, or Bitbucket just as easily.

What You’ll Need

Before setting up your first Git-connected deployment, make sure your environment is ready. The setup is simple, but a few essentials will save you time later.

• An AWS account with the right CloudFormation permissions to create and manage stacks.
• A GitHub account with access to Codespaces and Actions if you plan to test or automate workflows directly in GitHub.
• A few local tools installed on your system:
• Git for version control.
• AWS CLI for authentication and quick command-line actions.
• Python3 for installing and running cfn-lint, which helps validate your CloudFormation templates before deployment.

Once these are in place, you’re ready to connect GitHub to CloudFormation and start building a fully automated IaC workflow.

Step 1: Set Up Your Git Repository

Start by creating a new repository on GitHub. You can keep it empty for now. Once created, clone it to your local workspace or open it directly in GitHub Codespaces if you prefer working in the cloud.

Before writing any templates, install CloudFormation Linter (cfn-lint). It’s a simple tool that checks for errors and best practices in your CloudFormation files.

pip3 install cfn-lint

After installation, confirm it’s working correctly:

cfn-lint --version

Running lint checks early might seem like an extra step, but it saves hours later. It helps you spot missing properties, wrong syntax, or unsupported resources before you ever deploy anything to AWS.

Step 2: Create Your CloudFormation Template

Next, it’s time to create your first CloudFormation template. In your repository, add a new file named s3.yaml. This template will create a simple S3 bucket that we’ll later deploy automatically through Git sync.

Paste the following code into your file:

AWSTemplateFormatVersion: "2010-09-09" Description: Simple S3 bucket created via CloudFormation Git Sync Resources: MyS3Bucket: Type: AWS::S3::Bucket Properties: BucketName: cf-s3-git-bucket-v1

Once you’ve saved the file, validate it with cfn-lint to make sure there are no syntax or logic errors.

cfn-lint -t s3.yaml

If the terminal returns no errors, congratulations, your template is valid and ready to deploy.

Even a simple validation step like this can prevent long debugging sessions later. It’s your first safety check before pushing code to GitHub.

Step 3: Add the Deployment Configuration File

Now that your template is ready, CloudFormation needs to know where to find it. That’s where the deployment configuration file comes in. It tells CloudFormation which template to deploy and how to handle parameters, tags, or future stack settings.

In your repository’s root folder, create a new file named deployment-file.yaml and add the following line:

template-file-path: ./s3.yaml

Your project directory should now look like this:

/my-repo ├── s3.yaml └── deployment-file.yaml

This configuration file acts as the blueprint for your Git sync setup. Currently, it’s minimal because we’re working with a basic template. As your stacks grow, you can extend it to include parameters, tags, or even multiple templates across environments.

Step 4: Configure AWS CloudFormation Git Sync

With your files ready, it’s time to connect GitHub with CloudFormation. Follow these steps:

1. Open the AWS Management Console and navigate to CloudFormation.
2. Click "Create Stack" and select "With new resources (standard)".
3. In the Template source section, choose Sync from Git repository.
4. Select GitHub as your connection type and sign in if prompted.
5. Pick your repository and branch, then specify deployment-file.yaml as the configuration file.
6. Under Permissions, choose Create new IAM role to let CloudFormation securely deploy resources.
7. Review the settings and create the stack.

Once the configuration is complete, CloudFormation will begin monitoring your GitHub repository for any changes. Each new commit will automatically trigger an update to your stack, keeping your infrastructure perfectly in sync with your code.

Step 5: Verify Sync and Observe Auto-Deployment

Now it’s time to see your automated setup in action.

Follow these steps to test the sync:

1. Open your s3.yaml file and make a small change. For example, update the bucket name:
2. BucketName: cf-s3-git-bucket-v2
3. Save the file and push the changes to your GitHub repository:

git add . git commit -m "Updated bucket name to v2" git push

1. Wait a few moments while CloudFormation detects the update and automatically redeploys your stack.
2. Go to the Git Sync tab in the CloudFormation Console to monitor progress. You can view sync status, deployment history, and detailed logs for each event.

If everything is set up correctly, you’ll see the new bucket created automatically, no manual steps required. Your Git commits are now directly powering your AWS deployments.

Results

After the deployment finishes, your new bucket cf-s3-git-bucket-v2 appears in the AWS S3 console. No manual actions are required because the entire process is triggered by your Git commit.

CloudFormation now automatically tracks your repository, detects any changes, and redeploys the stack whenever needed. This means your infrastructure always matches your latest code without additional scripts or human involvement.

You can monitor these deployments in the Git Sync tab of the CloudFormation Console. It displays sync status, deployment history, logs, and rollback options, providing you with full visibility into what has changed and when.

This setup brings a few key advantages:

• Faster iterations. Deployments happen automatically after each commit.
• Reduced human error. No one needs to manually trigger or manage stack updates.
• Versioned environments. Every stack reflects the exact state of your Git repository.

The result is an infrastructure workflow that stays consistent, transparent, and continuous. Your Git repo becomes the single source of truth, and CloudFormation handles the rest.

Conclusion

Sometimes the best improvements are the quiet ones. Git sync doesn’t add more tools; it simply makes CloudFormation feel lighter and smarter.

No console hopping, no manual uploads, no waiting for stacks to finish updating. Just clean commits that go live in minutes.

What makes this setup powerful is how natural it feels. Developers stay in GitHub while CloudFormation handles deployments, keeping everything versioned, predictable, and easy to roll back when needed.

That’s the kind of automation that gives teams back their time and peace of mind.

At Coditas, we help teams build setups like this every day, creating solutions that are reliable, secure, and built for scale on AWS.

If you’re ready to move from manual workflows to automated infrastructure, we’ll help you get there faster and smarter.

References:

https://dev.to/aws-builders/automate-cloudformation-deployments-from-github-63p