Leverage Matrices for DRY Workflow Management

Architecture Reference : https://aws.amazon.com/vi/blogs/networking-and-content-delivery/deployment-models-for-aws-network-firewall/ Deploy Multi-VPC Reference : https://github.com/tnx-journey-to-cloud/terraform-aws-vpc We create a VPC module with Terraform to reuse and call it whenever we deploy a VPC in Multi-VPC environment such as Spoke, Ingress, Egress, … The source code available here: https://github.com/tnx-journey-to-cloud/terraform-aws-networkfirewall Our Cloud Journey’s members: https://github.com/hungran https://github.com/hiimtung https://github.com/kerashanog https://github.com/haicasgox https://github.com/lacoski https://github.com/HieuChayA4

Open source tools integrated with Terraform and GitHub Atlantis Atlantis is an application for automating Terraform via pull requests. It is deployed as a standalone application into your infrastructure. Atlantis listens for GitHub, GitLab or Bitbucket webhooks about Terraform pull requests. It then runs terraform plan and comments with the output back on the pull request. When you want to apply, comment atlantis apply on the pull request and Atlantis will run terraform apply and comment back with the output.

Multi-account AWS environment Each AWS account is a resource container for AWS Cloud services, an explicit security boundary, a container for cost tracking and billing and a mechanism to enforce service quotas and API threshods. An account acts as an identity and access management isolation boundary. First, we begin by building resources in a single AWS account that represents a management boundary which segments permissions, costs, and services. However, as the customer’s organization grows, greater segmentation of services becomes necessary to monitor costs, control access, and provide easier environmental management.