Couchbase have created a number of different AMIs that are available within the Amazon Web Services Marketplace. You can see the full list of available AMIs using this link.
The AMIs share the following attributes:
Based on the current release version for Couchbase Server 1.8.
Use the Amazon Linux operating system
Supported on 64-bit AMI
Use the Amazon EC2 and Amazon EBS services
Configured with a single EBS volume for persistent storage
To launch an AMI you can use either the 1-Click Launch method, or the custom configuration (Launch with EC2 Console) method. The 1-Click Launcher method configures a number of settings for you automatically, including configuring the firewall port configuration. This method also pre-installs Couchbase Server for you and configures it ready to use by logging into the Couchbase Server Administration Web Console.
For the EC2 Console method, Couchbase Server will be automatically installed for you, but you must configure your security group settings for the firewall and port configuration by hand.
To create an instance using the 1-Click method:
Visit the AWS Marketplace and select the Couchbase Server AMI you want to use. See the AWS Marketplace using this link.
Select the Region you want to use when launching your Couchbase Server node. Note that if you are create a new multi-node cluster, all your nodes should be located within the same region.
Select the EC2 instance type you want to use for your nodes. Each node you create should be of the same type.
Select the key pair you want to use when connecting to the node over ssh.
Click. This will create your new instance.
Once the instance has been created, you will be presented with the deployment details. Take a note of the Instance ID.
Visit the EC2 Management Console and click on the instance ID for the instance just created. In the instance detail panel, make a note of the Public DNS hostname. You will need this to login to your Couchbase Server installation.
To connect to your Couchbase Server installation, open a
browser and connect to the instance URL on port 8091. For
You will be prompted for the user and password for the Couchbase Server web console:
Password is your instance ID
Once you have successfully logged in, you should be presented with the Couchbase Server Administration Web Console Cluster Overview window. The server will have been automatically configured for you.
Once the instance has been started, it will operate the same as any Couchbase Server instance.
Adding more nodes to your cluster
You can add nodes to your cluster by starting additional instances and adding them to the cluster. To add each node to your cluster, follow these steps:
Start a new instance of EC2 using the same Couchbase AMI and EC2 instance type as used by your existing cluster nodes.
For each node that you want to add to the cluster, make a note of the internal IP address of each node. You can find this information by clicking on each instance within the EC2 Management Console. The internal IP is shown in the Private IP Address section of the instance panel.
Open the Administration Web Console for one of the servers in your existing EC2 Couchbase Server cluster.
Go to the Manage Server Nodes section of the Web Console.
Administrator and the password will be
the individual instance ID.
Once you have added your nodes, perform a rebalance operation to enable your nodes within the cluster. For more information, see Section 5.3, “Rebalancing (Expanding and Shrinking your Cluster)”.
Changing your Couchbase Server Administrator password
To change your Couchbase Server password, you must ssh to your instance using the SSH key pair you selected during instance creation:
shell> ssh -i keypair.pem ec2-user@
Once you are connected, you need to use the Couchbase command line client to change the password:
remote-shell> /opt/couchbase/bin/couchbase-cli cluster-init \ -c 127.0.0.1:8091 \ -u Administrator -p OLD_PASSWORD \ --cluster-init-password=NEW_PASSWORD
This will configure the Administrator password for the cluster.
For information on typical administration tasks, including failover, backup, and rebalancing, see Chapter 5, Administration Tasks.