VictoriaLogs Log Database

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

## Store and Search Your Logs in Your Own VPC

VictoriaLogs is a fast, cost efficient database for logs from the VictoriaMetrics team. It ingests structured and plaintext logs over many protocols, stores them compactly on disk, and queries them back with the LogsQL query language through a built in browser UI and HTTP APIs, from a single static Go binary with no external storage dependency. There is no Elasticsearch cluster, no Kibana and no object store to operate: ingestion, indexing and query all live in one process on one instance.

This image delivers VictoriaLogs fully installed as a systemd service, fronted by an authenticating nginx reverse proxy, with log storage on a dedicated EBS volume.

## Who This Is For

Platform and SRE teams who want log storage inside their own VPC rather than a third party SaaS, without running an Elasticsearch plus Kibana cluster to do it. Application teams shipping logs from Loki, Fluent Bit, Vector, an OpenTelemetry Collector or syslog who need an endpoint to point at on day one. Observability owners replacing a multi node log backend with a single instance appliance.

## Application Stack

• VictoriaLogs 1.52.0 single static Go binary, run by a dedicated non login system account
• nginx reverse proxy on port 80, the only public listener, enforcing HTTP Basic Auth
• Multi protocol log ingestion under /insert/ (its own JSON stream, Loki push, Elasticsearch bulk, OpenTelemetry, syslog)
• The LogsQL query API at /select/logsql/query and the built in log explorer UI at /select/vmui/
• Log storage on a dedicated 32 GiB EBS volume, independently resizable and separate from the OS disk

## Secure By Default

VictoriaLogs, like every component in the VictoriaMetrics family, ships with no authentication of its own. For a log store that matters twice over: an open ingest endpoint lets anyone poison the store, and an open query endpoint leaks every log line in it, including hostnames, URLs, user identifiers, tokens and internal topology. This image therefore never gives the database a public listener.

• VictoriaLogs binds to loopback 127.0.0.1 only and is reachable solely through nginx
• Both the ingest path and the query paths sit behind the same HTTP Basic Auth gate
• A unique 24 character password is generated on first boot, bcrypt hashed into the nginx credential file and written to a root only file
• The image ships with an empty credential file, so no usable password exists in it and every login against the unbooted image is rejected
• The only unauthenticated route is a static health endpoint that never touches the database

## Getting Started

1. Launch the AMI, opening port 80 in your security group alongside SSH

2. SSH in and read the generated password: sudo cat /root/victorialogs-credentials.txt

3. Open http:///select/vmui/ and sign in as admin to search stored logs with LogsQL

4. Ship logs to http:///insert/ from Loki, Fluent Bit, Vector, an OpenTelemetry Collector or syslog using the same credentials

5. Query logs programmatically at /select/logsql/query

6. Verify the appliance end to end at any time: sudo /usr/local/sbin/victorialogs-selftest.sh

## Retention and Sizing

Log retention defaults to 30 days, and storage is capped at 80 percent of the data volume so a log burst cannot fill the disk and wedge the service. Both are single flag settings the user guide explains how to change. Size the volume against your ingest rate.

## 24/7 cloudimg Support

Every deployment is backed by cloudimg engineers available around the clock via email. Support covers:

• Initial deployment and instance sizing guidance
• Log shipper configuration (Loki, Fluent Bit, Vector, OpenTelemetry Collector, syslog) against the ingest endpoint
• Retention, disk sizing and storage tuning
• TLS termination with Let's Encrypt or custom certificates
• nginx reverse proxy and authentication configuration
• VictoriaLogs version upgrades
• Troubleshooting ingestion, query and connectivity issues

VictoriaLogs and VictoriaMetrics are trademarks of their respective owners. cloudimg is not affiliated with or endorsed by VictoriaMetrics. All product and company names are trademarks or registered trademarks of their respective holders.