You created a new VPC with CIDR range 10.10.0.0/16 and a new subnet with CIDR range 10.10.1.0/24
CIDR with /24 comes with 256 IP addresses.
When you go to VPC console subnets and look at the newly created subnet, you can only see 251 IP addresses.
You have not launched any resources in the newly created VPC.
What would have caused this?
Click on the arrows to vote for the correct answer
A. B. C. D.Answer: A.
https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Subnets.html#VPC_SizingFrom the above statement, only.
Option A is correct.
For Option C, AWS never launches any billable resources without notifying the account owner or administrator on behalf of you.
The correct answer is A, "The first four IP addresses and the last IP address in each subnet CIDR block are reserved by AWS."
When you create a subnet in a VPC, AWS reserves some IP addresses for its own use. These addresses are reserved for various purposes, such as routing, network addressing, and DNS. Specifically, AWS reserves the first four IP addresses and the last IP address in each subnet CIDR block for its own use. This means that out of the 256 IP addresses available in a /24 subnet, only 251 are available for you to use.
The first four IP addresses in a CIDR block are reserved as follows:
The last IP address in a CIDR block is also reserved and cannot be assigned to any instance or resource within the subnet. This is because it is the broadcast address, which is used to send traffic to all devices on the subnet.
Therefore, in a /24 subnet, 256 IP addresses are available, but only 251 can be used by your resources. The remaining five IP addresses are reserved by AWS for network infrastructure and cannot be assigned to any instances or resources within the subnet.
Option B is incorrect because AWS only reserves five IP addresses for the VPC itself, not for each subnet. These IP addresses are used for the VPC router, DNS server, and network address, and are reserved from the first subnet you create.
Option C is incorrect because AWS does not launch any monitoring resources on behalf of you when you create a new VPC or subnet. However, AWS does provide various monitoring tools and services that you can use to monitor your resources within a VPC.