Create Logpush ownership token file. See [eCDN Logpush](https://developer.salesforce.com/docs/commerce/commerce-api/guide/cdn-zones-logpush.html).
Operation ID: createLogpushOwnershipcurl "https://{shortCode}.api.commercecloud.salesforce.com/cdn/zones/v1/organizations/{organizationId}/zones/{zoneId}/logpush/ownership" \
-X POST \
-H "content-type: application/json" \
-d '{
"destinationPath": "s3://customer-bucket/site-name/{DATE}?region=us-east-1&sse=AES256"
}'
An identifier for the organization the request is being made by
f_ecom_zzxy_prd
{
"destinationPath": "s3://customer-bucket/site-name/{DATE}?region=us-east-1&sse=AES256"
}
Uniquely identifies a resource (such as an s3 bucket) where data will be pushed. Additional configuration parameters supported by the destination may be included. You can use the special string {DATE} in the URL path to separate logs into daily subdirectories; for example s3://customer-bucket/logs/{DATE}?region=us-east-1&sse=AES256. The name of the directory will be replaced with the date in YYYYMMDD format (e.g. 20220215) when the logs are stored.
s3://customer-bucket/site-name/{DATE}?region=us-east-1&sse=AES256
Created a new Logpush Ownership token.
{
"data": {
"destinationPath": "s3://customer-bucket/site-name/{DATE}?region=us-east-1&sse=AES256",
"fileName": "site-name/20230101/ownership-challenge-f1234567.txt"
}
}
The customer's new Logpush Ownership.