Newly created
IPsec VPN
Cloud Connect integrations will now be able to use any IP address range across the entire private IP address space (RFC1918) except for the IP address ranges:- assigned to devices (see https://docs.emnify.com/how-tos/add-ip-address-spaces, the Updatedtab),
- used by other Cloud Connect integrations of the same organization.
When using both Cloud Connect and OpenVPN, then avoid assigning subranges of 10.64.0.0/10 (e.g. 10.110.0.0/16) to CloudConnect. OpenVPN clients get private IP addresses assigned in 10.64.0.0/10 but, in this example, 10.110.0.0/16, being more specific (longer prefix) will be routed to Cloud Connect. If in doubt please contact the emnify support.
The same statement applies to
TGW Attachment
Cloud Connect integrations created in eu-west-1, eu-central-1, eu-central-2, us-east-1, sa-east-1, ca-central-1 and ap-southeast-1. TGW Attachment integrations created in eu-west-2, eu-west-3, eu-south-1, af-south-1, ap-southeast-2, us-west-1 on the other hand are limited to /22 CIDRs and additional availability checks.