MarkLogic and Amazon Web Services

To help you get going in the cloud quickly, MarkLogic provides Amazon Partner Amazon Machine Images (AMIs) and Cloud Formation templates. The templates, which build on the AMIs, can be used to construct MarkLogic Managed Clusters.

MarkLogic AMIs

MarkLogic provides two AMI series, Developer and Essential Enterprise.

The free Developer AMI is suited for a variety of purposes, from development to proof-of-concept work. You can also bring your own license (BYOL) to this AMI (and use it for those purposes allowed by the terms of your license). After you start up this AMI, you must request and install a free developer license key OR install your own pre-paid license key.

Available for purchase hourly, the Essential Enterprise AMI comes with a pre-packaged MarkLogic Essential Enterprise license key and the following features:

  • Search
  • HA/DR/Replication
  • Government-grade Security
  • Alerting
  • Location Services
  • Semantics (Limited-time, promotional offer)

If you prefer, you can also build your own custom AMIs using MarkLogic installers.*.

Launching an AMI with EC2 Console

To gain the benefits of high-availability and scalability, the best practice is to run MarkLogic as a cluster. The MarkLogic Cloud Formation templates provide the easiest way to make use of MarkLogic Managed Clusters, described below.

If you prefer to launch an AMI directly, here are the steps (these are covered in the short video below):

  1. Create yourself an Amazon account and sign up for Amazon Web Services. (You may need to provide personal details, verification, credit card information and the like).
  2. Browse to the AWS Marketplace, search for marklogic, choose an AMI (or choose one of the Marketplace links from this page), select a region, and accept the terms.
  3. Launch the AMI with the EC2 Console:
    • Choose a supported instance type (NB: MarkLogic AMIs will not run on micro instances).
    • Add EBS storage. Specifically, assign an EBS volume to /dev/sdf and leave off the Delete-on-termination checkbox, to enable you to keep your data. (If you prefer, you can launch the AMI and subsequently attach an existing EBS volume to /dev/sdf).
    • Use a Security Group that will open ports 7997-8100. (If you don't have such a group, you can create one directly in the EC2 Console UI).
    • Proceed to start your instance.
  4. When your instance is started, you can browse to the Admin UI on your host's port 8001. Log in with user "admin"; the password is set to the value of the instance ID.

Getting Started with MarkLogic on EC2

This video is best watched in full-screen mode, 720p resolution

Cloud Formation Templates and MarkLogic Managed Clusters

To gain the benefits of high-availability and scalability, the best practice is to run MarkLogic as a cluster. The MarkLogic Cloud Formation templates provide the easiest way to make use of MarkLogic Managed Clusters, the benefits of which include:

  • Automatic handling of changes in EC2 instance hostnames.
  • Automatic placement and management of data, to insure that nothing is lost on transient volumes.
  • Configuration of best-practice security, load balancing, routing, and handling of volatile instances.
  • Automatic restarting and reconfiguring of failed or unhealthy nodes in a cluster.
  • Pausing of entire clusters, while maintaining all configuration and data.
  • Simplified re-configuration of cluster instance types and topologies.

If you choose to launch the MarkLogic AMIs outside of the Cloud Formation templates, you will not have automatic access to the Managed Cluster features. (You can still gain access to those features via your own custom configuration and automation and the documented series of environment variables and the mlcmd utility.) For these reasons, we highly recommend starting with the Cloud Formation templates, even if you plan to start with a single-node cluster.

The templates serve both as Getting Started points as well as examples. Once you are comfortable with them, we encourage and expect you to copy and modify them to suit your specific needs.

NOTE: Successful launching of EC2 instances via a Cloud Formation template requires acceptance of the License Agreement for the underlying AMI. Please visit the corresponding AWS Marketplace AMI page to accept the License Agreement before attempting to launch a stack from any of the templates. For details see the Getting Started video below.
Description AWS Marketplace page (including Agreement Terms) Template URL Launch in US East (N. Virginia) Region
Single-instance Developer (Free, BYOL) Developer SingleNode-BYOL.template Launch
Cluster Developer (Free, BYOL) Developer ThreePlusCluster-BYOL.template Launch
Single-instance Essential Enterprise Essential Enterprise SingleNode-Enterprise.template Launch
Cluster Essential Enterprise Essential Enterprise ThreePlusCluster-Enterprise.template Launch

Getting Started via Cloud Formation templates

This video is best watched in full-screen mode, 720p resolution


Community-based support can be found on the developer website, by joining the mailing list as well as Q & A. Beyond that, please also see the Developer Support Program we offer.



Any distribution or sale of custom AMIs with MarkLogic installed is subject to MarkLogic License Agreement terms.


  • Hello, Anyone know which type of Failover 3-node cluster is configured with? Cloudformation architecture leads me to think that this is 'Local-disk failover' as each ASG has MarkLogic data however looking at boot messages on Slaves I can see that Forests are mounted remotely on Master and in fact when I kill Master node, the whole cluster is offline until new Master is created. None of the Slaves are promoting itself to become Master. Could it be that this managed cluster is just not completely configured for replication or this setup is in fact 'Shared-disk replication' and if Master Node goes down, we need to create new one and there's no way around it? Any advice appreciated, Thanks
  • Hello everyone, I have a problem on my ML server as it’s flooding /var/log/messages with the following errors: MarkLogic: Failed to update hostname on server localhost MarkLogic: Failed renaming my host via localhost MarkLogic: [/opt/MarkLogic/mlcmd/scripts/initialize-node.xsh line: 59] MarkLogic: Failed renaming my host to all online cluster hosts - waiting ... MarkLogic: Original host name <HOSTNAME-FROM-SMALLER-INSTANCE> does not match our new host name <NEW-HOSTNAME-AFTER-INCREASE> ... MarkLogic: Attempting to contact localhost to rename my hostid 4182996195802625515 to host <NEW-HOSTNAME-AFTER-INCREASE> MarkLogic: [/opt/MarkLogic/mlcmd/scripts/initialize-node.xsh line: 51] MarkLogic: Renaming host to <NEW-HOSTNAME-AFTER-INCREASE> on localhost I’m running MarkLogic 7.0-5.4 on ec2 under ASG usingCloudFormation template that was provided by MarkLogic. I terminated instance and new one was provisioned by ASG and everything seems to work but old hostname is showing 'at the top' when you login to console on port 8001 and log is flooded with above messages. I've sent message to mailing list but there was no response so I'm trying here. Any advice appreciated, Thank you
  • 3:15h latter - You can access the Administration portal on port 8001 using username "admin"and the password equal to the EC2 instance ID (e.g. "i-71feaa04).
  • Hi, is there a default admin password for ootb instances? I am trying to access the instance via browser, but I am getting a "User Name" and "Password" dialog, with the message "Authentication Required", "The server says: public". I have created the EC2 instance following your steps (MarkLogic 8 developer version - the onlyone available right now). It is running and status checks are fine. When I copy the public DNS with port 8001, I get the dialog - instead of the nice screen you get from the video.
  • When I launch the MarkLogic Essential Enterprise with an m2.2xlarge. If I change the instance type to the m2.4xlarge, does the Amazon/MarkLogic takes the license extend to 8-Core CPU autmatically or you will limit it the license and usage to the original instance type(m2.2xlarge). Regards, -Praveen
    • Hi Praveen. The Essential Enterprise AMI can be switched to any of the supported instance types. M2.4xl isn't one of them.