DCA Hardened Time Series Database for InfluxDB — Support & Quick Start

At a glance

Status	Live on Oracle Cloud Marketplace
Version	2.9.1-1
Platform	Oracle Linux 9
Ports open in the host firewall	SSH (22/tcp), 8086/tcp
Category	Databases
Upstream licence	MIT
Pricing	Pay-as-you-go software fee per OCPU-hour, billed by Oracle on your OCI invoice — see the listing's Pricing tab

Quick start

This is the listing's usage information, verbatim. Every command in it is run by our QA on a freshly launched instance before an image version can publish, so the text and the tested procedure cannot drift apart.

After launch:

1. Connect over SSH as the opc user with the key you supplied at launch:

   ssh opc@PUBLIC_IP

2. InfluxDB runs as a systemd service on port 8086, bound to loopback. First boot created an instance-unique admin account and API token:

   sudo cat /root/.influxdb2_default_credentials

3. Verify the service:

   sudo systemctl status influxdb
   curl http://127.0.0.1:8086/health

4. To reach the UI and API remotely, edit /etc/influxdb/config.toml and change http-bind-address to "0.0.0.0:8086", then:

   sudo systemctl restart influxdb

   (Your VCN security list must also allow TCP 8086 — the instance firewall already does.) Authentication is already enforced; sign in with the credentials from step 2 and rotate the password under Settings.

5. Write and query with any InfluxDB v2 client using the operator token, e.g.:

   curl -H "Authorization: Token YOUR_TOKEN" "http://SERVER_IP:8086/api/v2/buckets"

6. Data lives in /var/lib/influxdb. Attach and mount a block volume there before heavy use if you sized the boot volume small.

The image is CVE-patched at build time. Apply ongoing updates with:

sudo dnf -y update

What the image provides

• InfluxDB 2.9.1 (the fully open MIT-licensed v2 line), installed from InfluxData's official release with its SHA-256 checksum verified at build time, running as a dedicated unprivileged service.
• Zero-touch first boot: the instance onboards itself with an instance-unique administrator account, organization, bucket, and operator API token — no shared secret is baked into the image, and no setup wizard is ever exposed to the network. Credentials are written for the operator to /root/.influxdb2_default_credentials.
• Bound to loopback by default; you expose the API deliberately, after authentication already exists. The UI and API share one declared port (8086).
• A locked-down systemd sandbox (NoNewPrivileges, ProtectSystem, ProtectHome, PrivateTmp) and least-privilege service account.
• Security hardening aligned to the Oracle Cloud Marketplace image standards: SELinux enforcing, host firewall default-deny with only SSH and 8086 permitted, no account with a usable password, no stray keys, and the image fully patched at build time.

Fixed issues

Found by our customer-path QA, fixed in a new image version. Launch the current version for new deployments.

• Fixed in 2.9.1-1 (2026-10-07): On version 2.9.1 the service started influxd with a command-line flag it does not support, so the database never started and first boot could not create the administrator or the API token. 2.9.1-1 also turns off InfluxData usage telemetry.
  On an instance launched from 2.9.1: launch a new instance from version 2.9.1-1 — no data can exist on a 2.9.1 instance, because the database never ran.

Still stuck?

Email support@dcassociatesgroup.com (response within 1 business day) or use the contact form. Include the listing name, your OCI region, the instance OCID and the output of sudo journalctl -u <service> -n 100 for the unit named in the quick start.

InfluxDB is a trademark of InfluxData, Inc. This image is an independent hardened distribution and is not affiliated with, endorsed by, or sponsored by InfluxData.