AWS VPC is Virtual Private Cloud,
Is similar as On-premise data-center bind with firewall not to access outside of AWS,Its bind with your own AWS account and will have their own private IP's,Only those resources inside the VPC,Can communicate and access unless we define any rules with route/peer/NAT/Internet gateway to access outside AWS.
For Ex: In the below,We have AWS cloud computing,We have VPC for customer A,
And the customer A has 2 subnet each subnet is having one EC2 instance,The IP assign to those subnet is 10.0.1.0/24 and 10.0.2.0/24 which is private only for this VPC. and Its bind as for customer A,
The same way other customer can have similar setup with same 10.0.1.0/24 IP on his VPC.
Ref: https://aws.amazon.com/blogs/apn/amazon-vpc-for-on-premises-network-engineers-part-one/
Is similar as On-premise data-center bind with firewall not to access outside of AWS,Its bind with your own AWS account and will have their own private IP's,Only those resources inside the VPC,Can communicate and access unless we define any rules with route/peer/NAT/Internet gateway to access outside AWS.
For Ex: In the below,We have AWS cloud computing,We have VPC for customer A,
And the customer A has 2 subnet each subnet is having one EC2 instance,The IP assign to those subnet is 10.0.1.0/24 and 10.0.2.0/24 which is private only for this VPC. and Its bind as for customer A,
The same way other customer can have similar setup with same 10.0.1.0/24 IP on his VPC.
Ref: https://aws.amazon.com/blogs/apn/amazon-vpc-for-on-premises-network-engineers-part-one/
No comments:
Post a Comment