AWS CloudFormation introduces Git management of stacks
Share
Services
AWS CloudFormation now supports Git sync, enabling customers to synchronize their stacks from a CloudFormation template stored in a remote Git repository. A CloudFormation template describes your desired resources and their dependencies so you can launch and configure them together as a stack.
This feature enables developers to speed up the development cycle by integrating CloudFormation deployments directly into their Git workflow and reducing time lost to context switching. You can enable CloudFormation Git sync through the AWS Console, CLI, and SDKs. Dynamic values such as stack parameters and tags can now be specified via a YAML deployment file, enabling customers to track historical changes to these values in a Git file stored in your remote repository. After setup, AWS will automatically sync the deployment file and CloudFormation template, updating your stack after every commit. To test CloudFormation changes before pushing them to production, teams can configure one stack to sync from a Git staging branch and another from a production branch. Git sync works with GitHub, GitHub enterprise, GitLab, and BitBucket.
This feature is available in the following regions: US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Paris), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Milan), Europe (Stockholm), and South America (São Paulo).
You can get started by checking out our documentation [here](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/git-sync.html) and our launch blog [here](https://aws.amazon.com/blogs/devops/automate-safe-aws-cloudformation-deployments-from-github/).
What else is happening at Amazon Web Services?
Read update
Services
Share
Read update
Services
Share
Amazon Managed Service for Prometheus now supports configuring a minimum firing period for alerts
October 16th, 2024
Services
Share