• automatic peering. The Cloud Accelerator does not use automatic peering. When you run a server in the cloud, you deploy the Cloud Accelerator to be the furthest appliance in the network, because
the Discovery Agent on the server is configured to use the Cloud Accelerator automatically. When you run a client in the cloud, and there are multiple appliances in the path to the server, the Cloud Accelerator is selected for acceleration first. You can enable automatic peering on the remote appliances to make the Cloud Accelerator peer with the furthest appliance in the network.

• simplified routing. The Cloud Accelerator for AWS is not deployed in-path, but rather in its unique out-of-path method using one interface. Simplified routing does not apply.

• WCCP/PBR/L4. The Cloud Accelerator for AWS uses a unique redirection mechanism that enables deployments in any cloud environment. The Cloud Accelerator also supports WCCP/PBR/L4 redirection when made available by the cloud provider. Amazon EC2 does not support these traditional redirection mechanisms.

• connection forwarding. The Cloud Accelerator uses a unique out-of-path method; connection forwarding does not apply.

• PFS. It is easier and simpler for you to run a separate file server instance in the cloud and not use the SteelHead for Proxy File Service (PFS).

• WAN visibility mode. The Cloud Accelerator currently supports only correct addressing. It does not support full transparency and port transparency.

• CIFS prepopulation. Typically, you configure prepopulation on the remote appliance instead of the Cloud Accelerator.