Claim traffic filter link ID ownership through the API
This example demonstrates how to use the Elastic Cloud RESTful API to claim different types of private link ID (AWS PrivateLink, Azure Private Link, and GCP Private Service Connect). We cover the following examples:
curl \
-H "Authorization: ApiKey $API_KEY" \
-H 'content-type: application/json' \
https://api.elastic-cloud.com/api/v1/deployments/traffic-filter/link-ids/_claim \
-d '
{
"region": "eu-west-1",
"link_id": "$VPC_ENDPOINT_ID"
}
'
curl \
-H "Authorization: ApiKey $API_KEY" \
-H 'content-type: application/json' \
https://api.elastic-cloud.com/api/v1/deployments/traffic-filter/link-ids/_claim \
-d '
{
"region": "gcp-us-central1",
"link_id": "$PSC_CONNECTION_ID"
}
'
curl \
-H "Authorization: ApiKey $API_KEY" \
-H 'content-type: application/json' \
https://api.elastic-cloud.com/api/v1/deployments/traffic-filter/link-ids/_claim \
-d '
{
"region": "azure-eastus2",
"azure_endpoint_name": "$AZURE_ENDPOINT_NAME",
"azure_endpoint_guid": "$AZURE_ENDPOINT_GUID"
}
'
curl \
-H "Authorization: ApiKey $API_KEY" \
-H 'content-type: application/json' \
https://api.elastic-cloud.com/api/v1/deployments/traffic-filter/link-ids \
curl \
-H "Authorization: ApiKey $API_KEY" \
-H 'content-type: application/json' \
https://api.elastic-cloud.com/api/v1/deployments/traffic-filter/link-ids/_unclaim \
-d '
{
"region": "eu-west-1",
"link_id": "$VPC_ENDPOINT_ID"
}
'
curl \
-H "Authorization: ApiKey $API_KEY" \
-H 'content-type: application/json' \
https://api.elastic-cloud.com/api/v1/deployments/traffic-filter/link-ids/_unclaim \
-d '
{
"region": "gcp-us-central1",
"link_id": "$PSC_CONNECTION_ID"
}
'
curl \
-H "Authorization: ApiKey $API_KEY" \
-H 'content-type: application/json' \
https://api.elastic-cloud.com/api/v1/deployments/traffic-filter/link-ids/_unclaim \
-d '
{
"region": "azure-eastus2",
"azure_endpoint_name": "$AZURE_ENDPOINT_NAME",
"azure_endpoint_guid": "$AZURE_ENDPOINT_GUID"
}
'