Using VPC to Access Resources on Multiple Clusters
Using VPC to Access Resources on Multiple Clusters
Amazon Virtual Private Cloud (Amazon VPC) enables the provision of a logically isolated section of the Amazon Web Services (AWS) cloud. In this location, you can launch AWS resources in a virtual network that you define. Network communication via private IPs is only facilitated through VPC peering.
VPC peering allows a user of one VPC to access the resources of another VPC. For example, the Informatica domain is installed on VPC-A, while the EMR cluster is on VPC-B. When you enable VPC peering, you enable access to the EMR cluster from the Informatica domain.
Enable VPC peering when the Informatica domain and the Data Integration Service are on not on the same Virtual Private Cloud (VPC).
The following illustration shows Informatica services on different VPCs submitting various kinds of jobs to a shared EMR cluster on VPC-A:
Based on internal tests, VPC peering within the same region adds no performance overhead to mapping runs.