KB-1831 Cloning Appian Cloud sites FAQ

Purpose

The purpose of this article is to answer common questions involved with cloning an Appian Cloud site for troubleshooting purposes.

Table of Contents:

What is a clone?
Why does Appian Support request to create a clone?
Who has access to the code/data hosted in the clone?
How long is the cloned persisted?

What is a clone?

A clone is a replica of an existing Appian Cloud site. A new AWS instance is started, and a snapshot from the existing Appian Cloud site is used to populate the data on the new instance(s). All Appian Cloud clones are hosted in the same secure infrastructure as all other Appian Cloud sites and are subject to the same security controls.

Why does Appian Support request to create a clone?

Appian Support requests to clone a site for troubleshooting purposes. When investigating certain issues, it is sometimes necessary to run tests to gain a deeper understanding. In order to eliminate the risk of impact to an actual Appian Cloud site, it is necessary to run these tests on a clone (replica) of the environment.

Who has access to the code/data hosted in the clone?

Access to the code/data hosted in the clone is restricted to the following and is never shared with any third parties:

Those who have access to the original Appian Cloud site.
Team members from Appian Support and/or Appian Engineering that are involved in diagnosing the issue(s) reported by the customer.

How long is the cloned persisted?

The clone is persisted as long as investigation on the current issue persists. Once the investigation is complete or the investigation no longer requires the clone (or at anytime as directed by the customer), Appian will shut down the clone and delete the data.

Affected Versions

This article applies to all versions of Appian Cloud.

Last Reviewed: January 2019