Licensing Issues During or After Deployment - Teradata® VantageCloud Enterprise on AWS

VantageCloud Enterprise on AWS (DIY) Installation and Administration Guide - 3.2.0.0

Deployment
VantageCloud
Edition
Enterprise
Product
Teradata® VantageCloud Enterprise on AWS
Release Number
3.2.0.0
Published
March 2026
ft:locale
en-US
ft:lastEdition
2026-04-06
dita:mapPath
cnb1751049708013.ditamap
dita:ditavalPath
eps1751058592388.ditaval
dita:id
jnv1467245119674
Product Category
Cloud

If you receive licensing errors during or after deployment, access the AWS CloudWatch logs (look for log group Teradata/DBS/stack-name and log stream telm_stack-name).

If a problem occurs during deployment, the stack is rolled back and activated licenses are automatically revoked.

During deployment, activated licenses are automatically revoked if a failure occurs. If activated licenses did not get revoked, you can revoke them manually. After revoking the licenses from the instances, you can delete the AWS CloudFormation Stack.

Following are examples of errors and possible remedies:
Errors Remedies
License doesn't have requested tier or term Make sure the term you selected when you deployed matches the email confirmation.

The VantageCloud license tier is determined when you select the AMI.

Not enough tcores available If additional TCores are needed, contact your Teradata Account Team.
DBValidateLicense In AWS CloudWatch logs, look for the log group: /aws/lambda/stack-name-DBCheckLicenseFunction
Not all nodes activated successfully Contact Teradata Services.