-
Notifications
You must be signed in to change notification settings - Fork 392
CloudBeaver Enterprise deployment in Google Cloud
- Overview
- Prerequisites
- Deployment in Google Cloud Console
- Deployment with Google Cloud CLI
- CloudBeaver public image URIs
This guide shows how to deploy CloudBeaver Enterprise on Google Cloud Platform (GCP) using both the Google Cloud Console and the Google Cloud CLI.
Before you begin, make sure you have:
- A Google Cloud account for accessing GCP services.
- Compute Engine set up in your project.
If you don’t have a GCP account, sign up on the Google Cloud signup page.
To deploy CloudBeaver in Google Cloud, you need certain permissions to create and manage resources like virtual machines, disks, and networks. Ensure you have the necessary permissions for your project.
Tip: For a full list of permissions and more information on how to manage them, see the official Google Cloud Permissions documentation.If you don’t have the required permissions, contact your system administrator.
-
Log in to the Google Cloud Console, then go to Compute Engine -> Images. Click [+] Create image.
-
Complete the Create an image form:
- Enter the image name in the format
cloudbeaver-ee-server-ubuntu-%version%
orcloudbeaver-ee-server-rhel-%version%
, depending on the operating system. - Select Virtual disk (VMDK, VHD), and in the Virtual disk file field, enter this URI:
cloudbeaver-ee-server/
. Click BROWSE and choose your version.
- Enter the image name in the format
Tip: Replace
%version%
with the desired version number, such as24-2-0
.
- Click Create. The process may take up to 15 minutes.
-
After the image is imported, navigate to the Images tab, find your imported image, and click [+] Create instance.
-
Name your instance and set up the following:
- Under Machine configuration, choose a machine type with at least 1 CPU and 4GB RAM for optimal CloudBeaver performance.
- Click Change, select your custom image, and set the disk size to at least 100GB.
-
In the Firewall section, check Allow HTTP traffic and Allow HTTPS traffic to make the instance accessible online.
-
Click Create. Your instance will be ready in a few minutes. Verify by pasting its External IP into your browser.
-
Begin the initial configuration of the CloudBeaver server in your browser.
Tip: For more detailed steps on configuring and managing the server, see the Managing cloud deployed services guide.
-
In the Google Cloud Console, go to Compute Engine and click Activate Cloud Shell to launch the CLI within GCP.
-
Authorize any prompts if needed.
Run this gcloud
command to create a new instance:
gcloud beta compute instances create cloudbeaver-ee-server \
--zone=us-central1-a \
--machine-type=e2-medium \
--tags=http-server,https-server \
--image=https://www.googleapis.com/compute/v1/projects/dbeaver-public/global/images/cloudbeaver-ee-ubuntu-24-2-0 \
--create-disk=auto-delete=yes \
--boot-disk-size=100GB --boot-disk-device-name=cloudbeaver-ee-server
You can customize the command as needed. For more details on using the Google Cloud CLI, see the official documentation.
Tip: Replace the
--image
URL with a different version if needed.
- After the instance is created, retrieve its external IP (needed for accessing the CloudBeaver server):
gcloud compute instances list --filter="name:cloudbeaver-ee-server" --format="get(networkInterfaces[0].accessConfigs[0].natIP)"
This command will return the external-ip
, which you’ll need to begin the initial setup.
-
Use the
external-ip
to start configuring and accessing the CloudBeaver interface. -
In your browser, go to
http://<external-ip>/
, where<external-ip>
is the public IP address of your GCP instance. -
You’ll be redirected to CloudBeaver’s initial configuration wizard to complete the setup.
Tip: For guidance on locating your instance's public IP address, see GCP: Viewing IP Addresses.
https://www.googleapis.com/compute/v1/projects/dbeaver-public/global/images/cloudbeaver-ee-ubuntu-%version%
https://www.googleapis.com/compute/v1/projects/dbeaver-public/global/images/cloudbeaver-ee-rhel-%version%
Tip: Replace
%version%
with the desired version number, such as24-2-0
. For more information on tags, see CloudBeaver release cycles.
- Application overview
- Demo Server
- Administration
- Server configuration
- Create Connection
- Connection Templates Management
- Access Management
-
Authentication methods
- Local Access Authentication
- Anonymous Access Configuration
- Reverse proxy header authentication
- LDAP
- Single Sign On
- SAML
- OpenID
- AWS OpenID
- AWS SAML
- AWS IAM
- AWS OpenId via Okta
- Snowflake SSO
- Okta OpenId
- Cognito OpenId
- JWT authentication
- Kerberos authentication
- NTLM
- Microsoft Entra ID authentication
- Google authentication
- User credentials storage
- Cloud Explorer
- Cloud storage
- Query Manager
- Drivers Management
- Supported databases
- Accessibility
- Keyboard shortcuts
- Features
- Server configuration
- CloudBeaver and Nginx
- Domain manager
- Configuring HTTPS for Jetty server
- Product configuration parameters
- Command line parameters
- Local Preferences
- API
-
CloudBeaver Community
-
CloudBeaver AWS
-
CloudBeaver Enterprise
-
Deployment options
-
Development