Listing Thumbnail

    Cosmian KMS - Ubuntu 24.04 (AMD SEV-SNP)

     Info
    Sold by: COSMIAN 
    Deployed on AWS
    This Customer Managed Key Management System has charges associated with the use of the software from UAT to Production and also standard support from Cosmian.

    Overview

    This is a repackaged software wherein additional charges apply for extended support.

    Cosmian kms is a modern, cloud-ready key management system for your encryption keys and certificates, running inside a Cosmian vm - a verifiable and confidential virtual machine.

    This ensures that your KMS remains entirely confidential, at rest and in use, and is verifiable (no hardware of software tampering).

    Cosmian kms delivers unparalleled data security for your organization with an on-the-fly encryption/decryption keys solution, empowering sovereignty, security, and efficiency.

    • Protect your data sovereignty with our independent security solution, eliminating reliance on public cloud providers.

    • Strengthen your security posture by taking charge of sensitive data encryption, including workspace, R&D data, HR information, and electronic communications.

    • Streamline your IT system and server management with automated processes, empowering your system administrators to boost productivity and efficiency in infrastructure management.

    What is in Cosmian kms? Modern lifecycle management for keys and certificates : Cosmian kms offer cutting-edge features for managing encryption keys and certificates throughout their lifecycle.

    • Key storage
    • Key generation
    • Key rotation
    • Key distribution
    • Key usage policies

    Advanced Public Key Infrastructure integration : Integrating seamlessly with external entities, the Cosmian kms facilitates Public Key Infrastructure management beyond the confines of your organization. Whether it's leveraging third-party actors or overseeing key governance, we ensure a streamlined and secure process.

    Embedding standard and modern encryption libraries : Embracing both standard and contemporary cryptographic algorithms, the Cosmian kms boasts an unparalleled breadth of coverage.

    • FIPS 140-3 validated encryption libraries
    • Covercrypt: Post-quantum resistance & access policy
    • Findex: search encryption

    Highlights

    • Advanced Key Management for crypto-agility / Enhanced Data Protection / Zero Trust KMS Strategy / Scalability and Flexibility

    Details

    Sold by

    Categories

    Delivery method

    Delivery option
    64-bit (x86) Amazon Machine Image (AMI)

    Latest version

    Operating system
    Ubuntu 24.04

    Deployed on AWS
    New

    Introducing multi-product solutions

    You can now purchase comprehensive solutions tailored to use cases and industries.

    Multi-product solutions

    Features and programs

    Financing for AWS Marketplace purchases

    AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
    Financing for AWS Marketplace purchases

    Pricing

    Cosmian KMS - Ubuntu 24.04 (AMD SEV-SNP)

     Info
    Pricing is based on actual usage, with charges varying according to how much you consume. Subscriptions have no end date and may be canceled any time. Alternatively, you can pay upfront for a contract, which typically covers your anticipated usage for the contract duration. Any usage beyond contract will incur additional usage-based costs.
    Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator  to estimate your infrastructure costs.

    Usage costs (30)

     Info
    Dimension
    Cost/hour
    c6a.xlarge
    Recommended
    $1.52
    c6a.16xlarge
    $24.32
    r6a.8xlarge
    $12.16
    r6a.2xlarge
    $3.04
    c6a.12xlarge
    $18.24
    c6a.24xlarge
    $36.48
    m6a.8xlarge
    $12.16
    r6a.4xlarge
    $6.08
    c6a.metal
    $72.96
    c6a.48xlarge
    $72.96

    Vendor refund policy

    We apply the standard refund policy from AWS which states that refund can be done directly through AWS within the first 48 hours. After that no refund will be taken into account.

    How can we make this page better?

    We'd like to hear your feedback and ideas on how to improve this page.
    We'd like to hear your feedback and ideas on how to improve this page.

    Legal

    Vendor terms and conditions

    Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .

    Content disclaimer

    Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.

    Usage information

     Info

    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

    [5.17.0] - 2026-02-24

    Features : AWS External Key Store (XKS) v2 Cosmian KMS can now act as an AWS XKS proxy enabling transparent integration with AWS KMS External Key Store: Implements the full XKS Proxy API - a single endpoint that gives AWS KMS live-proxy coverage for all XKS-capable services (S3, EBS, RDS, DynamoDB, Secrets Manager, and more) AWS SigV4 request authentication middleware XKS endpoints: health status, key metadata retrieval, encrypt, decrypt New --xks-* server configuration flags New documentation/docs/aws/xks.md guide Azure External Key Manager (EKM) v0.1-preview Cosmian KMS now implements the Azure EKM proxy API v0.1-preview : Endpoints: info, key metadata, Wrap, Unwrap - faithful to the Azure EKM specification mTLS (mutual TLS) authentication New --azure-ekm-* server configuration flags Flexible versioning structure for future API versions New documentation/docs/azure/ekm/ekm.md guide CLI (ckms) moved into this repository : The cosmian CLI (previously maintained in a separate cli repository) is now co-located in this repository under crate/clients/ckms/: The ckms binary and its full test suite are now built and tested from this repo CLI documentation moved into cli_documentation/ with its own MkDocs configuration Findex server references removed from the CLI documentation and configuration examples Nix packaging extended: nix/cli.nix and nix/common.nix added for building and distributing the CLI as a standalone DEB, RPM, and DMG package Hardcoded system tag strings (e.g. "_sk", "pk") replaced with SYSTEM_TAG* constants from cosmian_kmip::kmip_2_1::extra::tagging WASM and UI test scripts hardened against pnpm major-version mismatches between the system pnpm and the nix-shell pnpm add --header/-H flag and custom_headers config option to forward arbitrary HTTP headers with every request, enabling use behind zero-trust proxies such as Cloudflare Access UI Branding : New loginCardColor field in branding.json to control the login card background color New blank starter theme at ui/public/themes/blank/ with SVG placeholder assets Bug Fixes : Security: KMIP Import with replace_existing=true now verifies the caller owns the existing object before overwriting it Packaging DEB and RPM removal scripts now clean up /usr/sbin/cosmian_kms and /usr/local/cosmian/ on uninstall macOS build retry loop in nix/scripts/package_dmg.sh handles intermittent hdiutil: create failed - Resource busy CI errors Build : Linux packages: README now installed as README.md (was README - not rendered as markdown by package managers) pnpm version pinned to 10 in build_ui.sh Security : ajv updated 6.12.6 -> 6.14.0 (vulnerability fix) minimatch overridden to >=10.2.1 (ReDoS CVE) lru 0.14.0 (transitive via mysql_async 0.36.1): RUSTSEC-2026-0002 acknowledged in deny.toml - no upstream fix available yet; severity low (CVSS 2.7) Documentation : New openssl_override.md: how to point Cosmian KMS to a custom OpenSSL build using a systemd drop-in override New Azure EKM guide (documentation/docs/azure/ekm/ekm.md) New AWS XKS guide (documentation/docs/aws/xks.md) HSM operations: added pkcs11-tool key creation examples and label uniqueness constraint warning UI branding: loginCardColor field reference and blank theme usage README: new Integrations section covering cloud providers (AWS/Azure/GCP), databases, and HSMs

    [5.16.2] - 2026-02-22

    Bug Fixes : [OpenTelemetry] Deduplicate OpenTelemetry export metric (Revoke and Destroy operations) Debug impl of ServerParams was misleading a algorithms restriction Fix non-FIPS openssl.cnf provider configuration: the FIPS provider was incorrectly activated in non-FIPS builds via nix/openssl.nix that now generates distinct provider configurations per build variant: FIPS builds use fips+base, non-FIPS builds use default+legacy+base. Build : Refactor OpenSSL provider management into a dedicated openssl_providers module in crate/server/src/, consolidating safe_openssl_version_info(), init_openssl_providers() (production), and init_openssl_providers_for_tests() (test environments) into a single place. Improve determinism of nix/openssl.nix OpenSSL builds: Patch ENGINESDIR/MODULESDIR in the generated Makefile to fixed /usr/local/cosmian/lib/... paths, preventing Nix store path embedding in compiled libcrypto strings. Set SOURCE_DATE_EPOCH=1 and ZERO_AR_DATE=1 in build and install phases. Normalize all output file timestamps with find $out -exec touch --date=@1 {} +. Non-FIPS Nix Linux builds are now bit-for-bit reproducible (nix-build --check passes for all four Linux variants: FIPS/non-FIPS x static/dynamic OpenSSL): Removed ${toString ../.} from RUSTFLAGS -C remap-path-prefix - it embedded the machine-specific workspace path into the derivation, causing cross-machine hash divergence. Added -C strip=symbols and -C symbol-mangling-version=v0 to strip residual host-path artefacts from symbol tables. Scrub the Nix-store path from OpenSSL's buildinf.h at build time so the OpenSSL derivation hash is identical across machines. Pin all builtins.fetchTarball calls in default.nix with explicit sha256 hashes (nixpkgs 24.11, rust-overlay, nixpkgs 22.05) - eliminates Nix-version-sensitive evaluation impurity and removes the NIXPKGS_GLIBC_234_URL environment variable override. Non-FIPS Docker image now ships OpenSSL 3.6.0 provider modules (legacy.so, openssl.cnf) and sets OPENSSL_CONF/OPENSSL_MODULES environment variables, matching the FIPS image layout. macOS packaging fixes in nix/scripts/package_dmg.sh and related CI scripts. (deps) Bump keccak in the cargo group across 1 directory Documentation : Add mTLS database configuration examples Testing : Add React and WASM tests

    [5.16.1] - 2026-02-15 Bug Fixes : Add MLKEM algorithms to the predefined DEFAULT KMIP policy

    [5.16.0] - 2026-02-04

    Features : Add PQC hybridized KEM support via cosmian_cover_crypt: The Cosmian KMS supports Post-Quantum Cryptography (PQC) hybridized Key Encapsulation Mechanisms (KEM) via the cosmian_cover_crypt crate. This crate provides a configurable KEM framework that can operate in pure classical, pure post-quantum, or hybrid mode by combining a pre-quantum KEM with a post-quantum KEM through a KEM combiner (using SHA-256). Server supports CreateKeyPair for Configurable-KEM and Encrypt/Decrypt encapsulation/decapsulation flows. Add server-side KMIP algorithm policy allowlists (enforcement via kmip.policy_id and [kmip.allowlists]) kmip.policy_id selects a policy (case-insensitive): DEFAULT: built-in conservative allowlists (e.g., SHA-2/3, P-256/P-384/P-521 + Curve25519/448, AEAD/wrapping modes, OAEP/PSS/PKCS5, RSA 3072/4096). CUSTOM: enforce the allowlists you set under [kmip.allowlists]. If kmip.policy_id is unset, the KMIP policy layer is disabled. None vs [] semantics (for each allowlist): None means "no restriction", while an empty list [] means "deny all" when enforcement is enabled. (UI) Runtime branding support via /ui/branding.json (title, theme, and favicon resolved before React renders) Theme asset support under /ui/themes//... with Ant Design token overrides Replace the example theme favicons with neutral, non-Cosmian icons (docs) Add post-install UI branding / theme override guide (paths under /usr/local/cosmian/ui/dist/) (packaging)Include nested UI theme assets in linux packages (recursive dist/**/ globs) (nix) Stage and validate UI dist/ content during packaging (checks index.html, assets/, themes/, branding.json) Bug Fixes : Fix SQL Locate request for OpenTelemetry metrics collector: Refactored SQL Locate query building in locate_query.rs to use bound, typed parameters (LocateQuery + LocateParam) instead of interpolating values into SQL (safer + fixes type/cast handling across SQLite/Postgres/MySQL). Updated the SQL backends to consume the new LocateQuery API: crate/server_database/src/stores/sql/{mysql,pgsql,sqlite}.rs. Improved DB test error context in json_access_test.rs to make failures easier to diagnose. OpenTelemetry wiring updates: mod.rs: add OTEL resource attributes (service name/version + optional environment). otel_metrics.rs: ensure active_keys_count time series exists even when 0. cron.rs: fall back to default username if hsm_admin is empty. Fix regression on KMIP 1.0 (Fresh and InitialDate attributes) Fix Linux packaging smoke tests when the host has /etc/cosmian/kms.toml present by running with an explicit temp config. Make OpenTelemetry export tests resilient under FIPS Nix shells by running curl in a clean environment (avoid inherited OpenSSL/LD overrides). (ui) Azure BYOK export Build : Nix builds now target GLIBC <= 2.34 (Rocky Linux 9 compatibility) by updating pins and building Linux OpenSSL/server outputs against a glibc 2.34 stdenv; server vendor hash expectations are split by static/dynamic on Linux. SBOM generation improvements: .github/scripts/nix.sh sbom strictly validates --target/--variant/--link, defaults to generating all combinations, and supports generating a specific server subset. SBOM tooling runs in an isolated workdir to avoid stray repo-root artifacts, keeps only final sbom.csv + vulns.csv reports per output directory, and deduplicates CVE rows in-place (via nix/scripts/dedup_cves.py, with optional filtering helper nix/scripts/filter_vulns.py). (deps) Bump jsonwebtoken in the cargo group across 1 directory (deps) Bump bytes in the cargo group across 1 directory (deps) Bump time in the cargo group across 1 directory (deps) Bump actix-files in the cargo group across 1 directory Documentation : Update SBOM documentation to match the generator output layout and behavior. Update OpenSSL versions

    [5.15.0] - 2026-01-21

    Features : Upgrade OpenSSL to 3.6.0 but keep 3.1.2 for FIPS crypto provider Provide /health endpoint Add k256 (RFC6979) curve for sign/verify for non-fips builds Download CLI through UI Support RFC 3394 (AESKeyWrap with no padding)

    WARNING about AES Key Wrap changes Any previously manually exported keys in JSON format must be manually updated if they have been previously wrapped with AES. This can be done using the following command:

    sed -i 's/NISTKeyWrap/AESKeyWrapPadding/g' your_exported_key.json Bug Fixes : Remove RUSTSEC-2023-0071 about rsa dependency and handle database without sqlx Summary of changes: openidconnect is removed in favor of manual OIDC implementation jwt-simple is replaced by jsonwebtoken old crate cloudproof_findex has been removed sqlx has been replaced by those crates: tokio-postgres deadpool-postgres mysql_async tokio-rusqlite rusqlite

    WARNING about Redis migration: For KMS server versions less than v5.12, first migrate KMS Redis-Findex database to 5.14 then 5.15. For KMS server versions 5.12 to 5.14, no migration needed to 5.15.

    Fix Docker container issues : Upgrade lru and downgrade yank flat2 to 1.1.5 Fix double hash in RSASSAPSS in raw and digest data mode for sign/verify RSA signature/verify tests only run on non-fips Derive session cookie encryption key from public URL and user-provided salt for load-balanced deployments Documentation : Add MySQL integration doc Update Percona integration doc Add AWS ECS Fargate doc Build : (deps) Bump react-router from 7.5.3 to 7.12.0 in /ui in the npm_and_yarn group across 1 directory

    [5.14.1] - 2025-12-26

    Features : Add IDP multiple audiences configuration on [idp_auth]. Dehardcode kacls-migration audience for Google CSE migration and allow alternative audiences (e.g. for Google Decrypter use)

    WARNING Server TOML configuration - kms.toml: The deprecated [auth] section has been fully removed in favor of [idp_auth]. Usage is:

    ... [idp_auth] jwt_auth_provider = [ "https://accounts.google.com ,https://www.googleapis.com/oauth2/v3/certs ,my-audience,another_client_id", "https://auth0.example.com ,,my-app", "https://keycloak.example.com/auth/realms/myrealm ,,audience_1,audience_2" ] ... Documentation : Publish SBOM and vulnerability reports Improve readme Bug Fixes : Sign and verify for raw and digest data - rfc6979 Allow explicitly AGPL-3.0-or-later license

    Additional details

    Usage instructions

    WARNING : The region east-us1 must not be used to deploy Cosmian products ! It is only present due to an AWS testing constraint but this region does not allow the deployment of confidential VM for the moment.

    Make sure to enable the configuration related to AMD SEV-SNP option located in the advanced details tab within the marketplace deployment page.

    As the Cosmian KMS is deployed on top of a Cosmian Verifiable VM, cosmian_vm_agent starts for the first time, it initializes several components:

    1. It generates a self-signed certificate and sets the CommonName of the certificate to the value of the machine hostname.
    2. It generates a LUKS container (/var/lib/cosmian_vm/container) and mounts it at /var/lib/cosmian_vm/data. Note that /var/lib/cosmian_vm/tmp is a tmpfs. It is encrypted but it should contain only volatile data since it is erased at each VM reboot. Data in this directory is encrypted due to the fact that the RAM is encrypted.
    3. It generates the TPM endorsement keys.

    It is recommended to configure 1. and 2. on your own for production systems.

    The certificate can be changed at will:

    • Edit your DNS register to point to that VM.
    • Create a trusted certificate using the method of your choice (e.g., Let's Encrypt) or use cosmian_certtool.
    • Edit the cosmian_vm_agent configuration file to point to the location of the TLS certificate and private key.

    The LUKS container can be regenerated using cosmian_fstool with your own size and password (to store by yourself in a secure location). It is recommended to use an additional backup disk to store the container. You can skip all these first startup steps by setting COSMIAN_VM_PREINIT=0 when starting cosmian_vm_agent.

    Once the image is instantiated (on GCP, Azure, or AWS), the <code>cosmian_vm_agent</code> automatically starts as a systemd service when the VM boots.

    You can now install any packages or applications you want on the VM.

    Your VM is now set and ready.

    Finally, please follow the deployment process to configure your KMS properly: https://docs.cosmian.com/deployment/cosmian_vm_kms/ 

    Support

    Vendor support

    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

    Customer reviews

    Ratings and reviews

     Info
    0 ratings
    5 star
    4 star
    3 star
    2 star
    1 star
    0%
    0%
    0%
    0%
    0%
    0 reviews
    No customer reviews yet
    Be the first to review this product . We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.