AWS Service Limits | Teradata VantageCloud Enterprise on AWS (DIY) - AWS Service Limits - Teradata® VantageCloud Enterprise on AWS

VantageCloud Enterprise on AWS (DIY) Installation and Administration Guide - 2.4

Deployment
VantageCloud
Edition
Enterprise
Product
Teradata® VantageCloud Enterprise on AWS
Release Number
2.4
Published
April 2024
Language
English (United States)
Last Update
2024-07-15
dita:mapPath
kma1662437965174.ditamap
dita:ditavalPath
nat1649317391363.ditaval
dita:id
jnv1467245119674
Product Category
Cloud

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 and R6i 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.

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.