Overview
This AMI runs Nextcloud, the open-source file sync, sharing and collaboration platform, with PostgreSQL 17, Valkey and a cron container on Ubuntu 24.04 LTS. The container images are the official Docker Hub images, pinned to Nextcloud 34.0.5 (Apache variant), PostgreSQL 17.11 and Valkey 9.1.3 and baked into the AMI, so first start does not depend on a registry. Nextcloud is an independent project and Perimattic is not affiliated with it.
Why Nextcloud?
Nextcloud gives you files, folders and sharing under your own control, with desktop, mobile and WebDAV clients, calendars and contacts (CalDAV and CardDAV), comments, versions, a trash bin and many optional apps from the Nextcloud app store.
What Perimattic adds
Secure by default: Nextcloud's setup wizard lets whoever opens a new server first create the administrator. Here Nextcloud's own installer creates the administrator from a random 24-character password generated on your server, before the container serves any request, so the wizard is never exposed. Setup then checks that the password works, that a wrong password, admin/admin and a blank password are refused, that anonymous requests are refused and that the installer cannot create another account. Only your domain is a trusted domain and the proxy settings are configured for Apache. There are no default or shared credentials in the image, and no extra app is enabled for you; public registration does not exist.
Pinned, tested versions: Nextcloud, PostgreSQL and Valkey are fixed to exact tags, not 'latest', so a rebuild never changes the application behind your back. Valkey is used for caching and file locking, protected by its own generated password, and background jobs run from a cron container.
HTTPS: Apache is configured as a reverse proxy with HSTS and a free Let's Encrypt certificate is requested for your domain with certbot. Nextcloud listens only on the loopback interface; PostgreSQL and Valkey are reachable only inside the Docker network.
Patched base: Ubuntu 24.04 LTS built through an automated EC2 Image Builder pipeline, with security updates applied at build time.
Where your files are, and limits
Every user's files are stored under /opt/app/nextcloud/data on the instance's root EBS volume, so choose the volume size for your data, grow it before it fills, and take EBS snapshots for backup. Uploads in the browser are limited to 512 MB; the desktop and mobile clients upload large files in chunks. Email (password reset, notifications) needs an SMTP server that you configure; without it an administrator can set a user's password. The usage-survey and announcements apps are switched off; update checks and the push-notification service still contact nextcloud.com. This is the community edition with no Nextcloud Enterprise subscription or support. Memory use when idle was about about 0.3 GB for Nextcloud, PostgreSQL and Valkey together in our tests (a t3.small, 2 GB, ran fine at idle).
Licence
Nextcloud server is released under the GNU Affero General Public License v3.0 (AGPL-3.0); this AMI runs the unmodified official image. PostgreSQL is released under the PostgreSQL License and Valkey under the BSD 3-Clause licence.
Getting Started Launch the AMI and open ports 22, 80 and 443 in the security group SSH in and answer the setup prompts (domain and admin email) Open https://your-domain and sign in as admin with the password printed at the end of setup Create users, install the apps you need and connect the desktop or mobile client
A domain name with an A record pointing at the instance is required, because the site is served over HTTPS.
This AMI is built and supported by Perimattic.
Book a free setup consultation at https://cal.com/gaurav-pareek-perimattic/marketplace-setup-consultations or email us at aws-support@perimattic.com .
Support Managed and supported by Perimattic, a cloud infrastructure company with 13+ years of experience serving global clients. We offer free setup assistance, custom integrations, infrastructure consulting, and 24/7 support.
Highlights
- Nextcloud 34.0.5 (AGPL-3.0) with PostgreSQL 17.11 and Valkey 9.1.3, pinned and pre-installed: your own file sync and sharing server with calendars and contacts.
- Secure first login: the administrator is created by Nextcloud's installer with a random 24-character password before the container serves any request; the setup wizard is never exposed, only your domain is trusted and anonymous requests are refused.
- Built on patched Ubuntu 24.04 LTS, with HTTPS through Apache and Let's Encrypt, and supported by Perimattic: free setup assistance at aws-support@perimattic.com.
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
- ...
Dimension | Cost/hour |
|---|---|
t3.medium Recommended | $0.03 |
t3.micro | $0.03 |
c3.2xlarge | $0.03 |
c3.4xlarge | $0.03 |
c3.8xlarge | $0.03 |
c3.large | $0.03 |
c3.xlarge | $0.03 |
c4.2xlarge | $0.03 |
c4.4xlarge | $0.03 |
c4.8xlarge | $0.03 |
Vendor refund policy
For any questions or concerns, please contact: Perimattic.com Email: aws-support@perimattic.com
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
Initial release.
- Application: Nextcloud 34.0.5 (container image pinned, baked into the AMI).
- Base: Ubuntu 24.04 LTS, fully patched at build time, built by an automated EC2 Image Builder pipeline.
- TLS: Apache reverse proxy with a Let's Encrypt certificate requested by certbot at first login.
- Credentials are generated on the instance at first login; none are present in the image.
- A random admin password is generated at first login and the administrator is created by Nextcloud's own installer before the container serves any request; setup verifies that a wrong password, admin/admin and a blank password are refused, that anonymous requests are refused and that the installer cannot create another account, before the site is published.
- Application: Nextcloud 34.0.5 (AGPL-3.0, unmodified official image, Apache variant) with PostgreSQL 17.11 and Valkey 9.1.3 (all pinned). Background jobs run from a cron container.
- Database and cache: reachable only inside the Docker network; the cache is password protected.
Additional details
Usage instructions
-
Launch an Instance
From AWS Marketplace, click Continue to Subscribe and then Continue to Configuration to launch the AMI.
-
Choose the Recommended Instance Type
t3.medium (4 GB of memory) is the recommended starting size: Nextcloud, PostgreSQL and Valkey together used about 0.3 GB when idle. A t3.small (2 GB) booted and passed our tests; previews, many users and apps such as office suites need more, so choose t3.large or larger for those. Size the EBS volume for your files.
-
Configure Security Group
Allow inbound traffic on the following ports:
- 22 (SSH) - terminal access for setup
- 80 (HTTP) - needed to validate your domain for the TLS certificate
- 443 (HTTPS) - access to Nextcloud
-
Point a domain at the instance
Create a DNS A record (for example cloud.example.com) pointing to the instance's public IP before you log in.
-
Connect to the Instance
ssh -i <your-key.pem> ubuntu@<public-ip>
-
First-Login Setup
The first SSH login runs a guided setup:
- Prompts for your domain and admin email and checks the DNS A record
- Generates a random 24-character admin password, a database password and a cache password on your server
- Starts Nextcloud, PostgreSQL, Valkey and the cron container; Nextcloud's installer creates the administrator before it serves any request
- Checks that the password works, that a wrong password, admin/admin and a blank password are refused, that anonymous requests are refused and that the installer cannot create another account
- Configures Apache as an HTTPS reverse proxy and requests a Let's Encrypt certificate
- Prints the URL and the admin credentials; they are also stored in /opt/app/access.txt (root only)
If a step fails, fix the problem shown and log in again: the setup resumes where it stopped.
-
Access Nextcloud
Open https://<your-domain> and sign in as admin with the generated password (view it again with: sudo cat /opt/app/access.txt). Create users under Users in the admin menu; there is no public registration.
-
Credentials
Generated on your server, never shared between customers. View them again with:
sudo cat /opt/app/access.txt
-
Manage the Services
cd /opt/app sudo docker compose ps sudo docker compose restart
Files are in /opt/app/nextcloud/data and the database in /opt/app/postgres: size the EBS volume for your data and back up all of /opt/app or snapshot the volume before upgrades. Command line: cd /opt/app && sudo docker compose exec -u www-data nextcloud php occ <command>. Set an SMTP server under Administration settings > Basic settings for password-reset and notification emails.
Thank you for subscribing.
Need Support or Customization? Perimattic's team can help with setup issues, custom features and integrations:
Email us: aws-support@perimattic.com WhatsApp: +91-92142 66896 Learn more: <www.perimattic.com >
We offer free setup assistance, custom development and integrations, and infrastructure consulting.
Resources
Support
Vendor support
Support by Perimattic
Perimattic provides 24/7 support for all AWS Marketplace products. Our team has 13+ years of cloud infrastructure expertise serving global clients.
Contact Channels: Email: aws-support@perimattic.com WhatsApp: +91-92142 66896 Website: <www.perimattic.com >
What We Help With: Initial setup and configuration assistance (free) Troubleshooting connectivity, performance, and backup issues Custom development and integrations Infrastructure consulting and architecture review Migration planning from other solutions Automation solutions and scaling guidance
Instance Sizing Guidance: t2.medium or t3.medium: Development environments, small applications m5.large: Production workloads with moderate traffic m5.xlarge: High-traffic production deployments and larger datasets
For workload-specific sizing recommendations, contact our team for a free consultation.
Refunds and Issues: If you experience any issues or need to request a refund, contact us at aws-support@perimattic.com and we will respond promptly.
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.