»Public Beta Limitations
»Overview
HCP BoundaryBETA does not have an SLA or Availability Guarantee of a production-grade tool. This Public Beta version is meant to collect early user feedback on the common workflows. Please avoid using HCP BoundaryBETA in your critical, production-level environments. The following is a breakdown of some, but not all, of the limitations that you should be aware of.
»Production Use & Reliability
HCP Boundary is in Beta and does not yet have an SLA or Availability Guarantee of a production-grade tool. Please do not gate your critical, production-level environments using HCP Boundary in Beta. HCP Boundary's Beta is meant to get early user feedback for common workflows, and is not designed to support production environments.
»Identity
HCP BoundaryBETA does not allow single sign-on using platform identities from the HashiCorp Cloud Platform. This feature will be available in the GA timeframe. Boundary will be deployed with an admin identity bound to a username and password auth method. These credentials will be provided by the user when they first set up HCP Boundary, and can be used to create other identities (users and auth methods) in HCP Boundary, including setting up an OIDC integration to ingress identities from an external identity provider.
»Data
While running, Boundary persists user's personally identifiable information (PII), including email addresses. This can be deleted by deleting your Boundary environment.
»Multi-Tenancy
HCP Boundary is a multi-tenant service. All tenants' Boundary controllers and workers are managed on a common network. HCP Boundary uses a multi-tenant Postgres RDBMS with each tenant receiving its own database on the cluster.
»Vault Integration
HCP BoundaryBETA only works with Vault environments on a public subnet. We recommend using an HCP Vault dev cluster (remember to configure public connections on step 11 of the HCP Vault deployment guide).
»Upgrades
Your HCP Boundary environment may be updated at any time during Beta. While HashiCorp makes no guarantees around uptime or scheduling of updates, we will do our best to notify users in advanced prior to making any updates to HCP BoundaryBETA.
»Enterprise Support & SLA
HCP BoundaryBETA does not yet offer enterprise support packages. Support is best-effort during US time-zone business hours. Should you experience an issue with the HCP BoundaryBETA that requires support, you can file a ticket here.