AWS eventbridge documentation change
Summary
Removed TriggerMesh from the partner list and deleted its entire documentation section.
Security assessment
Partner removal doesn't indicate a security issue. No security advisories, vulnerabilities, or configuration changes are mentioned.
Diff
diff --git a/eventbridge/latest/userguide/eb-api-destination-partners.md b/eventbridge/latest/userguide/eb-api-destination-partners.md index 6af262b72..ed3956e4c 100644 --- a//eventbridge/latest/userguide/eb-api-destination-partners.md +++ b//eventbridge/latest/userguide/eb-api-destination-partners.md @@ -7 +7 @@ -Cisco Cloud ObservabilityConfluentCoralogixDatadogDynatraceFreshworksMongoDBMomentoNew RelicOperataSalesforceSlackShopifySplunkSumo LogicTriggerMeshZendesk +Cisco Cloud ObservabilityConfluentCoralogixDatadogDynatraceFreshworksMongoDBMomentoNew RelicOperataSalesforceSlackShopifySplunkSumo LogicZendesk @@ -724,36 +723,0 @@ POST https://endpoint4.collection.us2.sumologic.com/receiver/v1/http/`UNIQUE_ID_ -None - -## TriggerMesh - -**API destination invocation endpoint URL** - - -Use the information in the [Event Source for HTTP](https://docs.triggermesh.io/concepts/sources) topic to formulate the endpoint URL. An endpoint URL includes the event source name and user namespace in the following format: - -https://`source-name`.`user-namespace`.cloud.triggermesh.io - -Include the Basic authorization parameters in the request to the endpoint. - -**Supported authorization types** - - -Basic - -**Additional authorization parameters required** - - -None - -**TriggerMesh documentation** - - -[Event Source for HTTP](https://docs.triggermesh.io/concepts/sources) - -**Commonly used API operations** - - -Not applicable - -**Additional information** - -