Using Amazon EventBridge with Interface VPC Endpoints - Amazon EventBridge
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Using Amazon EventBridge with Interface VPC Endpoints

If you use Amazon Virtual Private Cloud (Amazon VPC) to host your Amazon resources, you can establish a private connection between your VPC and EventBridge. Your resources on your VPC can use this connection to communicate with EventBridge.

With a VPC, you have control over your network settings, such as the IP address range, subnets, route tables, and network gateways. To connect your VPC to EventBridge, you define an interface VPC endpoint for EventBridge. The endpoint provides reliable, scalable connectivity to EventBridge without requiring an internet gateway, network address translation (NAT) instance, or VPN connection. For more information, see What is Amazon VPC in the Amazon VPC User Guide.

Interface VPC endpoints are powered by Amazon PrivateLink, which enables private communication between Amazon services using an elastic network interface with private IP addresses. For more information, see Amazon PrivateLink and VPC endpoints.

When you use a private interface VPC endpoint, custom events your VPC sends to EventBridge use that endpoint. EventBridge then sends those events to other Amazon services based on the rules and targets that you've configured. Once events are sent to another service you can receive them through either the public endpoint or a VPC endpoint for that service. For example, if you create a rule to send events to an Amazon SQS queue, you can configure an interface VPC endpoint for Amazon SQS to receive messages from that queue in your VPC without using the public endpoint.

Availability

EventBridge currently supports VPC endpoints in the following Regions:

  • US East (Ohio)

  • US East (N. Virginia)

  • US West (N. California)

  • US West (Oregon)

  • Africa (Cape Town)

  • Asia Pacific (Mumbai)

  • Asia Pacific (Hyderabad)

  • Asia Pacific (Hong Kong)

  • Asia Pacific (Singapore)

  • Asia Pacific (Sydney)

  • Asia Pacific (Jakarta)

  • Asia Pacific (Melbourne)

  • Asia Pacific (Tokyo)

  • Asia Pacific (Seoul)

  • Asia Pacific (Osaka)

  • Canada (Central)

  • Canada West (Calgary)

  • China (Beijing)

  • China (Ningxia)

  • Europe (Frankfurt)

  • Europe (Zurich)

  • Europe (Ireland)

  • Europe (London)

  • Europe (Milan)

  • Europe (Spain)

  • Europe (Paris)

  • Europe (Stockholm)

  • Middle East (UAE)

  • Middle East (Bahrain)

  • South America (São Paulo)

  • Israel (Tel Aviv)

  • Amazon GovCloud (US-West)

  • Amazon GovCloud (US-East)

Creating a VPC Endpoint for EventBridge

To use EventBridge with your VPC, create an interface VPC endpoint for EventBridge and choose com.amazonaws.Region.events as the service name. For more information, see Creating an Interface Endpoint in the Amazon VPC User Guide.

EventBridge Pipes specifics

Full EventBridge Pipes support for Interface VPC endpoints is not available. To use the following sources within a VPC with EventBridge Pipes, see the following: