|Brian Salcedo e28cacea42||1 year ago|
|tpm||3 years ago|
|.gitignore||3 years ago|
|Dockerfile||3 years ago|
|Makefile||3 years ago|
|README.md||1 year ago|
|build.sh||3 years ago|
|config.tf.dist||3 years ago|
|main.tf||3 years ago|
|networking.tf||3 years ago|
|security.tf||3 years ago|
Deploy Team Password Manager on AWS EC2 via Terraform.
Once the Terraform Apply is complete, A CoreOS instance runs a systemd unit (included in the user-data created by build.sh) which builds and runs a container that, in turn, brings up the Team Password Manager stack via docker-compose. The two build-stage containers then vanish - along with their files - and the end result is three running containers:
The final three containers are configured to survive unexpected shutdowns or reboots. Application data persistance and ACME storage is provided through the creation of two docker volumes.
The AWS Security Group resource is in security.tf, which defaults to allowing only HTTP & HTTPS. No SSH keys are associated with the instance - thus it is inaccessible (except for the app).