Overview
Services and listening ports
Toxiproxy, the bundled demo upstream and the nginx control-API front door running under systemd, with the raw control API and upstream bound to loopback only.
Services and listening ports
The bundled demo proxy
A toxic shaping real traffic
Loopback-only API, authenticated front door
This is a repackaged open source software product wherein additional charges apply for cloudimg support services.
Toxiproxy - Deterministic Resilience and Chaos Testing
Catch dependency failures before they reach production. Toxiproxy sits between your application and its upstream services - databases, caches, queues, and APIs - and injects controllable failures called toxics: latency, bandwidth limits, timeouts, connection resets, and data slicing. Because failures are deterministic and scriptable, you can reproduce a slow database or a flaky network in a test suite or staging environment exactly, on demand, instead of waiting for it to happen in production.
Ready to Test in Minutes
This image delivers Toxiproxy fully installed and running under systemd, so a working proxy is available within minutes of launch with no manual compilation or configuration editing required.
Out-of-the-box demo included:
- A small bundled upstream on the loopback interface
- A demo proxy forwarding a public port to that upstream
- A sample latency toxic already applied
List the proxies or curl through the demo port and you immediately see a real, failure-injecting TCP proxy on first boot.
Secure by Default
The Toxiproxy control API is unauthenticated by design and can create proxies to arbitrary destinations. This image addresses that risk with multiple layers:
- Control API bound to the loopback interface only - never exposed to the network
- Remote access fronted by an nginx reverse proxy over TLS
- HTTP Basic credential generated uniquely per instance at first boot - never baked into the image
- Only SSH, the demo proxy data port, and the authenticated control-API endpoint are opened
- Operating system ships fully patched with unattended security updates enabled
- systemd manages all services for automatic restarts and clean logging
Use Cases
- Pre-production resilience validation: verify your application handles slow or failed dependencies gracefully before deploying to production
- Automated test suites: script toxic injection via the HTTP control API to include failure scenarios in CI/CD pipelines
- Staging environment chaos: reproduce exact production failure modes on demand for debugging and root-cause analysis
- Dependency timeout tuning: validate that your connection pools, retries, and circuit breakers behave correctly under degraded conditions
Deploying on AWS
Deploy directly from AWS Marketplace onto any supported EC2 instance, alongside your existing VPC and security groups. After launch, retrieve your unique per-instance HTTP Basic credential over SSH from the root-only credentials file at /root/toxiproxy-credentials.txt, then point your application at the proxy ports instead of directly at your dependencies. Open only the ports your test clients need in the instance security group.
24/7 cloudimg Support Included
This product includes 24/7 technical support from cloudimg via email and live chat. The support team assists with deployment, control-API usage, toxic design for your specific failure modes, and security configuration.
Licensing and Attribution
This is a repackaged open source software product with additional charges for cloudimg support services. Toxiproxy is distributed under the MIT license. cloudimg is not affiliated with or endorsed by Shopify or the Toxiproxy project. All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
Highlights
- Deterministic chaos testing on demand: Reproduce slow dependencies, flaky networks, timeouts, and connection drops between your application and its databases, caches, queues, and APIs. Inject and remove toxics via the toxiproxy CLI or a scriptable HTTP control API, making failure scenarios repeatable in CI/CD pipelines and staging environments rather than waiting for them to surface in production.
- Running in minutes with a working demo on first boot: Toxiproxy is installed from official SHA256-verified release binaries and managed by systemd. The image ships a self-contained demo - a bundled upstream, a proxy on a public port, and a sample latency toxic already applied - so you can verify a real failure-injecting TCP proxy immediately after launch with no compilation or manual configuration required.
- Secure by default with 24/7 cloudimg support: The unauthenticated control API is bound to loopback only and fronted by an nginx TLS reverse proxy gated by a unique HTTP Basic credential generated per instance at first boot. Only SSH, the demo data port, and the authenticated endpoint are exposed. Backed by 24/7 cloudimg technical support via email and live chat for deployment, toxic design, and security configuration.
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.
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). Read the per-instance control-API credential and connection facts from /root/toxiproxy-credentials.txt (sudo cat /root/toxiproxy-credentials.txt). Drive the control API locally with the toxiproxy-cli command (for example: toxiproxy-cli list to see the bundled demo proxy, toxiproxy-cli inspect demo to see the sample latency toxic). The demo proxy forwards http://<instance-ip>:8080/ to a bundled loopback upstream; curl it to see the injected latency. For remote programmatic access, call the nginx-fronted control API at https://<instance-ip>:8443/ using the per-instance HTTP Basic credential (the raw control API on port 8474 is loopback only and never exposed). Point a proxy at your own dependency to reproduce network failures. Full walkthrough: https://www.cloudimg.co.uk/guides/toxiproxy-aws/
Resources
Vendor resources
Support
Vendor support
cloudimg Support
cloudimg provides 24/7 technical support for this product via email and live chat.
Contact: support@cloudimg.co.uk
What we help with:
- Deployment and initial configuration of the Toxiproxy image
- Retrieving your per-instance HTTP Basic credential after first boot
- Driving the Toxiproxy control API and the toxiproxy-cli command
- Designing toxics to reproduce your specific production failure modes
- Wiring the authenticated control-API endpoint to your own domain and TLS certificate
- Securing and network-scoping the demo and control ports
- Integrating Toxiproxy into CI/CD pipelines and automated test suites
- Updates and security patching guidance
Getting Started:
After launching the image, read your unique per-instance credential over SSH from the root-only file /root/toxiproxy-credentials.txt (sudo cat /root/toxiproxy-credentials.txt). Use the toxiproxy-cli command or the authenticated TLS endpoint to begin creating proxies and applying toxics. Contact support if you need guidance on instance sizing or security group configuration.
Refunds: For refund requests, contact support@cloudimg.co.uk with your AWS account ID and subscription details.
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.