This page applies to Appian Cloud only. It may not reflect the differences with Appian Government Cloud.
Appian Cloud environments that only allow Private Access (i.e. inbound access enabled only through VPN or PrivateLink) require additional networking considerations in order to leverage Appian DevOps features such as Compare and Deploy Across Connected Environments.
The Connected Environments for Private Access feature provides a simple-to-configure way to enable connectivity between two environments with Private Access. This is configured by enabling two way HTTPs traffic between your nominated environments. The HTTPs traffic between these environments will flow through the AWS internal network and will not traverse the public internet.
The diagram below shows how HTTPS traffic would flow between two environments with Connected Environments for Private Access enabled.
Your elected environments must meet the following prerequisites to enable Connected Environments for Private Access:
Appian Support will work with you through the following configuration procedure.
|Create a support case||Create a support case with Appian to enable Connected Environments for your Private Access environments. Provide a list of environments for which to enable Connected Environments.||Customer|
|Verify configurations and schedule maintenance window||Appian Support will verify the configurations and work with you to schedule maintenance windows for the affected environments.||Appian|
|Enable DevOps features||Configure DevOps features on your environments.||Customer|
Configuring Connected Environments for Private Access