DCA Hardened Data Store for Valkey — Support & Quick Start

At a glance

Status	Live on Oracle Cloud Marketplace
Version	8.0.10
Platform	Oracle Linux 9
Ports open in the host firewall	SSH (22/tcp), 6379/tcp
Category	Databases
Upstream licence	BSD-3-Clause
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. Valkey runs as a systemd service bound to loopback (127.0.0.1:6379), protected-mode on, password required. Check status:

   sudo systemctl status valkey

3. The password was generated uniquely for this instance at first boot. Read it (root only):

   sudo cat /root/.valkey_default_credentials

4. Smoke-test from the instance (valkey-cli warns that -a puts the password on the command line; that is expected):

   valkey-cli -a '<password>' PING
   valkey-cli -a '<password>' INFO server

   PING answers PONG; INFO reports the running version on its valkey_version line.

5. Rotate the password at any time:

   valkey-cli -a '<password>' CONFIG SET requirepass '<new-password>'
   then update the requirepass line in /etc/valkey/conf.d/local.conf so it survives a restart.

6. To reach Valkey from your application tier, expose it deliberately — append a bind override to the local config:

   echo 'bind 0.0.0.0' | sudo tee -a /etc/valkey/conf.d/local.conf
   then: sudo systemctl restart valkey

   Port 6379 is already permitted in the host firewall. Restrict it in your VCN security list to the application tier's CIDR; never expose Valkey to the internet. Protected mode and the password stay on. The cluster-bus (16379) and Sentinel (26379) ports remain blocked by the host firewall.

7. Data lives in /var/lib/valkey. Recommended sizing: at least 2 OCPU (4 vCPU) and 16 GB memory; size memory to your working set. For anything beyond evaluation, attach a block volume and point the dir setting at it before loading data.

The image is CVE-patched at build time. Apply ongoing updates, including Valkey errata from the Oracle Linux AppStream repository, with:

sudo dnf -y update

What the image provides

• Valkey 8.0.10, installed from the Oracle Linux 9 AppStream repository, so Oracle carries its security-errata stream directly — no third-party package repository is added to the image.
• Loopback-bound and password-protected by default. The server listens only on 127.0.0.1 with protected-mode on, and a per-instance password is generated on first boot; no shared secret is baked into the image.
• Security hardening aligned to the Oracle Cloud Marketplace image standards: SELinux enforcing, host firewall default-deny with only SSH and the Valkey port permitted, no account with a usable password, no stray keys, and the image fully patched at build time.

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.

Valkey and the Valkey logo are trademarks of LF Projects, LLC. This image is an independent hardened distribution and is not affiliated with, endorsed by, or sponsored by the Valkey project or LF Projects, LLC.