Ascend Enterprise can be deployed into customer's GCP account. Please see below on what GCP resources Ascend Enterprise requires, how to get Ascend Enterprise deployed and what's the maintenance and access expectations.
Required Resources
Ascend Enterprise (GCP) uses the following GCP services:
- Cloud SQL
- GCE (Google Compute Engine) - this API may need to be enabled before Ascend can be deployed
- GCS (Google Cloud Storage)
- GKE (Google Kubernetes Engine) - this API may need to be enabled before Ascend can be deployed
- IAM
- Load Balancer
Deployment Preparation
This section describes the 5 steps to prepare a dedicated GCP project for the Ascend Enterprise deployment.
Step 1: Create Dedicated GCP Project
Please create a dedicated GCP project within the Organization with the name ascend-io-customer-<customer_name>.


Step 2: Increase Quota
Please request resource quota increases in your desired region for Compute Engine API:
Team Size:
a. Increase “CPUs” limit from 24 to 100
b. Increase “Preemptible CPUs” limit from 24 to 100 (may already be higher)
Standard Size:
a. Increase “CPUs” limit from 24 to 500
b. Increase “Preemptible CPUs” limit from 24 to 500 (may already be higher)

Step 3: Sign Up Support Plan
Please sign up a support a GCP support plan, ideally at the level of “Production” or higher.
Step 4: Grant Ascend Access
Add the [email protected] group to the newly created GCP Project as a Project Editor
, Project IAM Admin
, Service Networking Admin
, and DNS Administrator
.


Step 5: Email Ascend Support
Once the above 4 steps are completed, please send an email to Ascend at [email protected] including the following:
- The desired region for the Ascend Enterprise deployment.
- The desired URL for Ascend Enterprise, e.g. example.ascend.io.
- The desired SSO options, such as Google, Okta, OneLogin, etc. Please follow our documentation for Okta and OneLogin to complete setup.
Deployment Process
Once Ascend receives the email containing the required information, Ascend will proceed with the deployment. This process usually completes within 48 hours after Ascend receives all required information.
Once the deployment has completed, customer will have access to Ascend Enterprise at the preferred URL, e.g. example.ascend.io.
Maintenance & GCP Project Access
Ascend will be responsible for new software releases and maintenance of all services within this GCP project.
Ascend Access
Ascend infrastructure team require access to the GCP project at all times to ensure reliability, performance, and code deployments.
Customer Access
Customer will also retain access to this GCP project for auditing purposes. Ascend does not recommend customer to host any other services in this GCP project other than Ascend Enterprise.
Updated 14 days ago