AWS Graviton Support

As of MarkLogic 11.3.4, Amazon EC2 instances powered by AWS Graviton processors are now supported for running MarkLogic 11. AWS Graviton processors are based on the ARM architecture and are optimized to provide the best price-performance on AWS. New MarkLogic Server AMIs running on AWS Graviton architecture are now available on the AWS Marketplace, and the MarkLogic CloudFormation template has been updated to allow selection of AWS Graviton as the architecture. See MarkLogic on Amazon Web Services for additional details.

AWS Graviton support

MarkLogic 11.3.4 adds support for AWS Graviton2, AWS Graviton3, and AWS Graviton4 EC2 instance types. Here is a breakdown of the newly supported EC2 instance types:

• t4g
• c6g, c6gd, c6gn, c7g, c7gd, c7gn, c8g, c8gd, c8gn, c8gb
• m6g, m6gd, m7g, m7gd, m8g, m8gd, m8gn, m8gb
• r6g, r6gd, r7g, r7gd, r8g, r8gd, r8gn, r8gb
• x8g, i8g, i8ge

Compatibility

EC2 instances using AWS Graviton processors are limited to the Amazon Linux 2023 and RHEL 9 (or compatible) operating systems.

The on‑disk and network formats used by MarkLogic Server are not compatible between x86 (Intel) and ARM (AWS Graviton) architectures:

• You cannot directly reuse or mount forests created on x86 nodes on AWS Graviton nodes—or vice versa.

• Mixing x86 and AWS Graviton nodes within the same cluster is not supported across architectures.

• Relying on physical copy methods (like copying forest directories) is not supported across architectures.

• Backups generated using one architecture cannot be loaded into a cluster with a different architecture.

Migrating to an AWS Graviton-powered EC2 cluster

Migrating an existing MarkLogic Server deployment to a new cluster running on AWS Graviton‑based EC2 instances can vary significantly depending on your environment, operational practices, and data movement requirements.

Due to the cross-architectural incompatibilities between x86 and ARM, migration involves creating a new MarkLogic Server cluster on AWS Graviton, installing the supported MarkLogic Server release, and configuring the new environment with the previous system's settings.

After deploying the new cluster, you can typically continue using the data‑movement or deployment tools already in your environment—like MarkLogic Flux—to populate the new system and prepare it for production.

Since every deployment differs in topology, security configuration, application architecture, and operational processes, you must adapt the specific migration workflow and cutover strategy to your organization’s requirements.

Unsupported features

MarkLogic 11.3.4 on AWS Graviton does not support the following features:

No SSL FIPS support

MarkLogic 11.3.4 on AWS Graviton does not support FIPS mode. So, the Admin Interface disables all options related to SSL FIPS, while related Admin API functions and the Management REST API report that SSL FIPS is not supported.

MarkLogic 11.3.4 on AWS Graviton still uses OpenSSL for encryption, but not in FIPS mode.

No ODBC driver

There are currently no plans to release an AWS Graviton build of the ODBC Driver RPM. However, the x64 build of the ODBC driver can interact with a MarkLogic 11.3.4 on AWS Graviton cluster.

No MarkLogic Converters package

The MarkLogic Converters package is not included in MarkLogic 11.3.4 on AWS Graviton. Support for MarkLogic Converters on the AWS Graviton build is being investigated for a future release of MarkLogic Server.