There was recently a question regarding monday-code Network Allowlist:
The allowlist needs explicit FQDNs (no wildcards). Our backend hits `assets.public_url` from GraphQL, and across three test accounts I'm already seeing different hosts, e.g. prod-euc1-files-monday-com.s3.eu-central-1.amazonaws.com and files-monday-com.s3.amazonaws.com.
The answer from the monday.com support:
I have the official list of Fully Qualified Domain Names (FQDNs) used by monday.com for file assets. As you observed, these URLs depend entirely on the hosting region of the specific account.
Since the monday-code Network Allowlist requires explicit entries and does not support wildcards, you will need to add the following four hostnames to reliably proxy file downloads across all regions and account tiers:
US (Default/Legacy): files-monday-com.s3.amazonaws.com
EU (Frankfurt): prod-euc1-files-monday-com.s3.eu-central-1.amazonaws.com
APAC (Sydney): prod-apse2-files-monday-com.s3.ap-southeast-2.amazonaws.com
Israel (Tel Aviv): prod-ilc1-files-monday-com.s3.il-central-1.amazonaws.com