Too many IPs required for BitBucket webhooks

[tm56]

We're moving an app to a shared, secured server, protected by a firewall.

We need to allow BitBucket's webhook incoming push requests through this firewall, which offers only 20 IP rules.

BitBucket's webhook requests come from no less than 34 different IP addresses!

Even if we combine them with CIDR, this would still use up a lot of slots, and wouldn't leave enough rules available for the other required allowed IPs.

Is there no better way to allow these webhook incoming requests, using up less IP slots?

If not, this would mean we need to set up a pipeline for this specific app. This is quite a chore, we'd be happy to skip.

Thanks

[Ben]

Hi @tm56 

With constant uptime/reliability in mind - it is recommended to whitelist all of these IP addresses, as we use multiple distributed servers to deliver content/connectivity to our platforms.

I would suggest either considering an upgrade of your firewall, or preparing a Pipeline to handle this connectivity. 

Cheers!

- Ben (Bitbucket Cloud Support)