Reputation: 597
I have no idea how to frame this question - but please do edit accordingly.
I developed an application App1 which resides in AWS which connects to App2 developed by a third party which is exclusively used by App1. App2 resides in AWS as well. App2 exposes a webservice to the internet and App1 connects to it.
App1 - eu-west
App2 - eu-central
My question here is since App1 and App2 sit in AWS, can I talk to App2's webservice without ever going to the internet or leaving the AWS network ?
Upvotes: 2
Views: 133
Reputation: 3496
Absolutely you can, using the relatively new AWS PrivateLink for Customers and Partners, which is a much neater solution than the previous option of VPC peering.
In App2, create a service endpoint to make it available to other AWS Accounts. (VPC > Endpoint Services > Create)
In App1 (service consumer AWS account), add the service endpoint from App1 as a VPC Endpoint. (VPC > Endpoints > Create > Find service by name)
This is a good guide to setting it up in more detail: https://docs.aws.amazon.com/vpc/latest/userguide/endpoint-service.html
Upvotes: 1
Reputation: 484
Sure you can. Here's how:
Upvotes: 0
Reputation: 749
Inter-region VPC peering connections allow secure communication between VPC resources in different AWS Regions. All network traffic between regions is encrypted, stays on the AWS global network backbone, and never traverses the public internet, thereby reducing threat vectors, such as common exploits and DDoS attacks. VPC peering is appropriate for many scenarios, for example, to provide VPCs full access to each other’s resources or to provide a set of VPCs partial access to resources in a central VPC. You can configure peering connections to provide access to part of a CIDR block or to an entire CIDR block of the peer VPC.
This Amazon blog post gives you a step by step tutorial and you can find more detailed information on Amazon VPC peering page.
Upvotes: 0