AWS Proton introduces Git management of service configurations

AWS Proton now allows customers to sync their service specifications from a Git repository. Customers use Proton as a self-service template system to define and update infrastructure. Now, customers can sync Proton service configurations like compute size and target deployment environment directly from GitHub or Bitbucket. Proton is a managed service for customers to increase the pace of innovation in their organization by defining, vending, and maintaining infrastructure templates for self-service deployments. With Proton, customers can standardize services to help meet security, cost, and compliance goals. Git management of service configurations enables customers to test changes on a staging branch and push changes to production. Customers can get started with this feature by creating a service-spec, an infrastructure definition file. This file contains the parameter variables that developers want to input when using a Proton template to create infrastructure for their service, such as compute size configurations and the target deployment environment (e.g., test1). If using the console, Proton can create a Pull Request with these files to your chosen repository. Proton will automatically sync the spec file and update the Proton service after every commit, so developers never have to leave their existing Git workstream to provision infrastrucure. For further customization, teams create a Proton-ops file that defines different configurations per instances of their service. For example, to test changes before pushing them to production, teams configure one instance to sync from a staging branch and another from a production branch. To learn more, check out our documentation [here](https://docs.aws.amazon.com/proton/latest/userguide/ag-service-sync-configs.html) and our launch blog [here](https://aws.amazon.com/blogs/containers/announcing-git-based-service-deployments-with-service-sync-for-aws-proton/).