Overview
HYDRA-CDN Edge Resilience gives infrastructure teams a buyer-managed API foundation for connecting application delivery paths. Keep control of how your clients, origins and existing delivery infrastructure connect through routing and transfer interfaces in your AWS account.
The AMI packages the service, local state and a unique first-boot access token so teams can begin evaluating the supplied APIs and connect them to application-specific workflows. Baseline operation is independent of a seller-hosted activation account.
Use the packaged service checks to establish a starting point, then validate the client-to-origin path and recovery behavior that your application needs. Configure access and integration alongside your existing delivery tools.
Run the HTTP API on a trusted private network or behind your TLS termination. Buyers manage origin and CDN integration, capacity and backups for the resulting delivery path.
Highlights
- Own your delivery integration: connect clients, origins and existing delivery infrastructure through buyer-managed routing and transfer APIs.
- Operate within your AWS account: control service access and local state with a unique first-boot token.
- Build around your workflow: use packaged service checks and private APIs to evaluate application-specific delivery paths.
Details
Features and programs
Financing for AWS Marketplace purchases
Pricing
Dimension | Description | Cost/hour |
|---|---|---|
t3.medium instance-hour Recommended | Hydra-CDN software usage on one t3.medium EC2 instance, per hour. | $0.50 |
c6i.large instance-hour | Hydra-CDN software usage on one c6i.large EC2 instance, per hour. | $0.50 |
c6i.xlarge instance-hour | Hydra-CDN software usage on one c6i.xlarge EC2 instance, per hour. | $1.50 |
m6i.xlarge instance-hour | Hydra-CDN software usage on one m6i.xlarge EC2 instance, per hour. | $1.50 |
c6i.4xlarge instance-hour | Hydra-CDN software usage on one c6i.4xlarge EC2 instance, per hour. | $4.00 |
Dimensions summary
Top-of-mind questions for buyers
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?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
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 .
Resources
Vendor resources
Support
Vendor support
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 infrastructure support
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.
Similar products
