Flood Agent
Search…
Introducing Flood Agent
Getting Started on Linux
Getting Started on macOS
Getting Started on Windows
Getting Started - Docker
Getting Started - Local JMeter & Gatling
Running a Flood
Shutting down
How it works
Configuration
Configuring Flood Agent
Configuring JMeter
Configuring Gatling
Configuring Flood Element
Deployment
Overview
Running with systemd (linux)
Running with NSSM (Windows)
Networking
Integrating with a web proxy
HOW-TOs
Setting up Flood Agent with Digital Ocean
Powered By GitBook
Networking
Flood agent requires access to several endpoints to operate.
To verify network connectivity, please use the flood-agent check command.
If you discover that connectivity is limited, please contact your operations staff.
Your internal network may already have a web proxy which you can use. For more details see Integrating with a web proxy.

Endpoints

The machine running flood-agent must have access to the following endpoints:
  • https://drain.flood.io
  • https://beacon.flood.io
  • https://vault.flud.io
  • https://flood-archives.s3-accelerate.amazonaws.com
  • https://logs.us-east-1.amazonaws.com
  • https://sns.*.amazonaws.com
  • https://sqs.*.amazonaws.com
  • https://us-west-2.compute.amazon.aws.com
  • https://*.docker.io (if planning to use Flood Agent with Docker)
​
Deployment - Previous
Running with NSSM (Windows)
Next - Deployment
Integrating with a web proxy
Last modified 1yr ago
Copy link
Contents
Endpoints