Best practice for automating cloudformation stack in github actions when repository holds cloud formation templates of multiple services

Viewed 13

We have a repository in GitLab which stores the cloud formation templates of IAM roles, permissions, security groups and Route 53 of multiple micro-services. Previously we used a separate repositories to handle the deployment from the repo above using Circle CI and Python scripts, to write ONLY the modified artifacts to s3 and then trigger Cloud formation stack to do the deployment after confirmation. for a visual representation, it looks something like this.

Infra CICD Eg

I am currently migrating this to GitHub and moving away from Circle CI, and would like to update the CI/CD here to follow best practices and to use GitHub Actions to do the deployment of the infra. What would be the best means to do so?

0 Answers
Related