Multi-Account deployment - MoM
Attandance:
- @Shawn Lim
- @amal.syahreza
- @agusprasetiyo
- @Frans
Notes:
Config Building block:
Example:
Service adjustment:
- Config
- dynamoDB idgen-seed (example)
- RPC client (for service in other product domain - other AWS account)
- rpcClient properties = secure: false
- service endpoint
- old : <service_name>.test.tvlk.cloud : 443
- new : <service_name>-vpce.ins.stg-tvlk.cloud : 80
- RPC client (internal ins communication)
- rpcClient properties = secure: true
- <service_name>.ins.stg-tvlk.cloud : 443
- S3
- RDS
- Memcached
- SQS
Deployment:
- Go to : ap-southeast-1/ins<xxx>/ins<xxx>-app
- modify : 01-locals.tf
- app_memory_java_opts
- asg_ami_id
- asg_*_capacity
- do “terraform plan”
- Create PR
- Run : “terraform apply” in ap-southeast-1/ins<xxx>/ins<xxx>-app
- Or you can skip this part if repository already implemented terraform CI/CD. Currently only dev and prod implemented it
- Merge PR
Action Item:
- Seed dummy data to insdata-postgres (@pieter @Shawn Lim)
- Create config for MultiAccount (@ins-backend-eng)
- Testing (@ins-backend-eng)