AWS eventbridge: Note on Custom Event Bus VPC endpoint service names
Summary
Adds a note that the Custom Event Bus uses its own endpoint service names (eventsv2, eventsv2-fips) requiring a separate interface endpoint, distinct from the events endpoint used by Custom Event Bus - Classic.
Security assessment
Documents private connectivity via VPC interface endpoints for a new endpoint service, which is network-security-relevant guidance (traffic stays off the public internet), but it does not address a specific vulnerability or incident.
Evidence
The Custom Event Bus has its own endpoint service names: `com.amazonaws.`region`.eventsv2` and `com.amazonaws.`region`.eventsv2-fips`. Create a separate interface endpoint for them; the `events` endpoint on this page serves Custom Event Bus - Classic only.
Diff
diff --git a/eventbridge/latest/userguide/eb-related-service-vpc.md b/eventbridge/latest/userguide/eb-related-service-vpc.md index be49ecf8d..8bbdac3ff 100644 --- a//eventbridge/latest/userguide/eb-related-service-vpc.md +++ b//eventbridge/latest/userguide/eb-related-service-vpc.md @@ -12,0 +13,4 @@ If you use Amazon Virtual Private Cloud (Amazon VPC) to host your AWS resources, +###### Note + +The Custom Event Bus has its own endpoint service names: `com.amazonaws.`region`.eventsv2` and `com.amazonaws.`region`.eventsv2-fips`. Create a separate interface endpoint for them; the `events` endpoint on this page serves Custom Event Bus - Classic only. See [Names, endpoints, and IAM permissions for the Custom Event Bus](./eb-custom-bus-names.html). +