VPC
Amazon Virtual Private Cloud that lets you provision logically isolated section of the AWS Cloud where you can launch AWS resources in a virtual network that you define
Hardware VPN
Hardware Virtual Private Network - connection between your corporate datacenter and your VPC; leveraging the AWS cloud as an extension of your corporate DC
What can you do with VPCs?
Default VPC vs Custom VPC
VPC Peering allows you to
connect one VPC with another via a direct network route using Private IP addresses
In VPC peering, instances behave as if
they were on the same private network
You can peer VPCs with
2. other VPCs in the same account
Peering should be configured as
star configuration (1 central VPC peers with 4 others)
Transitive Peering
Means that B can’t go directly to C through A - there has to be a connection from B to C.
Think of VPC as a logical
DC in AWS
VPC consists of
Subnet to AZ ratio
1 Subnet = 1 AZ
Security Groups vs NACL in terms of defining rules
Security groups are STATEFUL while NACLS are stateless
Transitive peering is not allowed - true or false
true
Security groups only ? rules
allow rules ; no deny
with NACL, what can you do with rules?
allow and deny
When a new VPC gets created, these get created automatically:
IP addresses reserved for amazon use
first 4 and last IP in each subnet CIDR block (5)
What setting needs to be changed for a public subnet to be publicly accessible?
Auto-assign public IP should be changed to yes (default is no)
What happens when you initially create an IGW, does it automatically attaches to a VPC?
No
How many IGW can be attached to a VPC?
1
Security groups in relation to VPC
it doesn’t span VPCs
When a new VPC gets created, these do not get created automatically
2. Default IGW
How are AZs assigned?
randomized; US-East-1A in your AWS account can be a completely different zone to US-East-1A in another AWS account