Considerations and Limitations - Teradata Software for AWS

Teradata Vantageā„¢ on AWS (DIY) Installation and Administration Guide

Product
Teradata Vantage on AWS
Release Number
5.08
Published
November 2018
Language
English (United States)
Last Update
2018-11-07
dita:mapPath
upc1519757374969.ditamap
dita:ditavalPath
TeradataAWS_PubCloud_5.08.ditaval
dita:id
B035-2800
lifecycle
previous
Product Category
Cloud
Consider the following limitations before deciding to scale out or scale in.
Considerations Limitations
Database license tier Developer tier is not supported.
Maximum node limit Do not scale out the system beyond the maximum node limit.

For BYOL, make sure you have enough TCores before you scale out the system.

Maximum volume count per node limit Do not scale in the system if it increases the volume count beyond 24 per instance.
Maximum scale out limit Do not scale out the system beyond the maximum node count limit. You cannot go beyond the minimum storage subpool count of 2 per node.

Do not scale out beyond four times the size of a deployed 24-AMPs-per-node system. There are 3 AMPs in a storage subpool. With 24 AMPs per node in an initial system deployment, there are 8 storage subpools per node.

Minimum scale in limit Do not scale in the system beyond the maximum storage subpool count of 8 per node.
Power of two scaling limit A system can be scaled out only two times (2x) the size, which doubles the total node count (half the EBS storage) or four times (4x) the size, which quadruples the total node count (quarter the EBS storage).

Assuming a system was previously scaled out, it can be scaled in only two times (2x, scale factor x/2) or four times (4x, scale factor x/4).