Unable to run the submitted job through AWS batch with Seqera listed firewall configuration IP

Ask for help
,
1

Hi,
Does the Seqera firewall configuration IPs changed recently?
I’m running my pipeline without an issue until last month using AWS Batch compute enviornment. But now I couldn’t able to run the very same pipeline with the same seqera IP setting…

18.135.7.45/32
18.169.21.18/32
18.171.4.252/32
35.176.121.51/32
35.178.254.247/32

In addition I added the following IPs (https://www.cloudflare.com/ips-v4/#) in my security group…

173.245.48.0/20
103.21.244.0/22
103.22.200.0/22
103.31.4.0/22
141.101.64.0/18
108.162.192.0/18
190.93.240.0/20
188.114.96.0/20
197.234.240.0/22
198.41.128.0/17
162.158.0.0/15
104.16.0.0/13
104.24.0.0/14
172.64.0.0/13
131.0.72.0/22

I could see if my security group inbound rules open to all IP then no issue. So I suspect the above IP configuration not correct! Appreciate any help.
Thanks
Justin

2

Hi Justin.

Can you share the error that you are seeing? The Seqera property addresses are publicly available at https://meta.seqera.io

3

@robsyme thank you for your response.
I used the very same seqera IP addresses. But the subnet of my vpc “Auto-assign public IPv4 address” was disabled “No”, the cluster requires public IP address to communicate to seqera in the internet. Now, jobs are allowed to submit by enable (Yes) the “Auto-assign public IPv4 address”.

4

Great! Glad to hear that you’ve found a resolution.