Skip to content
ownCloud File Sync and Share product logo
  • AWSAvailable on Amazon Web Services
  • AzureAvailable on Microsoft Azure
  • GCP· nextGoogle Cloud is next on the roadmap
Available

ownCloud File Sync and Share

ownCloud Server 10.16.3 with phpMyAdmin and Webmin on Ubuntu 24.04 LTS - file sync and share on your own instance, ready to sign in minutes after launch. Redis handles caching and file locking, background jobs run from cron, WebDAV works with the desktop and mobile clients, and the data directory sits outside the web root. A small service keeps the trusted domain correct if your IP changes.

Version
v10.16.3
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.

  • ownCloud Server 10.16.3
  • phpMyAdmin 5.2.3
  • Webmin 2.660
  • Apache 2.4.58
  • PHP 7.4.33
  • MySQL 8.0.46
  • Redis 7.0.15

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

Deploy anywhere

ownCloud File Sync and Share 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 · v10.16.3

    AWS AMI ID

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

    Released
    Root volume
    gp3 · 8 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.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
    Available

    Microsoft Azure

    Compute Gallery image · v10.16.3 (build 20260522)

    Azure Compute Gallery image ID

    Selected for you when you create the VM from the Azure Marketplace listing.

    Released
    OS disk
    Premium_LRS · 30 GiB
    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
    Launch on Azure MarketplaceAzure 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 and 8000 open; wait two to three minutes for first boot.

  2. Open http://<instance-public-ip>/ for a launcher page linking each console. ownCloud: /owncloud (username admin). phpMyAdmin: /phpmyadmin (username root). Webmin: port 8000 (username admin). The password for all three is your EC2 Instance ID, lowercase exactly as the console shows it (for example i-0123456789abcdef0).

  3. Desktop and mobile sync clients connect at http://<instance-public-ip>/owncloud over WebDAV.

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

  5. A stop/start that changes your public IP re-points ownCloud's trusted domain within seconds; set your own hostname and it is left alone. The image is HTTP-only - put your certificate or load balancer in front.

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 AMI; every component comes from its official source and nothing is copied from any third-party image.

  • No credentials ship in the AMI: the ownCloud admin, MySQL root and Webmin admin passwords are generated on your instance at first boot from EC2 instance metadata (IMDSv2), and the scripts that set them delete themselves afterwards.

  • The phpMyAdmin cookie encryption key is regenerated per instance too.

  • The ownCloud data directory lives outside the web root with Apache denying direct access, directory listing is off, and MySQL and Redis listen only on 127.0.0.1.

  • SSH is key-only; build-time SSH keys, shell history and logs were removed before the image was captured.

  • The bundled password tools enforce at least 10 characters with upper- and lower-case letters, a number and a symbol. ownCloud's built-in security and setup check reports 'All checks passed'. ownCloud 10.x requires PHP 7.4, which is supplied from the Ondřej Surý PPA build for Ubuntu 24.04 rather than an unsupported distro package.

  • The image is HTTP-only by design: terminate TLS at a load balancer or add a certificate to Apache before exposing it 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 and 8000 open in your network security group. Choose ubuntu as the administrator username so SSH and the script paths match. Wait about three minutes for first boot.

  2. Open http://<vm-public-ip>/owncloud and sign in as admin - http://<vm-public-ip>/ is a landing page that links to each console. phpMyAdmin is at /phpmyadmin (username root) and Webmin on port 8000 (username admin or root).

  3. The password is your VM ID: in the Azure portal open the virtual machine, choose Properties and copy VM ID - a 36-character value such as 02aab8a4-74ef-476e-8182-f6d2ba4166a6, typed exactly as shown in lower case.

  4. Your files live in /var/www/owncloud-data, outside the web root. SSH as ubuntu with your key and change passwords with sudo bash ~/iscripts/pass_owncloud.sh, pass_mysql.sh or pass_webmin.sh.

Security posture

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

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

  • The ownCloud administrator, MySQL root and Webmin passwords are all set on first boot from your VM's own vmId.

  • The data directory is outside the web root and Redis is loopback only.

  • The pre-image cleanup proves the build's own credentials are rejected before capture, and first boot sets every password from the new VM's own vmId, read from Azure IMDS.

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

  • Shell history, logs and cloud-init state are cleared before capture.

  • Verified against Microsoft's documented Linux certification test cases on a VM deployed from this gallery version - 13 passed, 0 failures - with VM extension provisioning confirmed and every helper script executed rather than only reviewed.

  • Restrict port 22 to trusted IP ranges, and put the consoles behind HTTPS with your own certificate before exposing them to the internet.