Uploaded image for project: 'Libmongocrypt'
  1. Libmongocrypt
  2. MONGOCRYPT-609

Publish libmongocrypt distribution package for Amazon Linux 2023

    • Type: Icon: Task Task
    • Resolution: Works as Designed
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: 1.8.0, 1.9.0, 1.8.1, 1.8.2
    • Component/s: Build
    • Not Needed

      A pre-built distribution package for `libmongocrypt` does not exist yet for Amazon Linux 2023.

      Although platform support for the MongoDB server itself has been added for Amazon Linux 2023 via SERVER-75282, not all projects the Mongo server may depend on support AL2023 yet.

      I discovered from my own situation that deployments of MongoDB that use the Node environment and client-side field-level encryption may fail on EC2 instances running AL2023. Mongo's Node bindings of `libmongocrypt` don't exist during `npm i mongodb-client-encryption`, so `libmongocrypt` must be installed.

      The official documentation does not provide instructions for installing `libmongocrypt` on AL2023 (only AL2013.3 and AL2), and the repositories listed there for any `yum`-based distro don't even exist. All packages available in the usual location are for debian-based systems: https://libmongocrypt.s3.amazonaws.com/

      Therefore we currently must compile this library from source directly on our EC2 instance, which is not desirable for CI deployments.

      Unless I just haven't found the location of the repo and the official docs haven't been updated yet.

      Sources:

      • AL2023 package publication was added as part of the PR coming out of MONGOCRYPT-580
      • This attempt (MONGOCRYPT-600) to install `mongodb-client-encryption` in Alpine fails for the same underlying reason.
      • kevin.albertson@mongodb.com mentions in MONGOCRYPT-416 that Alpine users' best bet is to compile `libmongocrypt` from source, which is also the case for AL2023 (in spite of it using a common Fedora-like flavoured kernel)
      • SERVER-76235 mentions "BUILD-16842" that I cannot access, but that presumably has a better history to the progress being made here, and a message from someone working with the AWS product team asking for a timeline. The link (https://repo.mongodb.com/yum/amazon/) mentioned there does not work for me.

            Assignee:
            roberto.sanchez@mongodb.com Roberto Sanchez
            Reporter:
            gus@ryer.io Angus Ryer
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: