Configuring Teradata Managed OTF Access | Teradata Managed OTF - Configuring Teradata Managed OTF Access - Teradata Vantage

Teradata® Open Table Format for Apache Iceberg and Delta Lake User Guide

Deployment
VantageCloud
VantageCore
Edition
VMware
Enterprise
IntelliFlex
Lake
Product
Teradata Vantage
Release Number
20.00
Published
October 2025
ft:locale
en-US
ft:lastEdition
2026-06-17
dita:mapPath
qrj1749167830193.ditamap
dita:ditavalPath
lli1749584660955.ditaval
dita:id
bsr1702324250454

The customer DBA logs in to the database and creates the Data Lake database (if it does not already exist) before creating a Teradata Managed OTF table. The Data Lake database can use the same name as the Teradata database or a different name.

If the Data Lake database name is different from the Teradata database name, you must specify this new name in the TableProperties.

Follow these steps for granting cross-account access using an IAM role:

  1. An administrator (or authorized identity) in the account that owns the external bucket (Account A) creates an IAM role.
  2. The administrator in Account A attaches a permissions policy to the role, granting cross-account access to the required resource.
  3. A trust policy is added to the role, specifying an IAM identity in the Teradata cluster account (Account B) as the trusted principal allowed to assume the role.
  4. A DBA in Account B delegates permissions to the EC2 instance using an authorization object. This enables the EC2 instance to assume the IAM role created in Account A, thereby gaining access to the external resource.