You'll need the following information for your first sign on.
- Your organization URL from the Teradata Welcome Letter.
- Your organization admin username from Teradata (probably email address), either from your welcome letter or your existing Teradata login.
- If you already have a Teradata sign on (Ping/Teradata Support Portal), your existing organization admin password.
- To use a private link, you must configure your source accounts to allow outbound traffic.
- If you are not using a private link, your network must have port 1025 open to the Teradata public IP address. You may need to submit a request to your IT department to grant access.
- AWS: To use customer managed encryption keys (CMEK) for your storage data, you'll need the key ARN string. Create a single-region encryption key in AWS KMS that is created for the same region where your Teradata environment is hosted. See Finding the key ID and key ARN and Creating symmetric encryption KMS keys. See also AWS: Create a Customer Managed Encryption Key.
- Azure: This capability is in Limited Availability for interested customers. Contact your account team if you are interested in using CMEK on Azure.
To use customer managed encryption keys (CMEK) for your storage data, you'll need the key URL. Create a single-region encryption key in Azure KMS that is created for the same region where your Teradata environment is hosted. See also Azure: Create a Customer Managed Encryption Key.
During the Getting Started process, you must already have or create the following:
- The dbc password. DBC is the username for the group admin DBA with root access. You create a password for the DBC role.
- At least one database user username and password.
- IP addresses to allowlist if you don't want your database to have public access.
- Cloud service provider source accounts (to allow outbound traffic) to allowlist if you want to use a private link.