Overview
This AMI runs NetBox, the open-source infrastructure resource modeling (IPAM and DCIM) application, with PostgreSQL 17 and two Valkey instances on Ubuntu 24.04 LTS. The container image is the community netbox-docker project's netboxcommunity/netbox image, pinned to NetBox 4.7.4 (image release v4.7.4-5.1.1), with PostgreSQL 17.11 and Valkey 9.1.3, baked into the AMI so first start does not depend on a registry. That image is maintained by the netbox-docker community, not by NetBox Labs. NetBox is an independent open-source project and Perimattic is not affiliated with it; NetBox is a trademark of its owner and other product names are trademarks of their respective owners.
Why NetBox?
NetBox is a source of truth for network and data centre infrastructure: IP address management (prefixes, VRFs, VLANs), sites, racks, devices, cables, circuits, virtualization, with a REST and GraphQL API, custom fields, webhooks, scripts and reports.
What Perimattic adds
Superuser created for you, nothing readable anonymously: during first-login setup a random 24-character password is generated on your server and the superuser, using the email you enter, is created by NetBox's own initialisation before the site is published, with the password given to that one command only. LOGIN_REQUIRED is on, so no data is visible without logging in; NetBox has no public registration. Setup then checks that the password works, that a wrong password and anonymous web and API requests are refused and that exactly one account exists. The secret key and API token pepper (64 characters each), the database password and both Valkey passwords are generated per instance. There are no default or shared credentials in the image.
HTTPS: Apache is configured as a reverse proxy and a free Let's Encrypt certificate is requested for your domain with certbot. NetBox serves only your domain name (ALLOWED_HOSTS) and listens only on the loopback interface; PostgreSQL and both Valkey instances are password protected and reachable only inside the Docker network. The anonymous census, release check, Copilot button and metrics endpoint are off.
Patched base: Ubuntu 24.04 LTS built through an automated EC2 Image Builder pipeline, with security updates applied at build time.
Limits you should know
No mail server is configured; set the EMAIL_* variables in /opt/app/docker-compose.yml if you want NetBox to send email. The first login runs NetBox's database migrations and takes eight to nine minutes (475 to 562 seconds in our tests); later starts take about a minute.
NetBox runs five containers (web, background worker, PostgreSQL and two Valkey instances). In our tests they used about 0.95 GB and the instance about 1.4 to 1.5 GB in use. It also ran on a t3.small (2 GB), but with only about 500 MB free, so a t3.medium (4 GB) is the recommended size. The web server runs two worker processes; raise GRANIAN_WORKERS in /opt/app/.env for more concurrency on a larger instance.
Licence
NetBox and the netbox-docker project are released under the Apache License 2.0; this AMI runs the unmodified community 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
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
- NetBox 4.7.4 (Apache-2.0) with PostgreSQL 17.11 and Valkey 9.1.3, pinned and pre-installed: IPAM and DCIM source of truth on your own server. Community netbox-docker image.
- Secure first login: a random 24-character superuser password is generated and the account created before the site is published; nothing readable without logging in; HTTPS through Apache and Let's Encrypt.
- Built on patched Ubuntu 24.04 LTS 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: NetBox 4.7.4 (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 superuser password is generated at first login and given only to NetBox's one-time initialisation, which creates the superuser before the site is published; LOGIN_REQUIRED is on; setup verifies that the password works, that a wrong password and anonymous web and API requests are refused and that exactly one account exists.
- Application: NetBox 4.7.4 from the community netbox-docker image netboxcommunity/netbox v4.7.4-5.1.1 (Apache-2.0, unmodified), with PostgreSQL 17.11 and Valkey 9.1.3 (all pinned). The image is maintained by the netbox-docker community, not NetBox Labs. Secret key and API token pepper are generated per instance.
- ALLOWED_HOSTS is the buyer's domain; census reporting, release check, Copilot and metrics are off. No SMTP is configured.
- Database and Valkey: password protected, reachable only inside the Docker network.
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 size. NetBox runs five containers: in our tests they used about 0.95 GB and the instance about 1.4 to 1.5 GB in use (a t3.small ran with about 500 MB free). The first login runs database migrations and takes eight to nine minutes.
-
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 NetBox
-
Point a domain at the instance
Create a DNS A record (for example netbox.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 and the database, cache, secret key and API token pepper on your server
- Starts PostgreSQL and Valkey, runs NetBox's migrations (eight to nine minutes) and creates the superuser
- Starts NetBox and its worker and checks that the password works, that a wrong password and anonymous web and API requests are refused and that exactly one account exists
- 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 NetBox
Open https://<your-domain> and sign in as admin with the generated password (view it again with: sudo cat /opt/app/access.txt). Nothing is readable without logging in. Create API tokens under your user menu.
-
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
Data is in the PostgreSQL database in /opt/app/postgres, uploads in /opt/app/media, scripts and reports in /opt/app/scripts and /opt/app/reports: back up all of /opt/app or snapshot the volume before upgrades, and keep SECRET_KEY and API_TOKEN_PEPPER_1 from /opt/app/.env with the backup. Only your domain name is accepted (ALLOWED_HOSTS). The container image is the community netbox-docker project's, not an image from NetBox Labs. No mail server is configured: set the EMAIL_* variables in /opt/app/docker-compose.yml to enable email.
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.