This product has charges associated with it for hardening, security configuration, and support.
NetBox is the open-source source of truth for network and data centre infrastructure, combining DCIM and IPAM in one Django application served by gunicorn behind nginx, with PostgreSQL for data and Valkey for caching and background jobs. This Lynxroute build is hardened and ready out of the box: every secret generated at first boot, HTTPS enabled by default with Certbot pre-installed, PostgreSQL and Valkey bound to loopback only, no outbound calls to third-party services, UFW firewall pre-configured, and a CIS Level 1 hardened Ubuntu 24.04 LTS base.
Apache-2.0 license - fully auditable, no vendor lock-in.
This is a repackaged software product wherein additional charges apply for hardening, security configuration, and support.
WHAT IS NETBOX
NetBox is the open-source source of truth for network and data centre infrastructure, combining DCIM (data centre infrastructure management) and IPAM (IP address management) in a single data model. It is a Django application written in Python, served by gunicorn behind nginx, persisting everything in PostgreSQL and using Valkey for caching and background job queues. It models sites, racks, devices, modules, cables and power feeds alongside prefixes, IP ranges, addresses, VLANs, VRFs and ASNs, plus circuits, wireless links, VPN tunnels and virtual machines. A documented REST API and a GraphQL endpoint make it the system of record that drives automation - Ansible, Terraform and NAPALM all read inventory from it. Custom fields, custom validation rules, config templates, journaling and a full change log let you model your own estate. Apache-2.0 license, no vendor lock-in.
WHAT THIS AMI ADDS
Security hardening:
Every secret generated at first boot on your own instance - the Django SECRET_KEY, the API token pepper, the PostgreSQL password, the Valkey password and the administrator password. Nothing is baked into the AMI
HTTPS enabled by default - nginx terminates TLS on 443 with a self-signed certificate and redirects port 80; Certbot and the nginx plugin are pre-installed so a trusted certificate is one command away
Session and CSRF cookies marked Secure, and the application is configured to trust the TLS proxy in front of it
PostgreSQL and Valkey bound to 127.0.0.1 only and never exposed; Valkey additionally requires a generated password
No outbound calls to third-party services - isolated deployment mode is enabled, so the instance sends no usage census, no release check and no remote catalogue lookups. One line of configuration reverses it if you prefer the upstream defaults
UFW firewall pre-configured - only 22, 80 and 443 reachable; database and cache ports blocked externally
fail2ban, auditd and AppArmor pre-configured
CVE scan - every image is scanned for vulnerabilities before release
OS hardening (CIS Level 1):
CIS Ubuntu 24.04 LTS Level 1 benchmark applied via ansible-lockdown
CIS Conformance Report at /etc/lynxroute/cis-report.html
CIS Tailored Profile at /usr/share/doc/lynxroute/CIS_TAILORED_PROFILE.md
The complete NetBox manual is built into the AMI and served from the instance itself, so it works on an isolated network with no internet access.
Highlights
NetBox security baked in: the Django SECRET_KEY, API token pepper, database password, cache password and administrator password are all generated at first boot on your instance, HTTPS enabled by default with Certbot pre-installed, PostgreSQL and Valkey bound to loopback only, no outbound calls to third-party services.
CIS Level 1 hardened Ubuntu 24.04 LTS: auditd, fail2ban, AppArmor, SSH key-only, IMDSv2 enforced. CVE-scanned before every release. SBOM (CycloneDX) and CIS Conformance Report included.
The source of truth your automation reads: DCIM and IPAM in one model, documented REST and GraphQL APIs, custom fields, config templates and a full change log. Apache-2.0 license - fully auditable, no vendor lock-in.
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Try this product free for 5 days according to the free trial terms set by the vendor. Usage-based pricing is in effect for usage beyond the free trial terms. Your free trial gets automatically converted to a paid subscription when the trial ends, but may be canceled any time before that.
You pay by the hour for the EC2 instance size you run. The four options map to AWS instance types, not feature tiers. The t3.medium and t3.large use burstable general-purpose instances, with t3.large carrying more compute and memory. The m6i.large and m6i.xlarge use fixed-performance general-purpose instances, with m6i.xlarge carrying more compute and memory. Every option ships the same hardened image, so your choice reflects the compute and memory you need. Billing runs on usage, so you pay only for the hours each instance runs.
Top-of-mind questions for buyers
What do I actually get for the hourly charge — a full VM or just software access?
Each hourly rate covers a running EC2 instance built from a hardened Ubuntu 24.04 image. The instance ships with the DCIM and IPAM software pre-installed, CIS Level 1 hardening, firewall, and per-instance credentials generated at first boot. You run it inside your own AWS account.
Am I charged when the instance is stopped or paused?
The hourly software charge applies only while the instance is running. Stopped instances do not accrue software fees. However, AWS may still bill for underlying resources like storage attached to a stopped instance. The software meter counts running hours only.
Does moving to a larger instance change my rate for all usage or just new hours?
You are billed per hour at the rate for whichever instance type is running at that time. Switching from t3.medium to m6i.xlarge, for example, changes the rate going forward. Past hours keep the rate that applied when they ran. Changes are manual, not automatic.
lynxroute.com
Helpful?
Vendor refund policy
We do not offer refunds for this product. AWS infrastructure charges (EC2, EBS, data transfer) are billed separately by AWS and are not refundable by us.
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
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.
Django SECRET_KEY, API token pepper, PostgreSQL password, Valkey password and administrator password all generated at first boot - nothing baked into the AMI
HTTPS enabled by default with a self-signed certificate; Certbot and the nginx plugin pre-installed
PostgreSQL and Valkey bound to 127.0.0.1 only; Valkey password-protected
Isolated deployment mode enabled - no outbound calls to third-party services
Complete NetBox manual built into the AMI for offline use
Open https://<PUBLIC_IP>/ in your browser - accept the self-signed certificate warning
Sign in as admin with the password from the credentials file, then change it under the user menu -> Profile -> Change Password
Create an API token under Profile -> API Tokens to drive NetBox from Ansible, Terraform or your own scripts
The instance takes 1-3 minutes to finish initialising on first launch; a loading page is served until NetBox is ready.
Restrict inbound 443 to your own address range until you have signed in and changed the administrator password.
All generated credentials, including the PostgreSQL and Valkey passwords, are saved to /root/netbox-credentials.txt on first launch.
The bundled NetBox manual is served at https://<PUBLIC_IP>/static/docs/ and needs no internet access.
Replace the self-signed TLS certificate with a CA-signed one for production use: sudo certbot --nginx -d yourdomain.com
This instance makes no outbound calls to third-party services. To re-enable the upstream release check and plugin catalogue, set ISOLATED_DEPLOYMENT = False in /opt/netbox/netbox/netbox/configuration.py and run: sudo systemctl restart netbox
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.
This is a repackaged open source software product wherein additional charges apply for technical support. Softwares Included: Ubuntu, Docker and NetBox community edition.
NetBox Community v4.2.6
NetBox is an ideal solution for modeling and documenting modern networks. It acts as a "source of truth" that helps power network automation. This Netbox OSS Image is preconfigured and ready to use.