KB-1831 Cloning Appian Cloud Sites FAQ

Kaushal Patel — Thu, 30 Apr 2026 13:55:25 GMT

Current Revision posted to Appian Knowledge Base by Kaushal Patel on 4/30/2026 1:55:25 PM

Purpose

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

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 an existing (host) Appian Cloud site is used to populate data on the new instance(s) creating a new separate site. All Appian Cloud clones are hosted in the same secure infrastructure as other Appian Cloud sites and are subject to the same security compliance protocols and 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 test and debug directly to better understand the nature and scope of the behavior. In order to eliminate the risk of impact to an actual Appian Cloud site, it is necessary to run these tests on a clone of the environment.

What data will be cloned?
As a clone is created from a snapshot of a host site, all data as it exists at the time of the snapshot on the host site will be copied and present on the clone. For example, all Appian objects will be included, but not data hosted externally in customer databases.

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 groups and is never shared with any third parties to ensure data integrity:

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

Do clones have any impact on the host Appian Cloud site or other existing environments?
No, clone sites exist separately outside of the host site and other existing Appian Cloud environments. Furthermore, outbound activity (emails, traffic, etc.) will be disabled as to not interfere with external systems.

How long is the clone and its data persisted?
The clone is persisted as long as the investigation into the current issue persists. Once the investigation is complete or no longer requires access to the clone, Appian will shut down the clone and delete its corresponding data. The clone can also be shut down at any time at the customer's discretion.

Affected Versions

This article applies to all versions of Appian Cloud.

Last Reviewed: April 2026

Tags: administration, Security, infrastructure, Cloud

KB-1831 Cloning Appian Cloud sites FAQ

Rebecca Jonas — Thu, 03 Jan 2019 16:54:02 GMT

Revision 12 posted to Appian Knowledge Base by Rebecca Jonas on 1/3/2019 4:54:02 PM

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

Tags: administration, Security, infrastructure, Cloud

KB-1490 Cloning Appian Cloud sites FAQ

Rebecca Jonas — Thu, 03 Jan 2019 11:43:43 GMT

Revision 11 posted to Appian Knowledge Base by Rebecca Jonas on 1/3/2019 11:43:43 AM

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?

Why does Appian Support request to create a clone?

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?

Affected Versions

This article applies to all versions of Appian Cloud.

Last Reviewed: January 2019

Tags: administration, Security, infrastructure, Cloud

DRAFT KB-XXXX Cloning Appian Cloud sites FAQ

Rebecca Jonas — Thu, 03 Jan 2019 11:41:15 GMT

Revision 10 posted to Appian Knowledge Base by Rebecca Jonas on 1/3/2019 11:41:15 AM

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?

Why does Appian Support request to create a clone?

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?

Affected Versions

This article applies to all versions of Appian Cloud.

Last Reviewed: January 2019

Tags: administration, Security, infrastructure, Cloud

DRAFT KB-XXXX Cloning Appian Cloud sites FAQ

Jordan Horwat — Thu, 03 Jan 2019 11:35:28 GMT

Revision 9 posted to Appian Knowledge Base by Jordan Horwat on 1/3/2019 11:35:28 AM

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?

Why does Appian Support request to create a clone?

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 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

Tags: administration, Security, infrastructure, Cloud

DRAFT KB-XXXX Cloning Appian Cloud sites FAQ

Jordan Horwat — Thu, 03 Jan 2019 11:29:15 GMT

Revision 8 posted to Appian Knowledge Base by Jordan Horwat on 1/3/2019 11:29:15 AM

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?

Why does Appian Support request to create a clone?

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 investigation on the current issue persists. Once the investigation is complete or the investigation no longer requires the clone, Appian will shut down the clone and delete the data (or at anytime as directed by the customer).

Affected Versions

This article applies to all versions of Appian Cloud.

Last Reviewed: January 2019

Tags: administration, Security, infrastructure, Cloud

DRAFT KB-XXXX Cloning Appian Cloud sites FAQ

Jordan Horwat — Thu, 03 Jan 2019 09:40:39 GMT

Revision 7 posted to Appian Knowledge Base by Jordan Horwat on 1/3/2019 9:40:39 AM

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?

Why does Appian Support request to create a clone?

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. The Solution Engineer assigned to the case manages this individual-level access in coordination with the customer.

How long is the cloned persisted?

Affected Versions

This article applies to all versions of Appian Cloud.

Last Reviewed: January 2019

Tags: administration, Security, infrastructure, Cloud

DRAFT KB-XXXX Cloning Appian Cloud sites FAQ

Jordan Horwat — Wed, 02 Jan 2019 09:49:58 GMT

