Simple FTP Service
Backend storage IP addresses
The IP addresses DocEvent's servers connect to your backend storage bucket from, per region - for bucket firewalls and ACLs.
Updated August 27, 2026Every file your users transfer through a Simple FTP Service is read from and written to your own backend storage - an S3 bucket, Azure Blob or Files storage, Google Cloud Storage, or any S3-compatible service. If you lock that storage down with a firewall or ACL, you need to allow DocEvent's servers to reach it.
These are the addresses our servers connect to your backend from, for the region your service runs in:
Which region does your service run in?
Allowlist every address below in your bucket's firewall or ACL - our servers may connect from any of them. The protocol your users connect with makes no difference here.
Backend storage IP addresses - us-east-1
| Backend storage IP addresses |
|---|
| 3.210.142.47 |
| 3.211.167.134 |
| 18.209.207.68 |
| 35.168.146.20 |
| 52.4.181.92 |
| 52.6.253.28 |
| 52.71.75.143 |
| 52.71.138.25 |
| 52.201.2.103 |
| 52.206.73.31 |
A few things worth knowing:
- The protocol your users connect with doesn't matter. FTP, FTPS and SFTP all reach your bucket from the same set of addresses - this list is about the connection between DocEvent and your storage, not between your users and DocEvent.
- Allowlist the whole set for your region. Any of the addresses may be the one connecting at a given moment.
- For Azure storage accounts, these are the addresses to add under Security + networking → Networking → Firewall - see Verifying a service with an Azure firewall enabled for the full walkthrough, including how to get past the create-time verification.
- For client-side firewalls - what your users need to allow to connect to the FTP/SFTP service itself - see Static IP addresses and ports.