Why should I care about networking in AWS ?
Scenario-1
- Deploying a multi-tier application (Ecommerce application) with and without scaling
Scenario-2
- Deploying an application which has some components on-premise (Hybrid)
What needs to be understood in AWS Networking
- VPC (Network)
- Subnet (Sub-network)
- Private Networks and Public IP addressing
- Internet Gateways
- Security:
- Security Groups
- Network ACLs
- NAT:
- NAT-instance
- NAT-Gateway
- Route-tables
- Multi-Network Communications Over Private IPs
- VPC Peering
- VPNS
- Point to Site
- Site to Site
- Endpoints
What should I use to create resources in Amazon
- Is this creation repetitive?
- Yes:
- AWS CLI (Command Line Interface)
- Templating (Cloud Formation)
- No:
- AWS Console
- Yes:
AWS CLI Installation
- Windows:
- Install Chocolatey
- Install Git For Windows:
choco install git -y
- Install AWS CLI:
choco install awscli
- Linux:
AWS CLI Configuration
- AWS CLI needs credentials to connect to your AWS account.
- But these credentials are not email id & Password, rather they are ACCESS KEY and SECRET KEY.
- TO Generate ACCESS KEY and SECRET Key Click Here
- Test AWS cli connectivity using
aws ec2 describe-vpcs