AWS FAQ
Yes, we have a fully-managed privately-hosted product. Customers who upgrade to this level will be able to run an AWS integration in the account of their choice. We will build and manage an EKS cluster in the account and region that you grant permissions for us to do so. Deploying your workloads will then run in your own account on your own servers in a separate VPC. You do not have to (and we ask you not to) do anything to maintain or troubleshoot or manage this EKS cluster.
Yes, some customers who wish to separate out their Release workloads from other private or test workloads can create clusters across boundaries like pre-production and production accounts for complete isolation. Please let us know before you do this or if you plan to do this as we want to make sure the processes and workflows you use with Release makes sense and work seamlessly.
Yes, customers who upgrade to the fully-managed, privately-hosted can elect to build multiple clusters in the same or in different regions, in the same or in different accounts. Please let us know before you do this or if you plan to do this as we want to make sure the processes and workflows you use with Release makes sense and work seamlessly.
ECR support is available to customers who upgrade to self-hosted clusters. View our guide on how to configure cross-account ECR access.
Yes, customers who upgrade to the fully-managed, privately hosted product have access to our Instant Datasets product which allows customers to have seeded or production-like databases for each environment. If you wish to use live access to an existing RDS instance we can perform integrations with other AWS services as described below.
Customers who upgrade to the fully-managed, privately-hosted product can have access to their private cluster to allow access to on-premise networks via P2P VPNs, or use a Client VPN to connect directly to the services running in the cluster. As with all complex integrations, we would need to work closely with you to gather all the information on scope, timing, level of effort, and so forth to work with you on this integration. Contact your sales person for help!
This access is integrated with either a P2P VPN or Client VPN attached to a Transit Gateway. This allows very flexible attachments and routing options for services in your cluster.
Customers who upgrade to the fully-managed, privately-hosted product can have access to other assets and services and networks (like VPCs, security groups, RDS instances, Kinesis etc.) in their accounts with some caveats and exceptions. To be safe and sane, we keep our EKS managed cluster and software running in a separate VPC. We do support peering, using Transit Gateway, RDS proxy, and Private Link integrations but these integrations are not stock or off the shelf and require some setup, configuration, documentation, and so forth that could be very unique to each scenario.
Thus, although we can support such integrations, you need to work with us on a close basis to plan and implement it so that it will work properly for your scenario. Contact your sales person for help!