---
schema_version: "1"
id: 0d44369799b0515d8b2cf1af083f8f29c31d454f401e6b65848b32c29204ec55
title: Scaling Tableau Server on AWS
collection: tableau
version: current
locale: en-us
portal_url: https://docs.salesforce.com/tableau/current/en-us/server/ts_aws_scaling.md
canonical_url: https://help.tableau.com/current/server/en-us/ts_aws_scaling.htm
source_site: help.tableau.com
content_type: documentation
content_hash: 130f79ff5afc7f94fa98c6c41d17aa50c79205e7aaae45a497f9e51cc6893fb5
description: Deployments on public clouds continue to be supported but the content for third-party public cloud deployments is no longer updated
---
[Skip to main content](#main-content)

# Scaling Tableau Server on AWS

## This is archived content

Deployments on public clouds continue to be supported but the content for third-party public cloud deployments is no longer updated.

For the latest Tableau Server deployment content, see the [Deploy](https://help.tableau.com/current/server/en-us/install.htm) section of Tableau Server help.

For those customers who have access, we recommend Tableau Cloud. For more details, see:

- [Tableau Cloud Manual Migration Guide](https://help.tableau.com/current/guides/migration/en-us/emg_intro.htm)
- [Tableau Cloud Trial for Admin](https://help.tableau.com/current/server-linux/en-us/install.htm)
- [Tableau Cloud: Get Started for Admin](https://www.tableau.com/learn/get-started/online-admin)

## Introduction

Tableau Server is designed to scale up with more CPU cores and memory, and scale out when you add servers. This architecture allows you to maximize the use of compute resources while giving you the ability to scale massively.

To build in redundancy, you need to add additional servers, which host copies of the repository, file store, and other processes. In this scenario, you should isolate the initial server in its own node, and it should ideally run as few of the server processes as possible.

**Note:** Although you can split an 8-core license onto two 4-core machines, we recommend that you scale in increments of 8-core machines only.

## Load Balancing

On AWS, Elastic Load Balancing (ELB) automatically distributes incoming application traffic across multiple Amazon EC2 instances in the cloud. It enables you to achieve greater levels of fault tolerance in your applications, and seamlessly provides the required amount of load balancing capacity needed to distribute application traffic.

You can use ELB to distribute requests across multiple gateways in a Tableau Server cluster. In the figure below, all three nodes have gateways, which are used to route requests to available server processes. Unlike the repository process, there aren’t any passive or standby gateway processes—all gateways are active. When you add a load balancer to a Tableau Server cluster, the URL that’s accessed by Tableau Server users belongs to the load balancer, not to the initial Tableau Server.

![A flowchart that illustrates the load balancing architecture across three Tableau Servers.](/tableau/current/en-us/server/en-us/Img/ts_aws_elb.png)

## High Availability

Now that you have provided redundancy for the file store, repository, and gateway by adding additional nodes, you can additionally build redundancy for the initial Tableau Server. You can do this by creating a backup of the initial Tableau Server. Although the backup must be licensed during installation, it does not count as one of the three environments allowable under the Tableau end user license agreement (EULA).

To configure for high availability, you need to run a failover cluster. If you configure for high availability, the initial Tableau Server may be running few or no Tableau Server processes. For more information, see [High Availability](https://help.tableau.com/current/server/en-us/distrib_ha.htm) in the Tableau Server Help.