Deployment overview

1. Initial Login and Consent

When you first log into the Admin Console to provision an instance, you'll be prompted to consent to an application. This application helps populate an Azure Resource Manager (ARM) template with the necessary configuration.

At this point, you'll need to provide:

• Your Azure Tenant ID
• Your Azure Subscription ID

2. ARM Template Deployment

After downloading the ARM template, you'll deploy it within your Azure subscription. This template performs the following actions:

• Creates resource groups
• Establishes managed identities
• Assigns roles to those identities within specific resource group scopes
• Deploys Azure Lighthouse to allow IBM SRE (Site Reliability Engineering) access to selected resources in your subscription

3. Data Plane Creation

Once the ARM template is deployed, you'll proceed to create the Data Plane. This step installs the core infrastructure components, including:

• Azure Service Bus
• Azure Monitor
• Azure Kubernetes Service (AKS) cluster

These components are provisioned using the roles and identities set up in the previous step. The Data Plane also includes necessary add-ons and prepares the environment for engine provisioning.

4. Engine Provisioning

In the final step, you'll provision the Db2 engine based on your selected deployment model. During this process:

• Required storage and compute nodes are automatically provisioned (nodes are managed by the Auto Scaler, and Node Groups are defined during Data Plane setup)
• A Db2 Warehouse multi-tenant console is deployed alongside the engine

You'll receive access to two endpoints:

• One for the Db2 engine instance
• One for the management console