Teleport Cloud FAQ
Teleport Cloud commits to SLA of 99.5%% of monthly uptime percentage, a maximum of 3 hours 40 minutes of downtime per month.
Reach out to sales to discuss pricing.
We use AWS-managed keys. Currently there is no option to provide your own key.
It's a Teleport-managed S3 bucket with AWS-managed keys. Currently there is no way to provide your own bucket.
You can connect servers, kubernetes clusters, databases and applications using reverse tunnels.
There is no need to open any ports on your infrastructure for inbound traffic.
We have made changes to allow you to log into your cluster using
tsh, then use
tsh login --proxy=myinstance.teleport.shtctl status
You must use the enterprise version of
If you have a local file
/etc/teleport.yaml on your machine
tctl will attempt to use the local cluster. Set the environment variable
"" so it will not attempt to use that Teleport configuration file.
export TELEPORT_CONFIG_FILE=""tctl tokens add --type=node
tctl nodes add --ttl=5m --roles=node,proxy --token=$(uuid)
Security audit has been completed and is available here.
Teleport Cloud is deployed using a Gravity cluster on AWS.
We will be upgrading the preview version of Teleport Cloud automatically.
We completed our most current SOC2 type 2 audit on April 12th, 2021.
The report covers:
- Teleport Open Source
- Teleport Enterprise, self-hosted
- Teleport Enterprise, cloud-hosted
Reach out to https://goteleport.com/cloud/sales for report details.
Not at this time.
FIPS is not currently an option for Teleport Cloud clusters.
Password hashes are generated using Golang's bcrypt.
Teleport uses letsencrypt.org to issue certificates for every customer. It is not possible to upload a custom certificate or use a custom domain name.
Each deployment is using at-rest encryption using AWS DynamoDB and S3 at-rest encryption for customer data including session recordings and user records.