|
This page applies to Appian Cloud only. It may not reflect the differences with Appian Government Cloud. |
Appian Cloud offers multiple ways to connect to resources that are in your self-managed network or in your private cloud.
Appian Cloud offers two different types of connections: IPSec VPN connections and AWS PrivateLink
IPSec VPN connections enable access to computer resources on a private network from an Appian Cloud instance. Each Appian Cloud instance can have multiple VPN tunnels enabled to securely integrate with resources in different networks.
We offer two different types of IPSEC VPNs:
Customers of Appian Cloud can use AWS PrivateLink to enable secure access from their Appian Cloud instances to their AWS resources hosted on their private networks. PrivateLink can be used to integrate with customer-owned services such as business data sources or authentication systems (LDAP or Single sign-On) through a customer's AWS Virtual Private Cloud (VPC). This integration option is an alternative to VPN Tunnels for customers who have IT infrastructure running on AWS.
The table below lists the differences between VPNs and PrivateLink.
| Static VPN | Dynamic VPN | PrivateLink | |
|---|---|---|---|
| Private DNS | Private DNS is permitted with the use of Static VPN. | Private DNS is permitted with the use of Dynamic VPN. | Custom DNS is allowed with the use of PrivateLink. |
| Type of Connection | Policy based static VPN tunnel. | Route based dynamic VPN connection. | AWS PrivateLink connection between Appian VPC and Customers VPC. |
| Failover Capabilities | Failover may be established by creating an additional VPN tunnel per application server and relies on a ping test to determine when to failover. | Failover is established automatically and happens during a predefined time frame. | Failover is not configurable for PrivateLink. |
| Number of VPN Tunnels Needed | Each application server will require their own VPN tunnel. If failover is required, each application server will require two total VPN tunnels. | At most, for each site there will be two connections | N/A |
| Connection Type | Bidirectional VPN tunnel which can be used to connect to Appian from a customer managed network or to connection from Appian to resources on the customer managed network. | Bidirectional VPN tunnel which can be used to connect to Appian from a customer managed network or to connection from Appian to resources on the customer managed network. | Bidirectional connection from Appian to customer managed VPC and customer managed VPC to Appian (using separate configurations). |
| Steps to Get Started | Review the following documentation on Static VPN. | Review the following documentation on Dynamic VPN. | Review the following documentation on PrivateLink. |
