Skip to content
Apache Guacamole Remote Desktop product logo
  • AWSAvailable on Amazon Web Services
  • Azure· soonComing soon on Microsoft Azure
  • GCP· nextGoogle Cloud is next on the roadmap
Available

Apache Guacamole Remote Desktop

Apache Guacamole 1.6.0 remote desktop gateway with PostgreSQL and Webmin on Ubuntu 24.04 LTS. Open Windows desktops, Linux desktops and server terminals over RDP, VNC and SSH from any web browser, with no client software to install and no RDP or SSH ports opened to the internet on the machines you reach. Add each connection once, then your team opens it from a browser tab with copy and paste, file transfer and per-user access control. Guacamole is a gateway, not a desktop: point it at the machines you already run.

Version
v1.6.0
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.

  • Apache Guacamole 1.6.0
  • guacd 1.6.0 (built from source)
  • FreeRDP 2.11.5
  • Apache Tomcat 9.0.123
  • OpenJDK 21
  • PostgreSQL 16.15
  • nginx 1.24.0
  • Webmin 2.670

LicensingOpen source (Apache-2.0), no licence key required

Deploy anywhere

Apache Guacamole Remote Desktop 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.6.0

    AWS AMI ID

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

    Released
    Root volume
    gp3 · 20 GiB
    Instance types
    • t3a.medium
    • t3.medium
    • t3a.large
    • 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.04/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.6

    Azure Compute Gallery image ID
    …/galleries/provencloud_marketplace/images/guacamole/versions/2026.11.1
    Released
    OS disk
    Premium_LRS · 30 GiB
    Gallery
    provencloud_marketplace
    Definition
    guacamole
    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 five minutes for first boot.

  2. Open http://<instance-public-ip>/ (or https://, accepting the one-time self-signed certificate warning) and sign in with username admin and your EC2 Instance ID, lowercase exactly as the console shows it (for example i-0123456789abcdef0). Webmin is on port 8000 with the same username and password.

  3. Add a machine under Settings > Connections > New Connection: pick RDP, VNC or SSH, enter its hostname or IP and port under Parameters > Network, and its credentials under Authentication. Leave the Guacamole proxy (guacd) section empty.

  4. SSH as ubuntu with your key pair. Change passwords with sudo bash /home/ubuntu/iscripts/pass_guacamole.sh, pass_postgres.sh or pass_webmin.sh.

  5. For production, point your own domain at the instance and replace the self-signed certificate with a trusted one. Allow ports 22 and 8000 only from your own IP.

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. guacd is compiled from the official guacamole-server source, and the web application and its PostgreSQL and brute-force-ban extensions are the official Apache releases.

  • No credentials ship in the image: on first boot every instance sets its own Guacamole administrator, PostgreSQL and Webmin passwords from EC2 instance metadata (IMDSv2) and creates its own HTTPS certificate and server keys.

  • PostgreSQL listens only on 127.0.0.1, and repeated failed sign-ins are banned by the auth-ban extension.

  • 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.

  • The certificate is self-signed: replace it with a trusted one before exposing the gateway publicly, and restrict ports 22 and 8000 to trusted IP ranges in your security group.

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>/ and sign in as admin. The password is your VM ID (Azure portal > the virtual machine > Properties > VM ID, for example 02aab8a4-74ef-476e-8182-f6d2ba4166a6). Webmin (port 8000, user admin) uses the same password. Add a connection under Settings > Connections, then open it from the home screen. Kubernetes connections and video export of session recordings are not included.

  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.