Customer-operated single-instance edge routing and transfer service with token-protected APIs, local state and buyer-configured private endpoints. Complements a buyer delivery path; no hosted seller account is required.
HYDRA-CDN Edge Resilience packages a customer-operated edge routing and transfer service in the buyer AWS account. The included application exposes token-protected private-network APIs and local health/state operations. The buyer configures the origin/CDN/client integration and any private decode/service endpoints; the AMI does not provision a decoder cluster or a global delivery network.
First boot creates a unique API token. The application listens on plain HTTP8080 and must stay on a trusted private network or behind a buyer-managed TLS terminator; never send bearer credentials over an untrusted plaintext path. Admin and Redis ports remain private/loopback. No seller account, additional software purchase, hosted activation or upload to a seller service is required for the included workflow.
Application state and local Redis persistence belong to the instance. Existing launch/reboot evidence verifies health and retention of a test Redis key. Customer backup/restore, resource capacity, private-network configuration and origin fallback require operator setup and validation. At capacity, writes may fail. Shadow telemetry is bounded and does not change decode decisions.
This listing does not claim global-CDN replacement, end-to-end delivery guarantees, blackhole recovery, automatic origin fallback or fixed performance. Health checks do not establish a complete buyer delivery path. Historical synthetic loss/recovery experiments are not production-network measurements. EC2/EBS and buyer-enabled AWS services have separate AWS charges. Follow the version-specific guide for configuration, access and troubleshooting.
Highlights
Customer-local edge routing/transfer APIs with buyer-configured private endpoints
Unique firstboot API token, local state and explicit network protection requirements
Documented single-instance operations, capacity and buyer recovery responsibilities
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing is based on actual usage, with charges varying according to how much you consume. Subscriptions have no end date and may be canceled any time. Alternatively, you can pay upfront for a contract, which typically covers your anticipated usage for the contract duration. Any usage beyond contract will incur additional usage-based costs.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
You pay by the hour for running HYDRA-CDN software on an EC2 instance. Pricing is tied to the instance type you choose, not fixed tiers or feature packages. The five options span different compute sizes: a t3.medium, three compute-focused instances (c6i.large, c6i.xlarge, c6i.4xlarge), and a memory-balanced m6i.xlarge. Larger or more capable instances carry higher hourly rates. You scale cost by selecting the instance that fits your workload and by how many hours you run it. EC2, EBS, and other AWS services bill separately at standard AWS rates.
Top-of-mind questions for buyers
What counts as one instance-hour for billing on each instance type?
One instance-hour is one hour of HYDRA-CDN software running on one EC2 instance of that type. Each running instance meters separately. This is a single-instance deployment, so the software does not run across multiple nodes. Partial hours and the exact rate depend on the instance type you launch.
Am I charged software fees while the instance is stopped or powered off?
Software charges meter running time only. A fully stopped or powered-off instance does not accrue HYDRA-CDN hourly charges. However, EBS storage and other buyer-enabled AWS services keep their normal AWS charges even when the instance is stopped. Application state on disk persists but is billed separately by AWS.
What is not included in the hourly software price?
The hourly rate covers HYDRA-CDN software usage only. EC2, EBS, and any buyer-enabled AWS services bill at standard AWS rates. Backups, patching, multi-node setup, and private-network configuration are buyer operations. No high-availability, fixed latency, automatic failover, or fixed throughput is guaranteed.
kenosian.com
Helpful?
Vendor refund policy
Refund requests are evaluated under the applicable AWS Marketplace terms and the published product support policy.
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Customer-operated single-instance edge routing and transfer service with firstboot credentials, private HTTP API, local state and buyer-configured private endpoints. Existing image retained; documentation clarifies operations and recovery responsibilities. Shadow telemetry does not change decode decisions. No global CDN or zero-loss guarantee.
Additional details
Usage instructions
Launch this Ubuntu24.04 AMI in your AWS account as ubuntu on a listed c6i.large/m6i.xlarge or sufficient instance. Restrict SSH22 to your administrator /32 or use authorized SSM access. Application HTTP8080 is plaintext: restrict it to a trusted private network or place it behind a customer-managed TLS terminator. Never expose bearer credentials over an untrusted plaintext connection. Keep admin9082 and Redis16379 private/loopback. 2. Run sudo systemctl show hydra-firstboot-token.service -p Result -p ExecMainStatus, then sudo systemctl is-active hydra-redis hydra-server and curl --fail http://127.0.0.1:8080/health. A completed firstboot oneshot may be inactive. 3. First boot creates the root-owned mode0600 token file /etc/hydra/hydra.env. Retrieve only within a private authorized administrative session; never put the token in user data, logs, tickets or seller messages. Use it as a Bearer token for protected client routes. 4. Inspect the installed hydra-server.service and configure DECODE_NODES to buyer-controlled private endpoints when applicable; no decoder cluster is provisioned. Connect the buyer origin/CDN/client path and separately verify delivery completion and origin fallback; a health response is not an end-to-end delivery result. 5. Inspect service status, local Redis ping, disk/memory and buyer backup/restore. State is under /var/lib/hydra-kv and /var/lib/hydra-redis. Local Redis capacity can reject writes; backups and multi-node deployment are buyer responsibilities. RGRK is bounded shadow telemetry and does not change decode decisions. No global-CDN, zero-loss or blackhole-recovery guarantee is made. No seller activation or second software purchase is required. Full setup and troubleshooting: https://kenosian.com/docs/marketplace/hydra-cdn.html . Business-hours support: info@kenosian.com.
Business-hours installation and troubleshooting by email: info@kenosian.com. Include product/version and redacted status only; do not send tokens, private keys or customer payloads. No24/7 support or uptime/latency SLA. Operation guide:
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Fastly's edge cloud platform is a globally distributed, programmable platform designed to take advantage of the modern internet and complement major cloud providers like AWS. Whether you need a high-performance CDN, enterprise-grade web application firewall (WAF), advanced bot protection, or powerful serverless edge computing, Fastly delivers it all without sacrificing speed or control.
Add a regional CDN to your Amazon CloudFront distribution. Mediatriple's network serves your viewers in Turkey, Europe, the Middle East and Africa, every other country stays on CloudFront. Route 53 geolocation routing in your account splits the traffic, health checks fall back to CloudFront automatically, packages are billed on your AWS invoice.
Cisco Secure Access, Cisco's Security Service Edge (SSE) solution, includes secure Zero Trust Network Access to your company's private/internal resources. Resource connectors are virtual machines deployed in your AWS environment that forward remote user traffic to your applications without requiring open inbound ports in your firewall.
Be the first to review this product. We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.