Install Using OCI Stacks

Pre-General Availability: 2026-03-13

Install Using OCI Stacks

Complete these steps to install the product by deploying an OCI stack.

Prerequisites

Before you begin the installation process, ensure that you have the following prerequisites:

Access to an Oracle Cloud Infrastructure (OCI) tenancy and permissions to create and manage Resource Manager stacks, compute and networking resources, and Container Registry and Kubernetes (OKE) resources.
The Resource Manager stack packages in .zip format for Oracle Blockchain Platform Enterprise Edition for Hyperledger Besu.
A basic understanding of blockchain concepts and Hyperledger Besu. For more information about Hyperledger Besu, see Besu Ethereum client.
Oracle Cloud Stack prerequisites:
- A base domain name (for example, obpee.example.com) for hosting the Blockchain Platform Manager and service console fully-qualified domain names
- Passwords for the Blockchain Platform Manager administrator and LDAP administrator
- An OCI Registry (OCIR) user name and active auth token
- Cluster details such as worker node count and OCPU and memory specifications

To get your OCIR user name and auth token, complete the following steps.

In the OCI console, select Profile and then select your user account.
Open Tokens and keys.
Under Auth tokens, create a token and then copy it and store it securely.
Determine your OCIR user name, which typically uses the following format: <tenancy-name>/oracleidentitycloudservice/<username>. For example, acmeinc/oracleidentitycloudservice/dev.user@example.com.

For more information, see Logging in to Oracle Cloud Infrastructure Registry.

EVM Compatibility

The platform is based on Hyperledger Besu v25.12, which supports Shanghai and Cancun EVM smart contracts. Use the platform to test and assess product capabilities and develop integrations. Do not use the platform in a production environment. API contracts might change between platform releases.

The following table shows the minimum versions of Solidity and Hardhat that can be used.

EVM Version	Minimum Solidity Version	Minimum Hardhat Version
Shanghai	0.8.20	2.14.0
Cancun	0.8.24	2.21.0

Create the Stack

You use Oracle Cloud Stack to create and deploy Oracle Blockchain Platform Enterprise Edition for Hyperledger Besu

Log in to OCI and then navigate to Developer Services, and then Resource Manager, and then Stacks.
Click Create Stack.
On the Stack information page, select My configuration, select the Zip file radio button, and then upload the .zip file that contains the stack configuration. For the limited availability release, the URL of the .zip file is provided by your Oracle point of contact in sales or product management.
Optionally customize the Stack Information fields. All fields are completed with defaults.
1. Custom provider
  Custom providers are not supported at this time.
2. Name
  Name of the stack. It has a default name and provides a date time stamp. You can edit this if desired.
3. Description
  Description of the stack that you are creating.
4. Create in compartment
  Defaults to the root compartment of your OCI tenancy.
5. Terraform version
  Ensure version 1.1.x or later is selected.
6. Tags
  Optional. Tags are a convenient way to assign a tracking mechanism.
Click Next.
Provide a name for the stack and enter the required parameters.
Blockchain Platform Configurations
1. Domain Name
  Specify the domain URL for hosting Blockchain Platform Manager and the service console. The default is Besuee.com.
2. Administrative User Password
  This is used to set the Blockchain Platform Manager administrative user's (obpadmin) password.
3. LDAP User Password
  This is used to set the administrative user's password for the LDAP authentication server.
OCIR Image Configurations
1. OCIR Username
  User name used to log into Oracle Cloud Infrastructure Registry. Enter the name of the user in the format:
```
<tenancy-namespace>/<username>
```
  where <tenancy-namespace> is the auto-generated Object Storage namespace string of the tenancy in which to create repositories (as shown on the Tenancy Information page). For example
```
ansh81vru1zp/jdoe@example.com
```
  Note that for some older tenancies, the namespace string might be the same as the tenancy name in all lower-case letters. For example,
```
example-dev
```
  If your tenancy is federated with Oracle Identity Cloud Service, use the format
```
<tenancy-namespace>/oracleidentitycloudservice/<username>
```
  See Logging in to Oracle Cloud Infrastructure Registry.
2. OCIR Auth Token
  The auth token used to access OCIR.
Kubernetes Cluster Configurations
1. Cluster Name
  Name of the OCI Kubernetes Engine cluster that will be created. Subsequent resources will also contain this name. In the final state, the deployment_id generated by the apply job will be added to this.
2. Node Pool Name
  Name of the node pool for the worker nodes.
3. Enable Cluster Autoscaler for Node Pool
  This will enable node pools to autoscale based on resource usage and will add and remove worker nodes as needed. When set to False, the Maximum Number of Worker Nodes tab is hidden.
4. Minimum Number of Worker Nodes
  The minimum number of nodes in the node pool. If autoscaling has not been enabled, this is the total number of worker nodes available. The default is 1. At a minimum, 1 worker node is required.
5. Maximum Number of Worker Nodes
  The maximum number of nodes in the node pool. This is only available if autoscaling has been enabled. The default is 10. The maximum is 100.
6. Worker Nodes Instance Shape
  Select the appropriate compute shape. The default is VM.Standard.E5.Flex. For information on supported shapes and their configurations, see: Supported Compute Shapes.
7. Worker Node OCPU Count
  The number of OCPUs for each worker node compute instance. The minimum is 4 OCPUs. The maximum is 64 OCPUs.
8. Worker Node Memory (GB)
  The amount of memory for each worker node compute instance. The minimum is 64 GB. The maximum is 1024 GB.
Review the information, and then create the stack by selecting Run Apply and then Create.
The stack creation process begins, which includes the deployment of resources such as a compute VM (jump host) and Kubernetes clusters.
Wait for stack creation to complete, which typically can take 40-45 minutes. Monitor the stack creation job and logs to track the deployment progress.
Once the stack job is marked Succeeded, the Application Information tab will be available. The information on this tab can be used to configure access to Blockchain Platform Manager.
For more information about these fields, see Application Information.