Metadata
- Last Updated: April 14, 2026
- 1 minute read
- MarkLogic Server
- Version 11.0
- Documentation
The Managed Cluster Feature uses an external metadata store (a DynamoDB table) to save the configuration information for the cluster. Whenever a cluster event happens, the metadata store is updated with latest cluster node information to ensure that the cluster remains available and reliable in different kinds of cloud service failure events.
AWSTemplateFormatVersion: 2010-09-09
Description: Deploy a MarkLogic Cluster on AWS with a new VPC
Metadata:
version: 9.0-20180427
binary: MarkLogic-9.0-20180427.x86_64.rpm
AWS::CloudFormation::Interface:
ParameterGroups:
- Label:
default: "Resource Configuration"
Parameters:
- IAMRole
- LogSNS
- VolumeSize
- VolumeType
- InstanceType
- SpotPrice
- KeyName
- NumberOfZones
- NodesPerZone
- AZ
- Label:
default: "Network Configuration"
Parameters:
- VPC
- PublicSubnet1
- PublicSubnet2
- PublicSubnet3
- PrivateSubnet1
- PrivateSubnet2
- PrivateSubnet3
- Label:
default: "MarkLogic Configuration"
Parameters:
- AdminUser
- AdminPass
- Licensee
- LicenseKey
ParameterLabels:
AdminUser:
default: Admin User
AdminPass:
default: Admin Password
Licensee:
default: Licensee
LicenseKey:
default: License Key
IAMRole:
default: IAM Role
LogSNS:
default: Logging SNS ARN
VolumeSize:
default: Volume Size
VolumeType:
default: Volume Type
InstanceType:
default: Instance Type
SpotPrice:
default: Spot Price
KeyName:
default: SSH Key Name
NumberOfZones:
default: Number of Zones
NodesPerZone:
default: Nodes per Zone
AZ:
default: Availability Zone
VPC:
default: VPC
PublicSubnet1:
default: Public Subnet 1
PublicSubnet2:
default: Public Subnet 2
PublicSubnet3:
default: Public Subnet 3
PrivateSubnet1:
default: Private Subnet 1
PrivateSubnet2:
default: Private Subnet 2
PrivateSubnet3:
default: Private Subnet 3