Back to the registry
Agent passport

InfluxDB - Hardened Self-Hosted Time Series Database

Lynxroute · Cybersecurity & IT

No attestation published

Certification per AWS Marketplace.

Provenance reach4 of 12 layers traced

Evidence tier Source Confirmed · 4 captures on record

User ratingNot rated0 reviews on the listing
Runs onUnknownVirtual machine
ProvenanceUnknown44% of the provenance layers this product can disclose
Evidence riskHighSign in to see the basis for this band.

What the publisher says

As described on AWS Marketplace.

This is a repackaged software product wherein additional charges apply for hardening, security configuration, and support.

WHAT IS INFLUXDB

Show the rest of the publisher’s description (17 more lines)

InfluxDB is an open-source time series database purpose-built for high write and query loads on timestamped data - infrastructure and application metrics, application events, IoT and sensor telemetry, and real-time analytics. This AMI ships the 2.x line: a single Go server (influxd) with a built-in web UI, a token-authenticated HTTP API on port 8086, and two query languages - Flux and InfluxQL. Features include unbounded retention policies, downsampling tasks, dashboards, alerting checks, and the line-protocol write API compatible with Telegraf and the broad InfluxData client ecosystem (Go, Python, JavaScript, Java, and more). Data persists to a local bolt metadata store and TSM storage engine under a dedicated data directory. MIT license, no vendor lock-in - distinct from the managed InfluxDB Cloud service.

WHAT THIS AMI ADDS

Security hardening:

  • Native TLS on port 8086 - a per-instance self-signed certificate is generated at first boot (no shared key baked into the image); swap in your own CA certificate anytime
  • Admin user, password, and an all-access operator token generated at first boot - written to /root/influxdb-credentials.txt (readable only by root)
  • Usage telemetry disabled
  • HTTP API and web UI require token / login authentication; unauthenticated API calls are refused
  • UFW firewall - SSH on 22 and InfluxDB on 8086 only
  • fail2ban, AppArmor
  • 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
  • auditd, SSH hardening, Kernel hardening, IMDSv2 enforced

Compliance artifacts:

  • SBOM - CycloneDX 1.6 at /etc/lynxroute/sbom.json
  • CIS Conformance Report at /etc/lynxroute/cis-report.html
  • CIS Tailored Profile at /usr/share/doc/lynxroute/CIS_TAILORED_PROFILE.md

Highlights

Highlighted by the publisher on AWS Marketplace.

InfluxDB security baked in: native TLS with a per-instance self-signed certificate generated at first boot, admin user + password + all-access operator token created at first boot, usage telemetry disabled - unlike bare InfluxDB AMIs that serve plaintext HTTP, sit on an unconfigured setup screen, and phone home telemetry by default.

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.

Self-hosted time series database for metrics, events, and IoT data: built-in Flux and InfluxQL, web UI and HTTP API on port 8086, unbounded retention. MIT license - fully auditable, no vendor lock-in.

Agent build and provenance

See the full provenance

The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.

Compliance

Government
  • FedRAMPConfirmedNot listed90%, registry-checkedNo FedRAMP Marketplace entry matched this vendor's domain, checked 2026-08-27registry recordas observed 2026-08-27

Confirmed means matched to a public authoritative registry. Claimed means the vendor or its listing states it, not yet cross-checked. A framework not shown was not found in any source we hold, which is not evidence against it. Not listed means a scoped registry check found no match for this vendor's domain: a No is a scoped registry check, not a compliance judgment. Confidence bands: 95% domain-verified, 90% registry-checked, 80% self-attested, 70% weak signal. Self-attested items marked “vendor's site” are gathered from the vendor's own website and are not verified by us.

Vendor

External enrichment · as of 2026-08-29

CompanyLynxrouteAutomated
IndustryTechnologyAutomated
Websitehttps://lynxroute.com/

Plans and pricing as listed

5 listed
t3.medium
  • Hrs
$0.05
m6i.large
  • Hrs
$0.05
m6i.xlarge
  • Hrs
$0.05
t3.large
  • Hrs
$0.05
t3.small
  • Hrs
$0.03

Refund terms

As stated by the publisher on AWS Marketplace.

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.

Sources

Marketplace listingaws.amazon.comSource
App certificationaws.amazon.comSource
StandardEulaStandardEulaSource

Publisher resources

1 link
Documenationdocs.influxdata.comSource

Linked repositories

1 repo
influxdata/influxdbgithub · AWS MarketplaceSource

Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.

Pricing
Paid
5 plans listed
Delivery
Virtual machine
Lynxroute is not affiliated with InfluxData Inc. - this AMI packages the MIT-licensed open-source InfluxDB 2.x distribution as a self-hosted EC2 service (distinct from the managed InfluxDB Cloud offering). "InfluxDB" is a trademark of InfluxData Inc. Visit us online: https://lynxroute.com For InfluxDB documentation: https://docs.influxdata.com/influxdb/v2/ For InfluxDB upstream issues: https://github.com/influxdata/influxdb/issues
Open the source listing ↗

Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.