This module will allow you to publish concourse on your own AWS infrastructure. Why another module? We needed something a little more prescriptive than the current module that's available (don't get us wrong, it's great) so we built this. It's a very straightforward deploy and will work in enterprise or startup situations. Proper networking design is left up to the reader.

Currently we support the following features:

1. Docker based deployment. The module uses the most recent ECS AMI for deployment and runs concourse inside containers in those instances. No binary installs here.
2. Configurable number of workers and webs along with volume sizes and instance types. Everything has a sane default but customize to your liking.
3. Requires AWS classic load balancing complete with SSL termination. We may upgrade this in the future, but it works fine. Why bother?
4. Configurable authentication scheme (you need to know what you're doing though). Pass your secrets through the appropriate configuration variable and we'll pass that to the docker container.
5. Configurable PostGres installation because you don't need RDS for this. Unless you're doing massive amounts of builds you'll never run out of storage with the added bonus of a cheaper DB instance.
6. Inherits the current AWS region from parent modules.

See the examples directory for more information on how to deploy this to your account. You shouldn't need to this very much. Check variables.tf for information on all the bits you'll need and also see the main.tf in the root directory for an example of how to call the module.

First, you need a decent understanding of how to use Terraform. Hit the docs for that. Then, you should understand the concourse architecture. Once you're good import this module and pass the appropriate variables. Then, plan your run and deploy.

Not much can go wrong here, but file issues as needed. Be sure to read our issues guide before hand. PRs are welcome.

This is a fairly minimal install that should plug into any AWS architecture. We crafted the security groups such that only the appropriate traffic sources are able to hit specific targets. For example, the only boxes able to hit the PostGres and worker instances are the web boxes. You can see this by deploying the module and inspecting the SGs, or looking at the appropriate section of the main.tf.