Create an Environment: Organization Admin | Teradata VantageCloud Lake Console - Create an Environment: Organization Admin - Teradata VantageCloud Lake

Lake - Configure and Manage Your Environment and Organization

Deployment
VantageCloud
Edition
Lake
Product
Teradata VantageCloud Lake
Release Number
Published
February 2025
ft:locale
en-US
ft:lastEdition
2025-10-24
dita:mapPath
erj1683672627920.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
erj1683672627920
  1. Sign in as organization admin.
  2. Select Create then Create environment.
  3. Fill out Environment.
    Important: The Consumption estimates to your right provide guidance for configuring the environment. See Using the Consumption Estimates.
    Item Description
    Name Name for this environment
    Region The available region list was predetermined during the sales process.
    AWS: Availability zone

    Google Cloud: Zone

    Zones can enhance performance and cost efficiency.

    Select a distinct location within the selected region.

    Package Service package (varies by cloud provider)
    For more details, see your appropriate cloud service description in Knowledge Base article KB0047025, available at https://support.teradata.com.
    • Standard: Supports fewer than 10 nodes, single node cliques, same environment backup and restore
    • Lake:
      • Premier 24x7 cloud support
      • Supports up to 128 nodes, single- and multi-node cliques, Private Link connectivity, same environment backup and restore
    • Lake+:
      • Premier 24x7 Priority cloud support + industry data models
      • Supports up to 128 nodes, single- and multi-node cliques, Private Link connectivity, multiple environments backup and restore
    Key management Configure encryption for customer data.
    Important: You can select a storage encryption type only when provisioning an environment. Once provisioned, the storage encryption type cannot be changed.

    Managed by Teradata: Default. Maintains support for your platform-managed encryption key.

    Customer managed: Create and manage the encryption key within your Key Management System. Paste in the appropriate string.

    • AWS: Key Amazon Resource Name (ARN) has the following format:
      arn:aws:kms:<region>:<account-id>:key/<key-id>
      • Region must be the same as the Lake environment.
      • Key Type should be Symmetric.
      • Key Usage should be Encrypt and decrypt.

      For more details including key rotation, see Knowledge Article KB0052805, available at https://support.teradata.com. You may need to log in before searching for it.

      See AWS: Create a Customer Managed Encryption Key for instructions on the key and completing the setup.

    • Azure: Key URL (Identifier)
      https://<key_vault_name>.vault.azure.net/keys/<key_name>/<key_version>
      • Key Vault must be in the same region as the Lake environment.
      • Pricing Tier - For regular CMEK, choose Standard. Teradata supports HSM-backed keys, which is the Premium pricing tier.
      • You must enable Purge protection to use CMEK.

      See Azure: Create a Customer Managed Encryption Key for instructions on the key and completing the setup. (Azure: CMEK is in limited availability. Contact your account team.)

    • Google Cloud: Key Resource Name:
      projects/<CUSTOMER_PROJECT_ID>/locations/<REGION>/keyRings/<KEY_RING_NAME>/cryptoKeys/<KEY_NAME>/cryptoKeyVersions/<KEY_VERSION>
      • KMS Key Ring must be in the same region as the Lake environment.
      • Encryption key must be configured with ENCRYPT_DECRYPT.
      • You must include the key version in the key resource name using this format: cryptoKeyVersions/<KEY_VERSION>

      See Google Cloud: Create a Customer Managed Encryption Key for instructions on the key and completing the setup.

  4. Fill out Primary cluster.
    Important: The Consumption estimates to your right provide guidance for configuring the environment. See Using the Consumption Estimates.
    Item Description
    AWS: Type
    • Standard: General-purpose option to provide balanced performance for a wide range of workloads.
    • High I/O: Suitable for workloads with high I/O requirement. Available in select AWS regions and availability zones.
    Instance size Available instance sizes vary by cloud service provider.

    For unit consumption rates, see your appropriate cloud service description and addendum in Knowledge Base article KB0047025, available at https://support.teradata.com.

    Instance count 2 to 128

    Number of nodes in the primary cluster. The available number may vary by cloud service provider.

    Total storage in TB 1 to 72TB per instance. For example, for 2 instances, enter 2 to 144TB.
  5. Fill out Database credentials.
    Item Description
    DBC Password The DBA (group administrator and root user) for the environment is called "dbc". This user owns all space in the system and has root access to the database. Set the password for dbc.
    • At least one non-blank character (trailing blanks are ignored)
    • Between 8 and 64 characters
    • Alphanumeric and special characters
    • Cannot contain double quotation marks (")
  6. [Optional] Advanced options: Select Use defaults or choose additional options.
    Important: The Consumption estimates to your right provide guidance for configuring the environment. See Using the Consumption Estimates.
    Item Description
    AMPs per instance
    Important: Consult with Teradata before modifying this option so improper configuration doesn't impact your primary cluster.

    Select the number of AMPs per instance for the instance size you selected.

    AWS: Storage type
    • General purpose SSD (gp3): Default
    • Provisioned IOPS SSD (io2 Block Express)
    • Both General purpose SSD and Provisioned IOPS SSD are supported for fewer than 10 nodes.
    • For 10 or more nodes, only Provisioned IOPS SSD storage is supported.
    • Provisioned IOPS SSD is required for multi-node cliques.
  7. Review the information and select Create.
    Deployment takes a few minutes.