mirror of
https://github.com/gravitational/teleport
synced 2024-10-21 01:34:01 +00:00
[docs] Added instructions for license.pem (#3504)
* Added instructions for license.pem Co-authored-by: Ben Arent <ben@gravitational.com>
This commit is contained in:
parent
2105c8764c
commit
5481491160
|
@ -7,7 +7,13 @@
|
|||
We provide these CloudFormation templates as an example of how to setup HA Teleport in
|
||||
AWS using our AMIs. The current template will create a Highly available Teleport setup
|
||||
using DynamoDB and S3 to store logs. This setup will acquire a Let's Encrypt x509 certificate
|
||||
for you.
|
||||
for you.
|
||||
|
||||
If you are using the enterprise template please ensure that you have an enterprise license
|
||||
available. If you are an enterprise customer you can find the license in your dashboard
|
||||
at https://dashboard.gravitational.com/web/ . Once the CloudFormation stack is complete
|
||||
you will need to place your enterprise license file onto each Auth server in
|
||||
`/var/lib/teleport/license.pem`.
|
||||
|
||||
## Launch VPC
|
||||
In this example Teleport requires a VPC to install into.
|
||||
|
@ -59,4 +65,4 @@ Once uploaded CloudFormation will ask for a bunch of parameters to configure Tel
|
|||
![Adding Setting](./img/aws-cf-oss-teleport.png)
|
||||
|
||||
The setup might take up to 20 minutes as it'll have to request a x509 certificate
|
||||
from Let's Encrypt to setup your cluster.
|
||||
from Let's Encrypt to setup your cluster.
|
||||
|
|
Loading…
Reference in a new issue