AWS Service Limits | Teradata Vantage on AWS (DIY) - 2.2 - AWS Service Limits - Teradata Vantage on AWS

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

Teradata Vantage on AWS
Release Number
Release Date
May 2021
Content Type
Publication ID
English (United States)

When you create an AWS account, AWS default service limits are set on certain resources on a per-region basis. When planning your deployment, check the limits to determine if any must be increased, especially for:

  • EBS storage (r5 instance types)
  • Quantity of EC2 instances
  • VPC elastic IP addresses

Depending on the size of your requested increase, obtaining approval from the Amazon Service Team may take more than 24 hours, so request limit increases in advance.

If your system includes m5 instance types, plan the storage configuration and calculate the total amount of EBS storage required. Compare that total with the AWS default limits for General Purpose (SSD) volume storage to determine whether to request an increase. You must increase the EBS limits in your default region as well as in any other regions where you want to deploy additional Vantage AMIs.

Before deploying a multi-node Vantage system, increase the instance limits to meet your needs. Teradata recommends increasing the limits to one more than the size of the system to support Node Failure Recovery. If you want to leave a downed node running for diagnostic purposes, Teradata recommends increasing the instance limits to two or more.

For larger systems, deployment may fail even after you increase the EBS and instance limits. This happens when sufficient resources are not available in your region and availability zone at the time of deployment. Try deploying again later, as more resources become available.