Basics for creating an Internet-connected VPC

  1. Choosing an address range Recommended: RFC1918 range /16(64K addresses) (avoid ranges that overlap with other networks to which you might connect)
  2. Setting up subnets in Availability Zones Recommended: /24 subnets(251 addresses) example: one subnet per Availability Zone: Availability Zone 1: Availability Zone 2: Availability Zone 3:

  3. Creating a route to the Internet
    • Route tables contain rules for which packets go where
    • Your VPC has a default route table
    • but you can assign different route tables to different subnets example: ``` default: Destination Target local

after create internet gateway: Destination Target local igw-xxxxxx

4. Authorizing traffic to/from the VPC
+ Network ACLs = stateless firewall rules
+ Security groups = stateful firewall

### More scenarios

+ non-internet facing VPC access the internet by routing to NAT in the internet facing VPC
+ VPC Peering
    1. Initiate peering request
    2. Accept peering request
    3. create routes
+ Extend your own network to VPC
    - VPN
    - Direct Connect
## The AWS Command Line Interface (CLI)
is a unified tool to manage your AWS services. With just one tool to download and configure, you can control multiple AWS services from the command line and automate them through scripts.

The AWS CLI v2 offers several new features including improved installers, new configuration options such as AWS Single Sign-On (SSO), and various interactive features. 

All IaaS (infrastructure as a service) AWS administration, management, and access functions in the AWS Management Console are available in the AWS API and AWS CLI.

The AWS CLI provides direct access to the public APIs of AWS services. You can explore a service's capabilities with the AWS CLI, and develop shell scripts to manage your resources. In addition to the low-level, API-equivalent commands, several AWS services provide customizations for the AWS CLI.




### config

$ aws help $ aws autoscaling help $ aws autoscaling create-auto-scaling-group help

aws configure $ aws configure –profile produser $ aws s3 ls –profile produser

~/.aws/credentials C:\Users\USERNAME.aws\credentials ~/.aws/config C:\Users\USERNAME.aws\config

$ aws configure import –csv file://credentials.csv

aws configure list

### IAM

###  Amazon Elastic Compute Cloud (Amazon EC2) instances

aws ec2 describe-instances

$ aws ec2 describe-instances

$ aws ec2 start-instances –instance-ids i-1348636c

$ aws sns publish –topic-arn arn:aws:sns:us-east-1:546419318123:OperationsError –message “Script Failure”

$ aws sqs receive-message –queue-url https://queue.amazonaws.com/546419318123/Test

### Amazon Simple Storage Service - S3
File Commands for Amazon S3

$ aws s3 ls s3://mybucket $ aws s3 cp myfolder s3://mybucket/myfolder –recursive $ aws s3 sync myfolder s3://mybucket/myfolder –exclude *.tmp

### dynamodb 

$ aws dynamodb list-tables

### Amazon SNS

### Amazon SWF

### others

Perform Basic Kinesis Data Stream Operations Using the AWS CLI:

### troubleshooting


aws command --debug


An error occurred (AuthFailure) when calling the DescribeInstances operation: AWS was not able to validate the provided access credentials

An error occurred (UnauthorizedOperation) when calling the DescribeInstances operation: You are not authorized to perform this operation.


aws shell


AWS Security Reference Architecture

AWS Security Reference Architecture