confluent_network_link_endpoint
provides a Network Link Endpoint resource that enables creating, editing, and deleting Network Link Endpoints on Confluent Cloud.
resource "confluent_network_link_endpoint" "nle" {
display_name = "nle1"
description = "TEST-NLE1"
environment {
id = "env-xyz456"
}
network {
id = "n-abc123"
}
network_link_service {
id = "nls-g3e1ox"
}
}
output "network_link_endpoint" {
value = confluent_network_link_endpoint.nle
}
The following arguments are supported:
display_name
- (Optional String) The name of the Network Link Endpoint.description
- (Optional String) The description of the Network Link Endpoint.network
(Required Configuration Block) supports the following:
id
- (Required String) The ID of the Network that the Network Link Endpoint belongs to, for example, n-abc123
.network_link_service
(Required Configuration Block) supports the following:
id
- (Required String) The ID of the Network Link Service, for example, nls-g3e1ox
.environment
(Required Configuration Block) supports the following:
id
- (Required String) The ID of the Environment that the Network Link Endpoint belongs to, for example, env-xyz456
.In addition to the preceding arguments, the following attributes are exported:
id
- (Required String) The ID of the Network Link Endpoint, for example, nle-abc123
.resource_name
(Required String) The Confluent Resource Name of the Network Link Endpoint.You can import a Network Link Endpoint by using Environment ID and Network Link Endpoint ID, in the format <Environment ID>/<Network Link Endpoint ID>
. The following example shows how to import a Network Link Endpoint:
$ export CONFLUENT_CLOUD_API_KEY="<cloud_api_key>"
$ export CONFLUENT_CLOUD_API_SECRET="<cloud_api_secret>"
$ terraform import confluent_network_link_endpoint.my_nle env-abc123/nle-abc123
The following end-to-end examples might help to get started with confluent_network_link_endpoint
resource:
cluster-link-over-aws-private-link-networks
: Cluster link over two dedicated clusters in separate AWS PrivateLink networks