Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://developer.hashicorp.com/terraform/enterprise/deploy/configuration/storage/connect-object below:

Configure data object storage | Terraform

This topic describes how to configure Terraform Enterprise to connect to an external data object service. This step is only required when Terraform Enterprise is configured to operate in external or active-active mode. Refer to Data storage settings overview for additional information.

Terraform Enterprise stores artifacts that it produces during operation, such as state files, plan files, run logs, and configuration versions, in an S3-compatible storage service. Complete the following steps to configure the connection to an externally-managed data object storage system:

1. In your object storage service, create a dedicated user that has permissions to access and manage the storage resources. Refer to the documentation for your object storage service for instructions.
2. Configure the connection settings in the Terraform Enterprise deployment configuration.

• Any S3-compatible object storage service, GCP Cloud Storage, or Azure blob storage.
• A bucket on the object storage platform for Terraform Enterprise to use. Your infrastructure provider may require the bucket to be in the same region as the Terraform Enterprise instance.
• Disable any lifecycle rules that would delete, archive, or transition objects in the object storage container. Terraform Enterprise expects to manage all data in the object storage service, so any lifecycle operations may result in unexpected data inconsistencies.

1. Add the TFE_OBJECT_STORAGE_TYPE variable to the configuration and set one of the following storage types:

   • s3: Stores objects in an AWS S3 bucket.

   • azure: Stores objects in an Azure blob.

   • google: Stores objects in Google's cloud platform.

     Refer to the TFE_OBJECT_STORAGE_TYPE reference documentation for additional information.

2. When using S3 in IPv6-only networks, you must also set the TFE_OBJECT_STORAGE_S3_ENDPOINT to "s3.dualstack.us-west-2.amazonaws.com". Refer to Enable IPv6 for additional information.

3. Configure the connection settings for the object type.

   ...
   env:
     variables:
       TFE_OBJECT_STORAGE_TYPE: s3
       TFE_OBJECT_STORAGE_S3_BUCKET: <S3 bucket name>
       TFE_OBJECT_STORAGE_S3_REGION: <S3 region>
       TFE_OBJECT_STORAGE_S3_USE_INSTANCE_PROFILE: <Enables AWS authentication using the default credential chain, including instance profile and pod identity>
     secrets:
       TFE_OBJECT_STORAGE_S3_ACCESS_KEY_ID: <Required when TFE_OBJECT_STORAGE_S3_USE_INSTANCE_PROFILE is false>
       TFE_OBJECT_STORAGE_S3_SECRET_ACCESS_KEY: '<Required when TFE_OBJECT_STORAGE_S3_USE_INSTANCE_PROFILE is false>'
   

   Refer to the S3-compatible storage configuration reference for information about all available settings.

   ...
   env:
     variables:
       TFE_OBJECT_STORAGE_TYPE: azure
       TFE_OBJECT_STORAGE_AZURE_ACCOUNT_NAME: <Azure storage account name>
       TFE_OBJECT_STORAGE_AZURE_CONTAINER: <Azure storage container name>
       TFE_OBJECT_STORAGE_AZURE_ENDPOINT: <Azure storage endpoint>
     secrets:
       TFE_OBJECT_STORAGE_AZURE_ACCOUNT_KEY: '<Azure storage account key>'
   

   Refer to the Azure blob storage configuration reference for information about all available settings.

   ...
   env:
   variables:
   TFE_OBJECT_STORAGE_TYPE: google
   TFE_OBJECT_STORAGE_GOOGLE_BUCKET: <Bucket name>
   TFE_OBJECT_STORAGE_GOOGLE_PROJECT: <GCP project ID>
   secrets:
   TFE_OBJECT_STORAGE_GOOGLE_CREDENTIALS: <BASE_64_ENCODED_SERVICE_ACCOUNT_CREDENTIALS>
   

   Refer to the Google cloud platform storage configuration reference for information about all available settings.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4