self-hosted/teleport
self-hosted/teleport
1
0
Fork 0
mirror of https://github.com/gravitational/teleport synced 2024-10-21 01:34:01 +00:00
Code Issues Packages Projects Releases Wiki Activity

[docs] Added instructions for license.pem (#3504)

Browse source 
* Added instructions for license.pem
Co-authored-by: Ben Arent <ben@gravitational.com>
This commit is contained in:
Jonathon Canada 2020-03-31 10:02:39 -07:00 committed by GitHub
parent 2105c8764c
commit 5481491160
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
examples/aws/cloudformation/README.md
View file

@ -7,7 +7,13 @@
We provide these CloudFormation templates as an example of how to setup HA Teleport in 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 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 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 ## Launch VPC
In this example Teleport requires a VPC to install into. 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) ![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 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.