Skip to content
Vaultwarden Password Manager product logo
  • AWSAvailable on Amazon Web Services
  • Azure· soonComing soon on Microsoft Azure
  • GCP· nextGoogle Cloud is next on the roadmap
Available

Vaultwarden Password Manager

Vaultwarden 1.37.4 password manager server with web vault 2026.7.0 on Ubuntu 24.04 LTS, served over HTTPS with live sync. Keep your team's passwords, secure notes and cards in an end-to-end encrypted vault on a server you control, share logins through organizations and collections, and use the Bitwarden-compatible browser extensions and mobile apps. Sign-ups are closed by default, so only addresses you invite can create an account, and the whole vault backs up with one command.

Version
v1.37.4
Operating system
Ubuntu 24.04 LTS
Architecture
x86_64
Support
Email support

What's installed

Every package and version on the image, identical on every cloud it ships on. Nothing else is installed.

  • Vaultwarden 1.37.4 (built from source)
  • Web vault 2026.7.0
  • nginx 1.24.0
  • SQLite
  • Webmin 2.670

LicensingOpen source (AGPL-3.0), no licence key required

Deploy anywhere

Vaultwarden Password Manager on AWS and Azure.

Google Cloud is next on the roadmap. One clean-room build, one first-boot credential model, one patch cadence — identical on every cloud you run. Every identifier below is the real one; copy it and launch.

  1. AWS
    Available

    Amazon Web Services

    AMI · v1.37.4

    AWS AMI ID

    Shown for your region on the AWS Marketplace launch page once you subscribe.

    Released
    Root volume
    gp3 · 30 GiB
    Instance types
    • t3a.small
    • t3.small
    • t3a.medium
    • m6a.large
    Regions34 regions· show all
    • us-east-1
    • af-south-1
    • ap-east-1
    • ap-east-2
    • ap-northeast-1
    • ap-northeast-2
    • ap-northeast-3
    • ap-south-1
    • ap-south-2
    • ap-southeast-1
    • ap-southeast-2
    • ap-southeast-3
    • ap-southeast-4
    • ap-southeast-5
    • ap-southeast-6
    • ap-southeast-7
    • ca-central-1
    • ca-west-1
    • eu-central-1
    • eu-central-2
    • eu-north-1
    • eu-south-1
    • eu-south-2
    • eu-west-1
    • eu-west-2
    • eu-west-3
    • il-central-1
    • me-central-1
    • me-south-1
    • mx-central-1
    • sa-east-1
    • us-east-2
    • us-west-1
    • us-west-2
    Launch on AWS MarketplaceAWS launch steps

    5-day free trial, then from $0.03/hr software charge (larger instance sizes cost more) plus your own EC2 costs, billed by AWS.

    Subscriptions are open to AWS India (AISPL) accounts. Outside India? Ask us for a private build.

  2. Azure
    Coming soon

    Microsoft Azure

    Compute Gallery image · v1.37

    Azure Compute Gallery image ID
    …/galleries/provencloud_marketplace/images/vaultwarden/versions/2026.11.1
    Released
    OS disk
    Premium_LRS · 30 GiB
    Gallery
    provencloud_marketplace
    Definition
    vaultwarden
    Resource group
    provencloud-marketplace-rg
    VM sizes
    • Standard_D2as_v7
    • Standard_D2as_v5
    • Standard_B2ms
    • Standard_D4as_v7
    Regions50 regions· show all
    • eastus
    • australiacentral
    • australiaeast
    • australiasoutheast
    • austriaeast
    • belgiumcentral
    • brazilsouth
    • canadacentral
    • canadaeast
    • centralindia
    • centralus
    • chilecentral
    • denmarkeast
    • eastasia
    • eastus2
    • francecentral
    • germanywestcentral
    • indiasouthcentral
    • indonesiacentral
    • israelcentral
    • italynorth
    • japaneast
    • japanwest
    • jioindiawest
    • koreacentral
    • koreasouth
    • malaysiawest
    • mexicocentral
    • newzealandnorth
    • northcentralus
    • northeurope
    • norwayeast
    • polandcentral
    • qatarcentral
    • southafricanorth
    • southcentralus
    • southeastasia
    • southindia
    • spaincentral
    • swedencentral
    • switzerlandnorth
    • uaenorth
    • uksouth
    • ukwest
    • westcentralus
    • westeurope
    • westindia
    • westus
    • westus2
    • westus3
    Azure launch steps