Revision 6 posted to Appian Knowledge Base by Jordan Horwat on 1/2/2019 9:49:58 AM

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?
What code/data is shared when a clone is created?
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 server(s). All Appian Cloud clones are hosted in the same secure infrastructure as all other Appian Cloud sites and 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 harm 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?

Only those who have access to the original Appian Cloud site will have access to the code/data hosted in the clone.

What code/data is shared when a clone is created?

The code/data hosted in the clone is NOT shared with anyone who does not have access to the original Appian Cloud site.

How long is the cloned persisted?

Affected Versions

This article applies to all versions of Appian Cloud.

Last Reviewed: January 2019

Tags: administration, Security, infrastructure, Cloud

DRAFT KB-XXXX Cloning Appian Cloud sites FAQ

Jordan Horwat — Wed, 02 Jan 2019 09:49:25 GMT

Revision 5 posted to Appian Knowledge Base by Jordan Horwat on 1/2/2019 9:49:25 AM

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?
What code/data is shared when a clone is created?
How long is the cloned persisted?

What is a clone?

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 harm 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?

Only those who have access to the original Appian Cloud site will have access to the code/data hosted in the clone.

What code/data is shared when a clone is created?

The code/data hosted in the clone is NOT shared with anyone who does not have access to the original Appian Cloud site.

How long is the cloned persisted?

Affected Versions

This article applies to all versions of Appian Cloud.

Last Reviewed: December 2018

Tags: administration, Security, infrastructure, Cloud

DRAFT KB-XXXX Cloning Appian Cloud sites FAQ

Jordan Horwat — Wed, 02 Jan 2019 09:48:26 GMT

Revision 4 posted to Appian Knowledge Base by Jordan Horwat on 1/2/2019 9:48:26 AM

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?
What code/data is shared when a clone is created?
How long is the cloned persisted?

What is a clone?

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 harm 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?

Only those who have access to the original Appian Cloud site will have access to the code/data hosted in the clone.

What code/data is shared when a clone is created?

The code/data hosted in the clone is NOT shared with anyone who does not have access to the original Appian Cloud site.

How long is the cloned persisted?

Affected Versions

This article applies to all versions of Appian Cloud.

Last Reviewed: December 2018

Tags: administration, Security, infrastructure, Cloud

DRAFT KB-XXXX Cloning Appian Cloud sites FAQ

Jordan Horwat — Mon, 31 Dec 2018 16:03:31 GMT

Revision 1 posted to Appian Knowledge Base by Jordan Horwat on 12/31/2018 4:03:31 PM

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?

What code/data is shared when a clone is created?

Why does Support request to create a clone?

Who has access to this code/data?

How long is the cloned persisted?

1) Who will have access to the code and data

2) That all code and data will not be shared

3) That all cloned code and data will be destroyed before the closure of this ticket

DRAFT KB-XXXX Cloning Appian Cloud sites FAQ

Jordan Horwat — Mon, 31 Dec 2018 13:34:06 GMT

Revision 3 posted to Appian Knowledge Base by Jordan Horwat on 12/31/2018 1:34:06 PM

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?
What code/data is shared when a clone is created?
How long is the cloned persisted?

What is a clone?

A clone is a replica of an existing Appian Cloud site. A new AWS instances is started, and a snapshot from the existing Appian Cloud site is used to populate the data on the new server(s). All Appian Cloud clones are hosted in the same secure infrastructure as the original Appian Cloud environments.

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 harm 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?

Only those who have access to the original Appian Cloud site will have access to the code/data hosted in the clone.

What code/data is shared when a clone is created?

The code/data hosted in the clone is NOT shared with anyone who does not have access to the original Appian Cloud site.

How long is the cloned persisted?

Affected Versions

This article applies to all versions of Appian Cloud.

Last Reviewed: December 2018

Tags: administration, Security, infrastructure, Cloud

DRAFT KB-XXXX Cloning Appian Cloud sites FAQ

Jordan Horwat — Mon, 31 Dec 2018 12:42:50 GMT

Revision 2 posted to Appian Knowledge Base by Jordan Horwat on 12/31/2018 12:42:50 PM

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?
What code/data is shared when a clone is created?
How long is the cloned persisted?

What is a clone?

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 harm 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?

Only those who have access to the original Appian Cloud site will have access to the code/data hosted in the clone.

What code/data is shared when a clone is created?

The code/data hosted in the clone is NOT shared with anyone who does not have access to the original Appian Cloud site.

How long is the cloned persisted?

The clone is persisted as long investigation on the current issue persists. Once the investigation is complete, Appian will shut down the clone and delete the data.

Affected Versions

This article applies to all versions of Appian Cloud.

Last Reviewed: December 2018

Tags: administration, Security, infrastructure, Cloud