|
This page applies to Appian Cloud only. It may not reflect the differences with Appian Government Cloud. |
Appian Cloud's content delivery network (CDN) is designed to deliver web content to users as securely, quickly, and reliably as possible no matter where they are located.
Content that changes based on factors such as user input and permissions. For example, data fetched from an upstream service, application server, or a Web API.
Web assets, such as images, JavaScript, and CSS, that are the same for all users of an Appian service and do not change based on input. See static content delivery for more information.
Caution: Appian Cloud uses dynamic IP addresses for public inbound web traffic which are subject to change without notice.
Relying on specific IP addresses or Classless Inter-Domain Routing (CIDR) ranges to restrict access from your corporate network is not recommended, as it could impact the access to and functionality of your Appian Cloud environment when they change.
As traffic increases, resource capacity automatically scales to ensure performance and reliability are not affected by volume.
Appian Cloud continuously monitors the health of its web servers and automatically replaces them as needed to ensure resiliency to hardware failures.
In the event of an application server hardware failure or availability zone failure on environments configured with High Availability (HA), web servers will intelligently route traffic to the healthy environments or zones. See High Availability for Appian Cloud for more information.
Appian Cloud has Denial of Service (DoS) protections to help ensure its availability and security. If an environment experiences an unusually high level of traffic, the DoS protections may be triggered. In the event that DoS protections are triggered, new requests to the affected environment may be blocked until the in-flight requests are completed or the high load subsides.
HTTP Strict Transport Security (HSTS) enforces the use of HTTPS for incoming web requests as a security best practice, ensuring all traffic between a web client and Appian Cloud is end-to-end encrypted.
Additionally, all environments using the default Appian Cloud domains have their URLs preloaded so that browsers will automatically use HTTPS for the initial request, even if the client specifies HTTP.
Tip: Preloading is not supported for portals.
Based on your security and compliance needs, you can configure your Appian Cloud environments to restrict access to specific Trusted IPs.
Appian Cloud Content Delivery
