AWS Service Limits
When you create an AWS account, AWS sets default service limits on certain resources on a per-region basis. When planning your deployment, check the limits to determine if any should be increased, especially for:
- EBS storage (m4 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 can take more than 24 hours, so request limit increases in advance of the time you need them.
If your system will include m4 instance types, plan the storage configuration and calculate the total amount of EBS storage required. (See Teradata Database Instance Types.) Compare that total with the AWS default limits for General Purpose (SSD) volume storage to determine whether you must 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 Teradata Database AMIs.
Before deploying a multi-node Teradata Database instance, 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 even further, to two or more.
For larger systems, deployment can still 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 can become available.