Typical use cases for Cloud Networks

Cloud Networks is especially useful for tightening security, increasing flexibility, and maintaining uninterrupted availability.

Secure east and west traffic

Get fully isolated, single-tenant Layer 2 networks designed to securely transfer sensitive information between servers located in the same region.

Enforce consistent network configuration

Program static routes, the gateway IP, and DNS servers into the Cloud Network API and have them automatically injected in your servers at boot time or when the network is attached. Use a Gateway Instances to connect your isolated Cloud Servers to the Internet.

VPN endpoint

Securely connect to remote resources via VPN. By programming static routes into your Cloud Networks subnet, you can ensure that all servers attached to your Cloud Network can access the remote networks connected via VPN.

High availability

Because multiple servers can share the same IP address, you can use fast IP address failover to enable high availability without making a separate API call.

See also

Networking considerations for cloud servers Networking considerations for OnMetal servers Networking considerations for RackConnect PublicNet in the cloud ServiceNet in the cloud Building servers without PublicNet or ServiceNet

Customer benefits from Cloud Networks Typical use cases for Cloud Networks Security groups DNS in the cloud Gateway Instances in Rackspace Cloud

Understanding Cloud Networks introduces key ideas. To learn how to put these ideas to work, start at Actions for Cloud Networks.