EBS is ideal if you want persistent data for production systems. The root volume for an instance and additional EBS volumes that you attach to the instance persist by default. Unless you set attached volumes to delete on termination, all data remains and storage-related charges continue to accrue. You can enable EBS storage deletion either when configuring an instance or after deploying an instance.
Consider the following when choosing the EBS storage.
- Highest reliability
- Lower performance (network-attached)
- Lowest cost per vCPU even with extra charges for EBS
- Up to 72 TB remote storage (pre-provisioned) on SSD volumes attached to the instance
- Data persists independent of running an instance which provides the ability to shut down an instance between sessions to reduce EC2 costs and lower cost of ownership
- Total node storage size for EBS instance types can be set using the Data Storage parameter when deploying Vantage for Advanced and Enterprise tiers.
- Expand EBS storage after deploying a Vantage instance.
For Vantage, only R5 and R6i instance types on AWS support EBS storage. Instance types supporting EBS storage may vary across other Vantage products.
Teradata recommends R5 and R6i instance types if you are deploying Vantage MPP instances. Vantage runs at the speed of the slowest node so using any of these EBS optimized instance types is important to get the maximum EBS volume bandwidth for your instance.
Manually attaching EBS volumes to your instance on Linux and updating the /etc/fstab file can result in data loss or corruption. EBS volumes are automatically attached at the time the instance is deployed.
For EBS volume type performance characteristics, see Amazon EBS Product Details.