Please enable JavaScript.

Coggle requires JavaScript to display documents.

Cloud Networking - Coggle Diagram

- - - - In Amazon Web Services (AWS), the range of IP addresses available for a Virtual Private Cloud (VPC) can be determined by the IP address range that you specify when you create the VPC. By default, a VPC is created with a default IP address range of 172.31.0.0/16, but you can specify a different range of your choice, as long as it is within the private IP address range (as defined by Internet Assigned Numbers Authority (IANA)) and is not already in use in your network.
      - When you create a VPC, you can specify a custom IP address range in CIDR notation, for example, 10.0.0.0/16, or 10.0.0.0/24. This CIDR notation is used to specify the range of IP addresses that the VPC can use, with the first part of the notation (e.g. 10.0.0) indicating the base IP address and the second part of the notation (e.g. /16 or /24) indicating the number of IP addresses in the range.
      - It is also worth noting that when you create a VPC, AWS reserves five IP addresses from the IP address range that you specify, that is the first four IP addresses and the last IP address, for VPC-specific operations, such as the VPC's router, DNS server, and DHCP server.
    - - Public subnets are connected to the Internet through an Internet Gateway (IGW) and can be used to launch resources that need to be directly accessible from the Internet, such as a web server.
      - Private subnets, on the other hand, are not connected to the Internet by default and can be used to launch resources that should not be directly accessible from the Internet, such as a database. Resources in private subnets can still access the Internet indirectly through a NAT gateway or NAT instance.
      - By doing so you are creating a security layer to your vpc, It will increase the security level of your VPC. Traffic from the Internet will be prevented from reaching the instances in private subnets, but these instances can still access the Internet to download software updates, for example.
  - - - An IGW is a horizontally-scaled, redundant, and highly-available VPC component that allows communication between instances in your VPC and the Internet. It acts as a target for Internet-routable IP traffic to flow in and out of your VPC. It can be thought of as the "gateway" through which Internet traffic flows in and out of your VPC.
      - Each VPC is automatically provided with an Internet Gateway and it is attached to the VPC by default, this allows all instances in the VPC to communicate with the Internet by default. You can also create additional subnets in your VPC and attach an IGW to them. This allows instances in those subnets to communicate with the Internet while instances in other subnets remain isolated.
      - It is also important to note that an Internet Gateway is not a physical device but it is implemented as a software component that runs in the Amazon VPC network.
      - By default, the Internet Gateway uses the VPC's main route table to determine the routes for Internet-bound traffic. You can also create custom routes to direct traffic to specific subnets, instances, or virtual appliances as well.
      - An Internet Gateway (IGW) is a component of Amazon Web Services (AWS) Virtual Private Cloud (VPC) that allows communication between instances in your VPC and the Internet.
    - - A VGW is a logical connection between a VPC and a VPN or Direct Connect link
    - - A VPN Connection, on the other hand, uses the internet to connect an on-premises network to a VPC.
    - - It allows for communication between instances in your VPC and on-premises data centers or other VPCs over a dedicated and highly available connection.
      - It acts as a hub for the Direct Connect connections, allowing you to connect multiple VPCs and on-premises networks to a single Direct Connect link, rather than having to create a separate Direct Connect link for each VPC or network.
      - This simplifies network architecture and reduces costs.
      - it also provides automatic failover and traffic management capabilities, which helps to improve the availability and performance of your connections.
  - - - Enabling communication between resources in different VPCs using private IP addresses
      - Allowing resources in one VPC to access resources in another VPC without the need for a VPN or Internet Gateway
      - Providing additional security and isolation for resources by keeping them within their own VPCs
    - - VPC peering is limited to VPCs within the same region.
      - you cannot create a VPC peering connection between VPCs in different accounts.
        
        If you want to connect VPCs in different accounts, you can use an AWS Transit Gateway, which allows to connect VPCs and on-premises networks across multiple accounts and VPCs. Another alternative is to use an VPN or Direct Connect to connect on-premises network to the VPC.
      - VPCs that are peered must have non-overlapping IP ranges, IP ranges can't overlap between peered VPCs, so you can't have the same IP addresses in both VPCs.
      - CIDR blocks of the VPCs can't be modified once they are created.