Launching Teradata Database Using CloudFormation
For BYOL, read Bring Your Own License before launching TeradataDatabase.
This procedure provides an option to create a placement group.
This procedure provides an option to encrypt your data volumes. To encrypt the root drive, see Encryption.
- If you have not subscribed to the software, do so now.
- From the AWS Marketplace, select Your Marketplace Software from your account menu in theupper-right corner.A list of your software subscriptionsappears.
- Click Launch MoreSoftware under the subscription name.
- Under Software Pricing,select your subscription term.
- Under Version, select theTeradata Database release version from which to launch the instance.
- Under Region, select aregion.See AWS Regions.
- Under Deployment Options,select Teradata Database local/EBS storage -existing VPC.See Database Templates.
- Under Launch, clickLaunch with CloudFormationConsole.The Select Templatepage appears and the template URL is automatically specified under Specify an Amazon S3 template URL based on yourselection at the previous step.
- Click Next.
- Under Specify Details,type a stack name.NoteThe stack name must be unique to your region orthe launch will fail.
- Under Parameters,specify the following values for the Teradata Database instance:
Parameter Category Parameter Name Action Licensing [BYOL only] EID Enter the entitlement ID which is a unique string of characters that enable you to use the licensed software. Obtain the EID from the email you received when you purchased the license. Term Select one of thefollowing for the license period:
- POC: Short-term license (30, 60 or90 days) used for a proof-of-concept
Obtain the term from the email youreceived when you purchased the license.
The term is visible as a suffix to thename in the Product column after you log in to theTeradata EMS server.
Teradata Database System Name Enter a Teradata Databasesystem name. DBC Password Enter a new defaultTeradata Database password. For security reasons, westrongly recommend you change the default dbc password to a differentpassword. Japanese Support Select yes to optimize the hashingalgorithm to spread data across all AMPs when using Kanjicharacters for primary indexes. The default setting isno. NTP Servers Enter the NTP servers,separated by commas. System Timezone [Optional] Enter theoperating system time zone of the database system. Thedefault is the timezone of the AWS region. Enable Secure Zones Select yes to change the defaultsetting to enable the Teradata Secure Zones databasefeature. The default setting is no. Enable Row-LevelSecurity Select yes to change the defaultsetting to enable the Teradata Row-Level Security databasefeature. The default setting is no. Enable Teradata Intelligent Memory
[Advanced and Enterprise tiers only]
Do one of the following:
- To disable Teradata IntelligentMemory, leave the default cache percent as 0.
- To enable Teradata IntelligentMemory, type a cache percent from 1 to 80 to specifythe size of the hot cylinder cache as a percentageof FSG cache.
See the ctl utility in Utilities and the Teradata Intelligent Memory Orange Book.
Node Configuration Number of Nodes Enter the number of nodes to launch for this stack.
The number of supported nodes depends on the license tier. See Teradata Database License Tiers.
If you are launching into an unfolded state, your node count must be a multiple of 2 (2x) or a multiple of 4 (4x).
Instance and StorageType Select an instance typefor the storage type you want. The storage size is per node.See Supported Instance Types. Fold / Unfold
[Advanced and Enterprise tiers only]
Do one of the following:NoteIf you choose not to unfold during launch, you can do so after launching. See Unfolding a System.
- Select None to disable this feature (default).
- Select Unfold-Ready to automatically allocate extra IP addresses from the subnet. This ensures the IP addresses used to connect to the Teradata Database for client connectivity do not change when the system is unfolded.
The initial state for a system has 4 secondary IP addresses per node.The following examples are for launching a 4-node system:
- When the system unfolds to 2x, then 8 nodes and 2 secondary IP addresses are assigned to each node.
- When the system unfolds to 4x, then 16 nodes and 1 secondary IP address is assigned to each node.
Clients will still use the same 16 IPs to connect to the Teradata Database system in both of the examples.
If you do not select this option now, you can allocate IP addresses after launching. See Configuring COP Entries.
- Select Unfolded-2x to launch half of the EBS volumes, enabling you to later fold the system after launching. See Folding a System.
- Select Unfolded-4x to launch a quarter of the EBS volumes, enabling you to later fold the system after launching. See Folding a System.
Data Storage [Advanced and Enterprise tiers only] Enter the total nodestorage size from 5 to 60 TB per node for EBS instance typesonly. EBS Encryption
[Advanced and Enterprise tiers only]
Do one of thefollowing:
- Select Yes to encrypt your EBS data volumes.
- Select No to not encrypt your EBS data volumes.
VPC/Network VPC Search or select anexisting virtual private cloud in which the system will belaunched. Database Subnet Select a subnet to usefor the database.
Ensure the subnet youselect has a sufficient number of IPs available. TheTeradata Database MPP instances require two IPs per nodeand all AWS subnets have 5 IPs reserved for internaluse.
See VPC and Subnet Sizing inthe Amazon Virtual Private Cloud User Guide.
Checkthat the subnet you choose has enough available IPs.From the AWS Web Console, under Networking, selectVPC. UnderResources,select Subnets.Check the AvailableIPs column for that specificsubnet.
Database PlacementGroup Do one of thefollowing:
- Enter the name of the existingplacement group.
- Leave it blank to not use aplacement group.
Elastic IPs Select if you want toallocate an elastic IP address to each node.
These will not be deleted when thestack is removed.
Recommended forMinimum Production and Full Production Teradataecosystems. See Elastic IP Addresses.
SecurityGroup Remote Access From Enter a CIDR block tolock down SSH and enable access to the Teradata Databasenodes. See Security Groups for Teradata Database. KeyPair AWS Key Pair Enter or select the keypair to SSH into for the instances.
- Click Next.The Options pageappears.
- [Optional] Under Tags,specify up to 50 unique key-value pairs for resources in your stack, allowingyou to search at a later time for the resources you launched.
- [Optional] Under Permissions, select an IAM role.You can click Learnmore to get more information.
- [Optional] Under Advanced, set additional options for your stack, such asnotifications and a stack policy.
You can click Learnmore to get more information.
- Click Next.The Review pageappears.
- Review the information carefully to ensure it is correct, andselect the standard AWS I acknowledgecheck box at the bottom.
- Click Create tocreate the stack.This process can take anywhere between several minutes up toan hour depending on your configuration.NoteTrying to SSH into the instance may cause the creation of thestack to fail. Do not try to SSH into the instance until eitherCREATE_COMPLETE displaysin the Status column or you receive afailure notification.
- [Optional] To monitor the stack creation progress, do thefollowing:
- From the AWS CloudFormation console, ensureCREATE_IN_PROGRESSdisplays in the Statuscolumn.
- After the stack is created, ensure CREATE_COMPLETE displays in theStatus column.
- From the AWS EC2 Console, click Instances in the left column and ensureyour instances are listed under the Name column.The name appears as the stack name followed by thenode name.
- [Optional] To SSH into the system with the public IP/DNS ofany of the nodes, type the following command:
ssh -i private-key-file ec2-user@instance-DNS-name or IP-addressAfter the stack is created, Teradata Database is readyand is started. No additional configuration is required. You do not need to runtdc-init or tdc-start.
- [BYOL only] If you receive licensing errors, see Licensing Issues.
- [BYOL only] Continuously monitor the AWS CloudWatch logs forerrors, warnings, and alerts until you stop or terminate your instance.See Accessing AWS CloudWatch Logs (look for log group Teradata/DBS/stack-name and log stream telm_stack-name).