Deploy Couchbase on Google Cloud C4A
Introduction
Get started with Couchbase on Google Axion C4A
Create a firewall rule on GCP
Create a Google Axion C4A Arm virtual machine on GCP
Install Couchbase
Perform Couchbase baseline testing
Benchmark Couchbase
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Introductory
Reading time:  30 min
Last updated:  31 Jul 2026
Skill level:
  Introductory
Reading time:
  30 min
Last updated:
  31 Jul 2026
Author:Pareena Verma, Arm
Arm IP:Neoverse
Tags: Databases Google Cloud Linux Couchbase
Author:
  • Pareena Verma, Arm
Arm IP:
Neoverse
Tags:
Databases Google Cloud Linux Couchbase

Who is this for?

This is an introductory topic for developers deploying Couchbase workloads on Arm Linux environments, specifically using Google Cloud C4A virtual machines (VM) powered by Axion processors.

What will you learn?

Upon completion of this Learning Path, you will be able to:

  • Provision an Arm-based SUSE Linux Enterprise Server (SLES) virtual machine on Google Cloud (C4A with Axion processors)
  • Install Couchbase Server on the SUSE Arm64 (C4A) instance
  • Verify Couchbase deployment by accessing the web console, creating a test bucket, and confirming cluster health
  • Benchmark Couchbase by measuring operations per second (ops/sec), memory utilization, and disk performance on the Arm platform

Prerequisites

Before starting, you will need the following:

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll deploy Couchbase Server on an Arm-based Google Cloud C4A virtual machine and validate the setup for benchmarking. You’ll provision a C4A instance, expose the Couchbase Web Console with a firewall rule, install Couchbase on a SUSE-based Arm64 VM, initialize the cluster, and create a test bucket. By the end, you’ll confirm the node is healthy and the bucket is ready for read and write benchmarking with external tools.

Frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
What result should I expect when I open `http://<VM_IP>:8091`?
You should see the Couchbase Web Console for initial setup or login. After completing the setup, the Servers page should show your node as healthy and your test bucket should appear in the Buckets view.
I can’t reach the Couchbase Web Console on port 8091 — what should I check?
Create a GCP firewall rule that allows TCP port 8091 and applies to your instance. Confirm that the VM is running, note its external IP, and try again.
Which package manager should I use to follow the installation steps?
The steps use zypper for SUSE-based systems. Follow the commands as shown to refresh repositories, update the system, and install required tools before adding Couchbase.
How do I know the environment is ready for benchmarking?
Confirm that the web console responds on port 8091, cluster initialization is complete, the node shows healthy status, and a test bucket exists. These checks indicate that the deployment is ready for workload testing.
When should I run YCSB workloads against Couchbase?
Run YCSB after you verify console access, complete cluster setup, and create a bucket. The specific YCSB commands aren’t listed here, so use your verified bucket name and credentials when you proceed.
Next