Introduce New Terraform Architecture Including the Terraform Modules and the Remote States.

1. Terraform
Architecture
David Hsu

2. What are we doing now?
ecs-creation
ecs-update

3. Why not ?
Use ecs-update makes ecs-creation meaningless

4. Then?
We will forget to update creation repo
Then Terraform repo will be not accurate with our infra

5. How to make Terraform
repo to be useful?
Using the same repo to create/update infra

6. But
Terraform creation still complicated

7. How to make it easy?
Terraform module and remote_state

8. How Terraform module
improve this ?
EC2 / ECS / Task_definition / ALB / Route53
Centralized Control

9. Example

10. terraform_remote_state
VPC / Subets / RTB / PeeringConnections
IN
Another Repo

11. Example

12. What else we need to notice
Avoid to use variables if unnecessary
Because it will make PR hard to review

13. What Force us to Update
Creation
Deployment will fail if you don’t update Creation repo

14. WHY
Don’t repeat the same things.
But we are always doing this.

15. Benefits
Let every engineer can modify Terraform scripts
Because it will become easy once we modularized it.
It is DevOps culture.

16. Benefits
Less deployment command we need to setup. in the
other word, we can reduce variables override and also
more readable.

17. Benefits
Modularized Terraform scripts will make PR easy to
review because less code we need to write and less
HCL function we need to understand.

18. The Most Important Thing
No more ecs-update repo Needed

19. Review
Use Creation repo on SemaphoreCI and
-target=[resource]
to avoid any changing which is unexpected

20. Review
DO NOT use
[ resource “aws_vpc”{} ] or
[ resource “aws_subnet” {} ] even
[ resource “aws_route_table” {} ]
on Creation repo
Please use [ terraform_remote_state ]

21. Review
Use more module resources as possible as you can

22. Review
Remember to follow our standard

23. NOW
Go to clone Shopline Terraform Module template !
git clone git@bitbucket.org:starlinglabs/ecs_modules_template.git