IP Delimitation in pipelines for Disabling MFA in Automated Tests

[Raul Picos]

We are running automated tests from a pipeline in a Bitbucket repository, but we need to define the IPs that the container generates to send them to the security team, so they can disable the MFA in the application we are going to test. Is that clear?

How can I do it?

[Theodora Boudale]

Hi Raul and welcome to the community!

If I understand correctly, you are looking for the IP addresses that your Pipelines builds are running from, is that correct?

The servers that execute all steps on Atlassian Cloud Infrastructure are hosted on Amazon Web Services (AWS).

An exhaustive list of IP addresses that the traffic may come from on AWS can be found by using the following endpoint:

• https://ip-ranges.amazonaws.com/ip-ranges.json

and filtering to records where the service equals EC2 or S3, and using the us-east-1 and us-west-2 regions. Please keep in mind that we do not recommend using these IP ranges as a security control due to their broad nature.

If your prefer a certain Pipelines step to run from more limited IP ranges, you could utilize the atlassian-ip-ranges flag that is available in larger steps (size 4x and above) for the Standard and Premium billing plans:

• https://support.atlassian.com/bitbucket-cloud/docs/step-options/#Runtime

Please Note: Opting for larger step sizes (4x/8x) may impact billing. We encourage you to review the relevant documentation on step sizes here to understand these implications fully.

These steps will run from a more limited range of IP addresses, that are listed here:

• https://support.atlassian.com/bitbucket-cloud/docs/what-are-the-bitbucket-cloud-ip-addresses-i-should-use-to-configure-my-corporate-firewall/#Atlassian-IP-ranges

Please feel free to let me know if you have any questions.

Kind regards,
Theodora