diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx index d70c432ee6e1bd..7e27ab9e90b0f8 100644 --- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx +++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/kinesis.mdx @@ -46,13 +46,13 @@ Logpush supports [Amazon Kinesis](https://aws.amazon.com/kinesis/) as a destinat 3. Create a Logpush job, using the following format for the `destination_conf` field: ```bash -kinesis://?region=&sts-assume-role-arn=arn:aws:iam:::role/ +kinesis://?region=&sts-assume-role-arn=arn:aws:iam:::role/ ``` 4. (optional) When using STS Assume Role, you can include `sts-external-id` as a `destination_conf` parameter so it is included in your Logpush job's requests to Kinesis. Refer to [Securely Using External ID for Accessing AWS Accounts Owned by Others](https://aws.amazon.com/blogs/apn/securely-using-external-id-for-accessing-aws-accounts-owned-by-others/) for more information. ```bash -kinesis://?region=&sts-assume-role-arn=arn:aws:iam:::role/&sts-external-id= +kinesis://?region=&sts-assume-role-arn=arn:aws:iam:::role/&sts-external-id= ``` ### STS Assume Role example @@ -62,7 +62,7 @@ $ curl https://api.cloudflare.com/client/v4/zones/$ZONE_TAG/logpush/jobs \ -H 'Authorization: Bearer ' \ -H 'Content-Type: application/json' -d '{ "name": "kinesis", - "destination_conf": "kinesis://?region=&sts-assume-role-arn=arn:aws:iam:::role/", + "destination_conf": "kinesis://?region=&sts-assume-role-arn=arn:aws:iam:::role/", "dataset": "http_requests", "enabled": true }'