Hi and welcome to the community!
We are migrating our 1x/2x size option builds to operate from new, broader IP ranges.
The Atlassian IP ranges from the documentation you shared are used only by 4x or 8x steps for workspaces on the Standard or Premium plan. If your workspace is on Standard or Premium plan and you would like your build step to use this more restricted set of IPs, your step will need to use a 4x or 8x size and the atlassian-ip-ranges: true flag. This is the documentation for both:
Please Note: Opting for larger step sizes (4x/8x) may impact billing. We encourage you to review the relevant documentation on step sizes above to understand these implications fully.
If you don't use this configuration or if your workspace is on the Free plan, then the following applies (I am quoting from the same documentation page you linked):
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, filtering to records where the service equals EC2 or S3, and using the us-east-1 and us-west-2 regions. We do not recommend using these IP ranges as a security control.
So, you will need to check this list:
and filter to records where the service equals EC2 or S3, and using the us-east-1 and us-west-2 regions.
Important Note: The IP addresses provided via this endpoint are managed by Amazon and are subject to change. We recommend regularly checking this endpoint and updating your firewall's IP list accordingly. Additionally, consider exploring automation options to streamline updating IPs in response to changes.
I hope this helps. Please feel free to let me know if you have any additional questions.
Kind regards,
Theodora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.