Overview
This is a repackaged software product wherein additional charges apply for hardening, security configuration, and support.
WHAT IS OPENLDAP
OpenLDAP is the reference open-source implementation of the Lightweight Directory Access Protocol and the directory server most self-hosted identity stacks are built on. Its server, slapd, is a single C daemon that stores users, groups, hosts and application entries in a hierarchical tree and answers LDAP queries over the network - the same protocol Linux hosts, VPN concentrators, mail servers, CI systems, wikis and hundreds of off-the-shelf applications already speak for authentication and identity lookup. Storage is LMDB, a memory-mapped transactional store compiled into the server, so there is no separate database process to run, tune or back up. Configuration is live: the whole server is described by entries under cn=config and changed with ordinary LDAP operations, with no restart and no configuration file to edit. Running your own directory keeps every credential, group membership and personnel attribute inside your own AWS account rather than a third-party identity service, which matters directly for GDPR and for sector rules on personal data. OpenLDAP Public License, no vendor lock-in.
WHAT THIS AMI ADDS
Security hardening:
- Anonymous binds refused - the directory does not answer unauthenticated clients at all, and every operation requires an identity
- No cleartext passwords on the wire - a security strength floor is enforced, so port 389 works only after StartTLS and a password bind over an unprotected connection is rejected by the server
- Per-instance TLS certificate and private key, generated on your own instance at first launch and never shipped inside the AMI
- Per-instance administrator password, generated at first launch and written to a root-only file - no shared or default credential exists in the image
- Salted password hashing (SSHA) for every password set through the directory
- Password hashes readable by nobody - the access rules let users change their own password without the right to read it, so a compromised session cannot walk away with a hash to crack offline
- Directory data is not world-readable - the permissive default access rule is replaced, so an authenticated identity is required to read anything
- UFW firewall pre-configured - only 22, 389 and 636 reachable
- fail2ban, AppArmor
- CVE scan - every image is scanned for vulnerabilities before release
OS hardening (CIS Level 1):
- CIS Ubuntu 24.04 LTS Level 1 benchmark applied via ansible-lockdown
- auditd, SSH hardening, Kernel hardening, IMDSv2 enforced
Compliance artifacts:
- SBOM - CycloneDX 1.6 at /etc/lynxroute/sbom.json
- CIS Conformance Report at /etc/lynxroute/cis-report.html
- CIS Tailored Profile at /usr/share/doc/lynxroute/CIS_TAILORED_PROFILE.md
- Operational audit log - every connection, bind and result recorded to /var/log/openldap/slapd.log
Highlights
- OpenLDAP security baked in: anonymous binds refused, cleartext password binds rejected by the server, per-instance TLS certificate and administrator password generated at first launch, password hashes readable by nobody including their owner.
- CIS Level 1 hardened Ubuntu 24.04 LTS: auditd, fail2ban, AppArmor, SSH key-only, IMDSv2 enforced. CVE-scanned before every release. SBOM (CycloneDX) and CIS Conformance Report included.
- Self-contained directory service: slapd with an embedded LMDB store, no external database, cache or runtime to operate. Configuration is live through cn=config, with no restart and no configuration file to edit. OpenLDAP Public License - fully auditable, no vendor lock-in.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Free trial
Dimension | Cost/hour |
|---|---|
t3.small Recommended | $0.03 |
t3.large | $0.05 |
t3.medium | $0.05 |
m6i.large | $0.05 |
Vendor refund policy
We do not offer refunds for this product. AWS infrastructure charges (EC2, EBS, data transfer) are billed separately by AWS and are not refundable by us.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
OpenLDAP 2.6.13 - Initial release (August 2026)
- OpenLDAP 2.6.13 on Ubuntu 24.04 LTS, built from the official upstream source release with a PGP-verified tarball
- CIS Level 1 hardening applied (ansible-lockdown/UBUNTU24-CIS)
- CVE-scanned before every release
- Anonymous binds refused; every operation requires an authenticated identity
- Cleartext password binds rejected - port 389 requires StartTLS, port 636 is LDAPS
- Per-instance TLS certificate and administrator password generated at first launch
- Salted password hashing (SSHA); password hashes are not readable, not even by their owner
- Embedded LMDB storage sized to 1 GiB - no external database to operate
- UFW firewall pre-configured (ports 22, 389, 636 only)
- fail2ban, auditd, AppArmor pre-configured
- SBOM (CycloneDX 1.6) at /etc/lynxroute/sbom.json
- CIS Conformance Report (OpenSCAP) at /etc/lynxroute/cis-report.html
- IMDSv2 enforced
Additional details
Usage instructions
- Launch instance (t3.small recommended)
- Open Security Group - allow TCP 636 (LDAPS) and TCP 389 (LDAP with StartTLS) from the networks that need to bind, plus TCP 22 from your IP
- SSH: ssh -i key.pem ubuntu@<PUBLIC_IP>
- Read credentials: sudo cat /root/openldap-credentials.txt
- Query the directory from this host: ldapsearch -H ldaps://localhost:636 -D "cn=admin,dc=example,dc=com" -W -b "dc=example,dc=com" -LLL dn
- Query it from a client machine - copy /etc/openldap/certs/slapd-cert.pem to the client, then: LDAPTLS_CACERT=/path/to/slapd-cert.pem ldapsearch -H ldaps://<PUBLIC_IP>:636 -D "cn=admin,dc=example,dc=com" -W -b "dc=example,dc=com" -LLL dn
- Change any server setting live, with no restart: sudo ldapmodify -Y EXTERNAL -H ldapi:///
The administrator password is generated at first launch and saved to /root/openldap-credentials.txt.
Port 389 requires StartTLS and port 636 is LDAPS - a plain unencrypted bind is refused by design, and anonymous binds are refused entirely. A client that reports "confidentiality required" is being told to use TLS, not that the port is broken.
The TLS certificate is self-signed and generated on your instance. Clients must trust it explicitly, or you can point the server at your own PKI by replacing three cn=config attributes - the exact command is in the credentials file.
The default directory suffix is dc=example,dc=com. To use your own domain, write it to /etc/lynxroute/openldap-domain before the first launch (cloud-init write_files does this cleanly); the suffix, the administrator DN and the client defaults are all derived from it. Changing it afterwards means exporting with slapcat, editing the DNs and reloading.
Back up the directory with: sudo slapcat -n 1 -l backup.ldif (data) and sudo slapcat -n 0 -l config.ldif (configuration).
Resources
Vendor resources
Support
Vendor support
Visit us online: https://lynxroute.com
For OpenLDAP documentation:
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products
