Velero sending requests to unexpected AWS regions?

[braudel]

Hello all,

I started doing some observability on outbound connections from my EKS and to my surprise I see several connections from velero to all sort of regions not related to my backup storage location. Ie running all within eu-west-1 but I see events like:

falco-687m5 falco 19:51:19.307379496: Notice Disallowed outbound connection destination <NA> (command=restic backup --repo=s3:s3-eu-west-1.amazonaws.com/... connection=198.19.2.213:58358->52.46.134.192:443 ...

falco-7487j falco 19:51:39.456149095: Notice Disallowed outbound connection destination <NA> (command=velero-plugin-f --log-level info connection=198.19.7.165:59654->52.95.132.163:443 ...

falco-7487j falco 19:51:40.967321085: Notice Disallowed outbound connection destination <NA> (command=velero-plugin-f --log-level info connection=198.19.7.165:34876->54.239.29.25:443 ...

Which according to maxmind geoip2 are nothing to do with eu-west-1:

52.46.134.192	US	Ashburn,Virginia Amazon.com	Amazon.com 
52.95.132.163	AU	Sydney           Amazon.com	amazonaws.com	
54.239.29.25	US	Ashburn          Amazon.com	Amazon.com

Any ideas why both velero and the plugin for aws seem to be triggering connections outside of my running region? The only backupstorage location I have is within eu-west-1.