As previously mentioned, Teradata MPP (multi-node) setup on AWS is a tad more involved than the previous SMP (single node) setup. Well, as we’re kind-hearted folks here at VLDB, we decided to show you how it’s done. Well, how we did it anyway.
Let’s see, if armed with an Amazon account and a credit card, you can have Teradata up and running on AWS in under an hour, as claimed by Stephen Brobst at the Teradata Partners conference recently.
Tick-tock, here goes…
Teradata AWS Marketplace
First of all, login to the AWS Management Console and select AWS Marketplace (under ‘Additional Resources’ on the right) then search for ‘Teradata Database Enterprise Edition’ in the AWS marketplace to go to the Teradata Database Enterprise Edition (1-32 nodes) page. From here you will have to subscribe to Teradata if not already done so.
Select the required ‘Region’ – in this case ‘EU(Ireland)’ – then click the ‘Continue’ button on the ‘AWS Marketplace Teradata Database Enterprise Edition (1-32 nodes)’ page to go to the ‘Launch on EC2’ page.
Launch Teradata on EC2
Set the following as required:
- Version – currently only ‘15.10.02.09-1’ available.
- Region – ‘EU (Ireland)’ is the closest region for the UK.
- Deployment – local or EBS storage and VPC options.
Click ‘Launch with CloudFormation Console’ to go to the ‘Create Stack/Select Template’ page.
AWS Cloud Formation Stack Template
Ensure you are in the correct AWS region (top right corner next to ‘Support’ drop-down) then click on ‘Next’ to go to the ‘Create Stack/Specify Details’ page.
AWS Cloud Formation Stack Details
Set the following & leave other values as default:
- Stack name – the name of the stack that will be created in CloudFormation.
- System Name – the name of the Teradata instance.
- DBC Password – the password for Teradata DBC user.
- Number of Nodes – the number of EC2 nodes required (1-32).
- Instance & Storage Type – select the EC2 instance type and storage type/size required.
- Availability Zone – choose availability zone from list.
- Remote Access From – specify CIDR block (IP range) from which SSH/DBMS access is allowed. Use 0.0.0.0/0 if required (any IP allowed) to test the setup process.
- AWS Key Pair – a pre-existing key pair must be specified.
See http://www.vldbsolutions.com/blog/teradata-on-aws-configurations-pricing/ for help on choosing EC2 instance & storage types. Apart from the number of nodes, this is the biggest driver of the cost of your Teradata on AWS stack.
Click on ‘Next’ to go to the ‘Create Stack/Options’ page.
AWS Cloud Formation Stack Options
Nothing needs to be set/changed in this page…unless you think otherwise.
Click ‘Create’ to proceed with the stack/instance creation which is monitored via CloudFormation.
AWS Cloud Formation Stack Review
There are lots of steps to go through as part of the provisioning. Once, complete the status will change to ‘CREATE_COMPLETE’:
Teradata on AWS Up and Running
Once the stack is up and running the next stage is to connect via SSH, Teradata Tools & Utilities (TTU) and a desktop SQL client. This is quite a big topic in itself and will be covered in a separate blog post.
So, to get back to Mr Brobst, we think it is possible to be up and running with Teradata on AWS in under an hour, but only if the node count is low, and only if you follow a guide that somebody has prepared…such as this one.