Hi Team,

In our Azure environment NSG outbound rules are not allowed to public websites from any Linux VM. We have allowed specific IP ranges to allow https://bioconductor.org website. Problem is these IP ranges are not fixed. Every call to this website gives different IP ranges. Is there a way or can you please provide a better way to handle this problem? By the way we cannot use a website url in NSG to allow a web address instead of IPs.

Please help.

Thanks,

Vivek Katakwar

bioconductor.org is served using Amazon Web Services route 53 / Cloudfront. IP addresses of 'edge' servers are described at https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html . Specific ranges are provided in https://ip-ranges.amazonaws.com/ip-ranges.json . Probably there are standard solutions to accessing cloudfront resources.

In classic HPC environments it is normal for a 'head' node to have internet access and compute nodes to be static with respect to internet content. Perhaps a similar scheme is appropriate in your current environment (why do your cloud nodes require dynamic access to bioconductor.org?) Probably it is worth asking why the policy is in place in the first instance, e.g., to avoid a mis-configured cloud computation from excess data download and generally to make efficient use of the compute resources without download bottlenecks.

Cloudfront resources are served from master.bioconductor.org, which has a static IP address 52.71.54.154 but always requires data movement from the location of the server (somewhere in the us-east), slowing downloads.