Version-specific AWS Marketplace customer deployment instructions. Documentation is not activation or external fulfillment.
Launch the listed Ubuntu24.04 image as ubuntu using a permitted c6i.large/m6i.xlarge or sufficient listed instance. Restrict SSH22 to the buyer administrator /32, or use an authorized Systems Manager session. The application API is plain HTTP8080: use it only on a trusted private network or behind a buyer-managed TLS terminator. Keep admin9082 and Redis16379 on loopback. A bearer token must never traverse an untrusted plaintext path.
sudo systemctl show hydra-firstboot-token.service -p Result -p ExecMainStatus sudo systemctl is-active hydra-redis hydra-server curl --fail http://127.0.0.1:8080/health
The firstboot oneshot can be inactive after successful completion. It creates /etc/hydra/hydra.env root-owned mode0600 with a unique API token. Retrieve it only in a private authorized administrative session; do not log it, use it in public user data or send it to the seller.
Inspect the installed hydra-server.service and configure DECODE_NODES to buyer-approved private decode/service endpoints where that feature is used. The image does not create a decoder cluster. Configure the existing CDN/origin/client integration for your path; a health response alone does not demonstrate a complete artifact-delivery workflow. Token-protected /kv and /cdn routes require the instance Bearer token. Keep the original origin path available for failure handling; verify client-side fallback in your own integration.
sudo systemctl status hydra-server hydra-redis --no-pager sudo redis-cli -h 127.0.0.1 -p 16379 ping
Inspect redacted service logs, application health and your actual delivery completion checks. RGRK observations are bounded shadow telemetry and do not alter decode decisions. No global CDN, blackhole recovery, loss-free transmission, automatic failover or fixed throughput is guaranteed.
Application state is under /var/lib/hydra-kv and Redis under /var/lib/hydra-redis. Redis is local and configured for AOF; a prior reboot smoke test retained a test key. Size and monitor disk/memory, and take buyer-controlled snapshots with tested restore. At capacity, writes can fail. The AMI does not automate backups, multi-node deployment or upstream installation.
Subscribe to this AMI through its AWS Marketplace offer and launch the selected version in your account. No seller-operated verification account, seller activation approval, second software purchase or proof upload is needed for the included workflow. EC2, EBS and any buyer-enabled AWS services have their normal AWS charges. Use an instance IAM role for AWS access; do not enter long-lived AWS access keys into this product. These instructions neither subscribe you to another Kenosian product nor send telemetry to a seller service.
Email info@kenosian.com for business-hours installation and troubleshooting support. Send version IDs and redacted service status; never send API tokens, private keys or customer payloads. This is a single-instance deployment. Customer backup/restore, patching, capacity limits and upstream/private-network configuration require buyer operations. No high-availability, fixed-latency, total-data-loss prevention or regulatory-certification guarantee is made.