AWS

Getting started on Amazon Web Services

From launch to signed in, step by step.

  1. Subscribe on AWS Marketplace and launch in your region with TCP 22, 80, 443 and 8000 open; wait about three minutes for first boot.

  2. Open https://<instance-public-ip>/admin, accept the one-time self-signed certificate warning and enter your EC2 Instance ID, lowercase exactly as the console shows it (for example i-0123456789abcdef0) as the admin token.

  3. On the Users page, invite the email address you want to use (no mail server is needed), then open https://<instance-public-ip>/, choose Create account and register with that address. Uninvited addresses cannot register.

  4. In the apps and browser extensions choose the self-hosted server option and enter https://<instance-public-ip>. Some mobile and desktop apps refuse a self-signed certificate: point your own domain at the instance and install a trusted certificate for those.

  5. Webmin is on port 8000 with username admin and the same Instance ID password. SSH as ubuntu with your key pair. Change the admin token with sudo bash /home/ubuntu/iscripts/pass_vw_admin.sh or Webmin with pass_webmin.sh; back up the vault with sudo bash /home/ubuntu/iscripts/vaultwarden_backup.sh.

Security posture

What this AWS image does and does not ship with, one fact per line.

  • Clean-room build on Canonical's official Ubuntu 24.04 LTS image: every component comes from its own official source, and nothing is copied from any third-party image.

  • Vaultwarden is compiled from its official release tag and the web vault is the checksum-verified build that release pins.

  • The image ships an empty data folder and no credentials: on first boot every instance creates its own vault database, server signing key, admin token (stored only as an Argon2id hash) and HTTPS certificate, and sets its own Webmin password, from EC2 instance metadata (IMDSv2).

  • Sign-ups are closed and invitations are required.

  • The vault is served over HTTPS only (port 80 redirects), and Vaultwarden runs as its own unprivileged user behind nginx.

  • SSH is key-only, and build-time SSH keys, host keys, machine ID, shell history and logs were removed before imaging.

  • The bundled password tools enforce at least 10 characters with upper- and lower-case letters, a number and a symbol.

  • Vaultwarden is an independent project, not associated with Bitwarden, Inc.

Azure

Getting started on Microsoft Azure

From launch to signed in, step by step.

  1. Create the VM from the Azure Marketplace listing with TCP 22, 80, 443 and 8000 open in your network security group. Choose ubuntu as the administrator username so SSH and the script paths match, and wait a few minutes for first boot to finish.

  2. Open https://<vm-public-ip>/admin (the first certificate is self-signed, so your browser shows a warning). The admin token is your VM ID (Azure portal > the virtual machine > Properties > VM ID, for example 02aab8a4-74ef-476e-8182-f6d2ba4166a6). From the admin page invite your first users; they create their own vault passwords. Webmin (port 8000, user admin) uses the same VM ID. Add your own domain and a trusted certificate before you share it with your team.

  3. For production, limit admin ports to your own IP address.

Security posture

What this Azure image does and does not ship with, one fact per line.

  • Clean-room build on Canonical's official Ubuntu 24.04 LTS image from the Azure Marketplace: every component comes from its own official source and no third-party image was launched or copied.

  • No two VMs share a login: first boot sets every password and secret key from the new VM's own vmId (read from Azure IMDS) or from fresh random values, and creates new SSH host keys.

  • The ubuntu login account ships password-locked with an empty authorized_keys, and Azure installs your own SSH key at deploy time.

  • Shell history, logs and cloud-init state are cleared before capture, and the image carries every Ubuntu 24.04 LTS security update with nothing pending.

  • Each gallery version is deployed as a Trusted Launch VM and checked against Microsoft's documented Linux certification test cases, the product's own end-to-end login tests and a stop/start cycle before it is published.

  • Restrict port 22 and the admin consoles to trusted IP ranges, and put public web consoles behind HTTPS with your own certificate.