-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Terraform docs/HA guide #3410
Conversation
Should be ready to check now. |
- 2 x m4.large Teleport **auth** instances in an ASG, behind an internal network load balancer, configured using DynamoDB for | ||
shared storage. [The desired size of the ASG is configured here](https://github.com/gravitational/teleport/blob/master/examples/aws/terraform/auth_asg.tf#L11) | ||
- 2 x m4.large Teleport **proxy** instances in an ASG, behind a public-facing load balancer - NLB for LetsEncrypt, ALB for ACM. [The desired size of the ASG is configured here](https://github.com/gravitational/teleport/blob/master/examples/aws/terraform/proxy_asg.tf#L12) | ||
- 1 x m4.large Teleport **node** instance in an ASG. [The desired size of the ASG is configured here](https://github.com/gravitational/teleport/blob/master/examples/aws/terraform/node_asg.tf#L10) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really need a node this large? As an example node. We should say this node isn't required, but is there as an example for how Teleport works.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we were basically trying to get something where it'd be good enough for pretty much anyone but the most hardcore users. m4.large is 10 cents an hour - I guess for 5 of those instances it adds up pretty quickly.
One thing I would like to do with Terraform is expose the instance types more readily as a variable which can be changed at runtime and make some recommendations for scale. It's just something that I haven't got around to testing yet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I pushed a few changes to your branch to speed up production cycle
Thanks @benarent. Incidentally this reminds me that we don't seem to have a page in the docs about how to use |
@@ -21,6 +21,7 @@ markdown_extensions: | |||
- footnotes | |||
- toc: | |||
marker: '[TOC]' | |||
toc_depth: 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love this, didn't realise we could do it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
^ Yeah, it' a new-ish feature... I've been a bit slow to adopt the new features after I updated the MkDocs image.
I would go ahead and merge this, I'll update a reference when I work on #3018 |
Work in progress