Before launching a Teradata Database on AWS instance, consider the implications of the available storage types, including media, capacity, data persistence, and cost related to data persistence.
Teradata Database on AWS
offers the following types of storage:
||Considerations and Use Cases|
|Amazon EC2 Instance Local Storage
||Local (both SSD and HDD)|
- Storage is ephemeral and requires a running instance
- Potential for data loss if instance fails
- Data protection available using Teradata DSC
- Lower reliability than EBS; HDD is lower reliability than SSD
- Highest performance
- Highest cost per vCPU per TB
- Up to 6.4 TB of storage per EC2 instance
- Lower performance than SSD
- Lower cost per vCPU per TB than SSD
- Up to 48 TB storage per EC2 instance
|Amazon Elastic Block Storage (EBS)
- Highest reliability
- Lower performance (network-attached)
- Lowest cost per vCPU even with extra charges for EBS
- Up to 30 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 launching a Teradata ecosystem or launching Teradata Database separately for Advanced and Enterprise tiers.
- Expand EBS storage after launching a Teradata Database instance. See Storage Expansion.
|Amazon Simple Storage Service (S3)
||Supported by Teradata Access Module for AWS, Teradata DSC, and Teradata QueryGrid.|
- Using Teradata Access Module for AWS with TPT, load and export between Amazon S3 and Teradata Database.
- Using Teradata DSC, back up and restore between Amazon S3 and Teradata Database.
- Using a Teradata QueryGrid Presto connector, query data stored in Amazon S3.
Specific storage options for Teradata Database on AWS depend on product and instance type.
See Amazon User Guide for Linux Instances.