Hello,
The Cloud team is happy to announce that ScyllaDB Cloud now supports wider IPv4 ranges for customer VPC peering connections.
VPC peering and Transit Gateway connections are no longer limited to RFC 1918 address ranges. Your VPC can now use:
- Private IPv4 ranges (RFC 1918), shared address space (100.64.0.0/10), or public IPv4 ranges supported by your cloud provider.
When you configure the connection:
- Enter only the ranges configured in the VPC you are peering from. ScyllaDB Cloud adds routes for every range you enter, so an incorrect range can interrupt access to external services.
- The ranges must not overlap any network in your ScyllaDB cluster, including the CIDR block you set when creating the cluster.
- Your VPC may use 172.17.0.0/16, even though this range is reserved for ScyllaDB cluster networks. AWS recommends avoiding it where possible, because services such as Cloud9 and SageMaker can use it internally. See AWS IPv4 CIDR considerations.
- The ranges must not overlap 0.0.0.0/8, 127.0.0.0/8, 169.254.0.0/16, 224.0.0.0/4, or 240.0.0.0/4 (see RFC 6890).
More in Configure Network Access