To ensure BlazeMeter's cloud engines can communicate with your application server, you may need to whitelist the relevant IP ranges. Here you'll find the available CIDRs (Classless Inter-Domain Routing) for the IPs used by BlazeMeter cloud engines.
While this document only pertains to engines, if you want more information about whitelisting other BlazeMeter addresses, please refer to our master guide Whitelisting BlazeMeter.
NOTE: Our providers each require a wide range of IPs to be whitelisted in order to use them for engines. If you find these ranges to be too wide to fit your security standards, then please consider the alternative options we provide for Running Performance Tests Behind Your Corporate Firewall.
Downloadable list of AWS Engines in JSON format
Find the AWS EC2 Region code<>Name mapping chart here.
Downloadable list of GCE Engines in JSON format
For more information, see Where can I find Compute Engine IP ranges? (in the Google Cloud documentation).
Find the Google Cloud Region code<>Name mapping chart here.
Downloadable list via this link (XML format).
Find the Azure Region code<>Name mapping chart here.
Functional GUI Testing Location IPs:
US East (Virginia) - Default Location
|US West (Oregon)||188.8.131.52
|EU West (London)||184.108.40.206
I just had our network configured to receive calls from the 6 IPs listed here for Blazemeter SandBox. When I tried running the test, the loadgenerator IP was NOT any of the ones listed. And then, for my surprise, when I looked at this page today, the SandBox IPs were REMOVED from the page content. Since I'm working on a PoC for Blazemeter, please reply to this comment ASAP. Thanks.
I want to know if BlazeMeter connects over port 443? Please confirm
Yes, Blazemeter utilizes SSL port 443
I am having same issue as in Eduardo's comment above.
Eduardo Tergolina Filho did you solve this issue?
Why do we have Azure and AWS locations in Blazemeter. Will it make any difference in response time or anything else, if we run test.
How is it useful to tell us to whitelist the entire AWS IP ranges (Downloadable list in JSON format)? That would open up our network to anyone running in AWS, not only BlazeMeter agents. That is a huge security risk. I'm surprised this article is even suggesting that.