Configure Confluence Data Center on one node.

Deploy into your existing ASI (takes about 20 minutes).

Deploy into a new ASI (takes about 40 minutes).

You can choose to build a new Atlassian Standard Infrastructure (ASI) for your deployment or deploy Confluence into your existing ASI:

If you don't already have an AWS account, sign up at, and sign in to your account.The deployment process includes these steps:

To build your Confluence Data Center cluster on AWS, follow the instructions in the deployment guide. By default, CloudWatch also collects and stores logs from each monitored node. Amazon CloudWatch, which provides basic monitoring for all application and database nodes in the deployment.Amazon Elastic File System (Amazon EFS) as the shared file system for storage.You can choose to use Amazon Aurora PostgreSQL instead. Amazon Relational Database Service (Amazon RDS) PostgreSQL as the external database for Confluence.A Confluence cluster with instances based on Amazon Linux.A Linux bastion host to enable secure access to Confluence Data Center.*.Managed network address translation (NAT) gateways to allow outbound internet access for resources in the private subnets.*.An Application Load Balancer, which also serves as a Secure Sockets Layer (SSL) termination proxy.This provides the network infrastructure for your Confluence deployment.* A virtual private cloud (VPC) configured with public and private subnets.Note: Accessing Confluence from a URL that is not the configured base URL is not supported.Use this Quick Start to set up the following Confluence Data Center environment on AWS: After configuring your Confluence server base URL to use HTTPS, access your Confluence via the configured base URL (exactly as it's set). Ensure that you are accessing your Confluence server via the configured base URL.Refer to step 4, 'Change your Confluence Base URL to HTTPS'. For detailed information, see to the following Atlassian HTTPS configuration documentation. Ensure that your Confluence server base URL is configured to use HTTPS.These problems are typically caused by an incorrectly configured Confluence server base URL. Typically, these problems manifest themselves as timeouts when users launch the Gliffy editor. However, some Confluence users may encounter problems when using Gliffyover an HTTPS / SSL connection.

The Gliffy for Confluence plugin supports secure HTTPS / SSL connections. Using Gliffy Atlassian plugins with HTTPS / SSL