AWS eventbridge documentation change
Summary
Improved formatting by adding backticks to field names and HTTP methods, updated Coralogix link, and standardized endpoint formatting
Security assessment
Formatting and documentation accuracy improvements without security implications. No security features added or vulnerabilities addressed.
Diff
diff --git a/eventbridge/latest/userguide/eb-api-destination-partners.md b/eventbridge/latest/userguide/eb-api-destination-partners.md index ed3956e4c..3a3848e8b 100644 --- a//eventbridge/latest/userguide/eb-api-destination-partners.md +++ b//eventbridge/latest/userguide/eb-api-destination-partners.md @@ -40,2 +40,2 @@ Type | Key | Value -Body Field | grant_type | client_credentials -Header | Content-Type | application/x-www-form-urlencoded; charset=utf-8 +Body Field | `grant_type` | `client_credentials` +Header | `Content-Type` | `application/x-www-form-urlencoded; charset=utf-8` @@ -136 +136 @@ Then, use the input transformer template to specify the data field as the partit -For a full list of endpoints, see [Coralogix API Reference](https://coralogix.com/docs/log-query-simply-retrieve-data/). +For a full list of endpoints, see [Coralogix API Reference](https://coralogix.com/docs/user-guides/alerting/outbound-webhooks/aws-eventbridge-outbound-webhook/). @@ -196 +196 @@ None -POST https://api.datadoghq.com/api/v1/events +`POST` https://api.datadoghq.com/api/v1/events @@ -198 +198 @@ POST https://api.datadoghq.com/api/v1/events -POST https://http-intake.logs.datadoghq.com/v1/input +`POST` https://http-intake.logs.datadoghq.com/v1/input @@ -231 +231 @@ Type | Key | Value -Header | Authorization | Api-Token `DYNATRACE_API_KEY` +Header | `Authorization` | Api-Token `DYNATRACE_API_KEY` @@ -248 +248 @@ Header | Authorization | Api-Token `DYNATRACE_API_KEY` -POST +`POST` @@ -354 +354 @@ Type | Key | Value -Header | Authorization | `MOMENTO_API_KEY` +Header | `Authorization` | `MOMENTO_API_KEY` @@ -529 +529 @@ The following key/value pair: -grant_type | client_credentials +`grant_type` | `client_credentials` @@ -628 +628 @@ Not applicable -POST - /admin/api/2022-01/products.json +`POST` \- /admin/api/2022-01/products.json @@ -630 +630 @@ POST - /admin/api/2022-01/products.json -GET - admin/api/2022-01/products/{product_id}.json +`GET` \- admin/api/2022-01/products/{product_id}.json @@ -632 +632 @@ GET - admin/api/2022-01/products/{product_id}.json -PUT - admin/api/2022-01/products/{product_id}.json +`PUT` \- admin/api/2022-01/products/{product_id}.json @@ -634 +634 @@ PUT - admin/api/2022-01/products/{product_id}.json -DELETE - admin/api/2022-01/products/{product_id}.json +`DELETE` \- admin/api/2022-01/products/{product_id}.json @@ -674 +674 @@ For both authorization types, you need an HEC token ID. For more information, se -POST https://`SPLUNK_HEC_ENDPOINT`:`optional_port`/services/collector/raw +`POST` https://`SPLUNK_HEC_ENDPOINT`:`optional_port`/services/collector/raw @@ -719 +719 @@ If you’re generating custom events from an application and want to send them t -POST https://endpoint4.collection.us2.sumologic.com/receiver/v1/http/`UNIQUE_ID_PER_COLLECTOR` +`POST` https://endpoint4.collection.us2.sumologic.com/receiver/v1/http/`UNIQUE_ID_PER_COLLECTOR` @@ -751 +751 @@ None -POST https://`your_Zendesk_subdomain`/api/v2/tickets +`POST` https://`your_Zendesk_subdomain`/api/v2/tickets