Overview
Tyk Gateway services active on loopback
The redis-server, tyk-gateway and nginx services active under systemd with Tyk Gateway 5.14.0, the gateway and Redis bound to loopback while only nginx serves port 80.
Tyk Gateway services active on loopback
Public gateway health endpoint
Control API gated and loopback only
Request proxied through the gateway
This is a repackaged open source software product wherein additional charges apply for cloudimg support services.
What You Get
A production-ready Tyk API Gateway (version 5.14.0) running as hardened systemd services within minutes of launch. No manual installation of the gateway or Redis, no configuration writing, no nginx wiring - just launch, retrieve your unique credentials, and start defining APIs.
Why Tyk Gateway
Tyk Gateway is a fast, cloud-native, open source API gateway written in Go. It handles authentication, authorization, rate limiting, quotas, request and response transformation, API versioning, and analytics - all driven by declarative API definitions. Tyk is trusted across the open source community for its performance and flexibility.
This cloudimg image ships the open source Gateway in file-based mode with a local Redis datastore, giving you a complete standalone gateway with no external dependencies, no Dashboard, and no commercial components.
Example Use Case
Place one gateway in front of a fleet of microservices so every request is authenticated, rate limited, and routed through a single entry point. Define each upstream service as a declarative API definition through the control API. The gateway proxies and load balances traffic, and you version and evolve APIs without touching the services behind them. Because the gateway keeps its keys, quotas, and rate limit counters in Redis, it enforces limits consistently across every request.
Architecture Overview
- Tyk Gateway binary - runs under its own systemd unit, bound to loopback only, serving the data plane, health endpoint, and secret-gated control API on one local port
- Local Redis instance - bound to loopback, stores keys, analytics, and rate limiting counters
- Nginx front end - publishes the data plane and public health endpoint on port 80, explicitly refuses the control API path so the control plane is never reachable from the internet
Security Architecture
The image ships with no known control API secret. On first boot, a one-shot service generates a unique 64-character secret for this instance alone, rewrites the gateway configuration with strict permissions, resolves the instance public URL, and records the secret and URL in a root-only file. The control API and Redis are bound to loopback, and port 80 returns a forbidden response for the control API path. Two instances launched from this image get different secrets - no two instances ever share a control plane credential.
Getting Started
- Launch this image with a security group allowing TCP 80 for API traffic and SSH from your admin address
- SSH in and read your instance control API secret and public URL from the credentials file
- Create your first API definition through the control API and reload the gateway
- Send a request through the public data plane to confirm it is proxied to your upstream
- Check the health endpoint to confirm the gateway and Redis are ready
For a guided onboarding walkthrough or help connecting the gateway to your services, contact cloudimg support at any time - we are available 24/7 with a one-hour average response time for critical issues.
About cloudimg
cloudimg provides expert-supported AMIs on AWS Marketplace, specializing in open source infrastructure software. Our engineers help with every stage from initial deployment through production scaling and version upgrades.
Licensing
Tyk Gateway is distributed under the MPL-2.0 license. cloudimg is not affiliated with or endorsed by Tyk Technologies; the Tyk name is used only to identify the open source software shipped in this image. All product and company names are trademarks or registered trademarks of their respective holders.
Highlights
- Complete standalone open source API gateway: authenticate, rate limit, proxy, transform, and version your APIs from a single Go binary with a local Redis datastore. Runs in file-based mode with no Dashboard and no external control plane. Define upstream services as declarative API definitions through the control API and evolve them independently. Launch to a serving data plane in minutes - no manual installation, configuration writing, or nginx wiring required.
- Secure by default with a unique per-instance secret: on first boot the image generates a cryptographically unique 64-character control API secret for this instance alone and records it in a root-only file. No shared or baked-in credentials exist. The control API and Redis are bound to loopback, and port 80 refuses the control API path, ensuring the control plane is never reachable from the internet. Two instances launched from this image always receive different secrets.
- 24/7 expert support from cloudimg with a one-hour average response time for critical issues. Our engineers help with authoring API definitions, authentication and rate limit policies, nginx and TLS front-end configuration, connecting the gateway to your upstream services, security group rules, health checks, Tyk Gateway version upgrades, and performance tuning for high-throughput deployments. Contact us anytime by email or live chat.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Free trial
- ...
Dimension | Description | Cost/hour |
|---|---|---|
m5.large Recommended | m5.large | $0.08 |
t2.micro | t2.micro instance type | $0.04 |
t3.micro | t3.micro instance type | $0.04 |
c5a.12xlarge | c5a.12xlarge instance type | $0.24 |
c5a.16xlarge | c5a.16xlarge instance type | $0.24 |
c5a.24xlarge | c5a.24xlarge instance type | $0.24 |
c5a.2xlarge | c5a.2xlarge instance type | $0.24 |
c5a.4xlarge | c5a.4xlarge instance type | $0.24 |
c5a.8xlarge | c5a.8xlarge instance type | $0.24 |
c5a.large | c5a.large instance type | $0.08 |
Vendor refund policy
Refunds available on request.
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
Initial release of the open source Tyk Gateway (version 5.14.0) as a ready to use API gateway, with a unique control API secret generated on first boot, the gateway and Redis bound to loopback, and an nginx front end that publishes the data plane and health endpoint on port 80 while refusing the control API path.
Additional details
Usage instructions
Connect via SSH on port 22 as the default login user for your operating system variant (for the Ubuntu 24.04 variant the user is ubuntu). Retrieve this instance's per instance control API secret and public URL with: sudo cat /root/tyk-gateway-credentials.txt - both are generated on first boot from a unique secret. Check gateway health (public, no auth) with: curl http://<public-ip>/hello. The control API is on box only, bound to loopback 127.0.0.1:8080 and gated by the secret; the public port 80 returns 403 for the control API path. Create an API definition and reload the gateway with: SECRET=$(sudo awk -F= '/^TYK_SECRET=/{print $2}' /root/tyk-gateway-credentials.txt); curl -H "x-tyk-authorization: $SECRET" -H 'Content-Type: application/json' -d '{"name":"httpbin","api_id":"httpbin","org_id":"cloudimg","use_keyless":true,"version_data":{"not_versioned":true,"versions":{"Default":{"name":"Default"}}},"proxy":{"listen_path":"/httpbin/","target_url":"http://httpbin.org","strip_listen_path":true},"active":true} ' http://127.0.0.1:8080/tyk/apis ; curl -H "x-tyk-authorization: $SECRET" http://127.0.0.1:8080/tyk/reload/group . Then send a request through the data plane: curl http://<public-ip>/httpbin/get. The recommended security group opens ports 22 (SSH) and 80 (API traffic). Services run under systemd: systemctl status tyk-gateway redis-server nginx.
Resources
Vendor resources
Support
Vendor support
cloudimg Support for Tyk Gateway
cloudimg provides 24/7 technical support for this Tyk Gateway product by email (support@cloudimg.co.uk ) and live chat.
Response Times:
- Critical issues: one-hour average response time
What We Help With:
- Deployment and first-boot configuration
- Retrieving your per-instance control API secret and public URL
- Authoring declarative API definitions
- Authentication, rate limiting, and quota policies
- Request and response transformation
- API versioning configuration
- Connecting the gateway to your upstream services
- Nginx and TLS front-end configuration
- Security group rules for the data plane on TCP 80
- Health checks and troubleshooting
- Tyk Gateway version upgrades and security patch guidance
- Performance tuning for high-throughput deployments
Billing and Refunds: For billing inquiries, subscription changes, or refund requests, contact support@cloudimg.co.uk .
Instance Sizing Guidance: Contact our team for recommendations on EC2 instance types matched to your expected request volume and concurrency requirements.
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

