Couchbase (cluster)

Deploy Couchbase, an enterprise-class NoSQL database built with a memory-first architecture, built-in caching, and workload isolation. The Couchbase cluster deploys three, five, or seven connected Enterprise Server nodes split between Data, Index, and Query services, allowing quick deployment and cluster expansion through Couchbase's multi-dimensional scaling.

šŸ“˜

Couchbase Enterprise Server license

Couchbase Enterprise Server is not free to use in production. Contact Couchbase Support to activate your license on Akamai Cloud and enable Couchbase application support.

1. Deploy Couchbase cluster

Ā Estimated deployment time:Ā 10–20 minutes

Follow the deployment instructions from the Get started section to configure the app, deploy it, and verify software installation.

For information on the app-specific configurations, see the Configuration options section.

Base distribution and plan

  • Supported distribution: Ubuntu 24.04 LTS
  • Minimum plan: Couchbase Enterprise Server requires 8GB of RAM.
  • Suggested plan: Use 16GB of RAM for production deployments.
🚧

Minimum RAM requirements

Deploying the Couchbase Enterprise Server cluster on a plan with less than 8GB of RAM fails. Your account is billed for any failed instances deployed with less than 8GB of RAM.

Configuration options

Configure the required options to deploy your instance. For additional customization, add advanced options.

The table maps the Cloud Manager UI fields to their corresponding API/CLI keys (stackscript_data) required for automated deployments.

StackScript ID: 1366191

UI fieldAPI/CLI keyDescription
Required options
Linode API tokentoken_passwordA valid Linode API token with grants to deploy Linode instances. Follow Manage personal access tokens to get the token on your account with Read/Write access to Linodes.
Limited sudo useruser_nameYour preferred username for the limited sudo user entered without any capital letters, spaces, or special characters.
When adding a limited sudo user, the user is created with a strong generated password for your new Linode instance, and the account is assigned to the sudo group, which provides elevated permissions when running commands with the sudo prefix.
Note: For easier and more secure access with the sudo user, add an account SSH key for the Cloud Manager user during deployment and select that user as an authorized_user. Their SSH pubkey will be assigned to both the root and limited user.
Email addressemail_addressThe email address to use for generating SSL certificates and the self-signed certificate authority (CA).
SSL InformationsslheaderSet to Yes by default. This requires providing details for a self-signed TLS/SSL certificate, like country, town, organization, and email address.
Country or regioncountry_nameApplies to a self-signed TLS/SSL certificate. The country or region for you or your organization. When using the API/CLI, specify it as a two-letter ISO country or region code.
State or provincestate_or_province_nameApplies to a self-signed TLS/SSL certificate. The state or province for you or your organization.
Localitylocality_nameApplies to a self-signed TLS/SSL certificate. The town or other locality for you or your organization.
Organizationorganization_nameApplies to a self-signed TLS/SSL certificate. The name of your organization.
Advanced options
Couchbase Server Countcluster_sizeThe number of Couchbase Enterprise Server instances deployed. Possible values are 3, 5, or 7. Defaults to 3.
CA Common Nameca_common_nameApplies to a self-signed TLS/SSL certificate. The common name for the self-signed Certificate Authority (CA). Defaults to Couchbase CA.

Note: After the app deployment completes, the password for your limited sudo user is generated and stored in the .credentials file in the home directory, along with application-specific passwords. Log in to your instance as root through the Lish console or SSH, then run cat /home/$USERNAME/.credentials to view its contents.

Use API, CLI, or Terraform

In addition to deploying the app to a new Linode instance via Cloud Manager, you can also use the Linode API, CLI, or Terraform. When running the operation, you need to provide the StackScript ID, supported Linux distribution, and app-specific fields along with the standard Linode deployment configurations.

Note: Generate a personal access token to authenticate your API, CLI, or Terraform requests.

curl --location 'https://api.linode.com/v4/linode/instances' \
    --header 'Content-Type: application/json' \
    --header 'Accept: application/json' \
    --header 'Authorization: Bearer abc123def456hij789klm' \
    --data-raw '{
        "region": "us-east",
        "type": "g6-standard-8",
        "image": "linode/ubuntu24.04",
        "label": "my-couchbase-cluster-one-click-app",
        "root_pass": "@C0mpl3x#P@ssw0rd",
        "stackscript_id": 1366191,
        "stackscript_data": {
            "token_password": "abc123def456hij789klm",
            "sudo_username": "jsmith",
            "email_address": "jsmith@example.com",
            "country_name": "US",
            "state_or_province_name": "Massachusetts",
            "locality_name": "Cambridge",
            "organization_name": "Akamai Technologies"
        }
    }'
linode-cli linodes create \
    --region us-east \
    --type g6-standard-8 \
    --label my-couchbase-cluster-one-click-app \
    --image linode/ubuntu24.04 \
    --root_pass @C0mpl3x#P@ssw0rd \
    --stackscript_id 1366191 \
    --stackscript_data '{"token_password":"abc123def456hij789klm", "sudo_username":"jsmith", "email_address":"jsmith@example.com", "country_name":"US", "state_or_province_name":"Massachusetts", "locality_name":"Cambridge", "organization_name":"Akamai Technologies"}'
resource "linode_instance" "my-linode" {
    region         = "us-east"
    type           = "g6-standard-8"
    label          = "my-couchbase-cluster-one-click-app"
    image          = "linode/ubuntu24.04"
    root_pass      = "@C0mpl3x#P@ssw0rd"
    stackscript_id = 1366191
    stackscript_data = {
        "token_password"         = "abc123def456hij789klm"
        "sudo_username"          = "jsmith"
        "email_address"          = "jsmith@example.com"
        "country_name"           = "US"
        "state_or_province_name" = "Massachusetts"
        "locality_name"          = "Cambridge"
        "organization_name"      = "Akamai Technologies"
    }
}

2. Access the Couchbase server

  1. Open your web browser and navigate to the rDNS address of the cluster provisioner. This is the instance labeled couchbase-occ-1-[region]-[uuid].

    See Manage IP addresses on a Linode for details on viewing your instance’s IP addresses and rDNS.

  2. Sign in to the dashboard using the username Administrator and the generated password located in /home/$sudo_username/.credentials.

  3. Once logged in, you can view the status of all cluster nodes from the Servers tab and start configuring buckets.

Manage firewall and security

The cluster deploys with preconfigured UFW firewall rules. These rules limit allowed traffic on node-to-node and cluster-to-cluster Couchbase ports to IP addresses within the cluster.

Only the cluster provisioner has firewall access configured for web and client ports.

The cluster manages these UFW configurations with application profile files in the /etc/ufw/applications.d directory. See Configure a Firewall with UFW for details on using UFW.

Activate your license

Contact Couchbase Support to activate your license on the newly deployed cluster before using it for testing, quality assurance, or in production. An active enterprise license is required for any use other than internal development or software evaluation.

Additional resources

For more information about the installed packages, see their official documentation.

šŸ“˜

Note that we can't vouch for the accuracy or timeliness of externally hosted resources.


Did this page help you?