Showing posts with label EC2 Instance. Show all posts
Showing posts with label EC2 Instance. Show all posts

Thursday, July 1, 2021

AWS: Instance Types : Instance Families : Instance Sizes : Instance Pricing : EC2

https://aws.amazon.com/ec2/instance-types/

https://aws.amazon.com/ec2/instance-explorer

Instance type

Instance   size

Hypervisor

vCPUs

Architecture

Cores

Threads   per core

Sustained   clock speed (GHz)

Memory   (GiB)

Network performance

Maximum   number of network interfaces

IPv4 addresses per interface

IPv6 addresses per interface

On-Demand   Linux pricing

c5.4xlarge

4xlarge

nitro

16

x86_64

8

2

3.4

32

Up to 10 Gigabit

8

30

30

0.68 USD per Hour

c5.2xlarge

2xlarge

nitro

8

x86_64

4

2

3.4

16

Up to 10 Gigabit

4

15

15

0.34 USD per Hour

c5.xlarge

xlarge

nitro

4

x86_64

2

2

3.4

8

Up to 10 Gigabit

4

15

15

0.17 USD per Hour

c5.large

large

nitro

2

x86_64

1

2

3.4

4

Up to 10 Gigabit

3

10

10

0.085 USD per Hour


Analytics

  • Elasticsearch Service  [Amazon Elasticsearch Service]
  • MSK  [Amazon Managed Streaming for Apache Kafka]


https://aws.amazon.com/ec2/instance-types/

n/w performance and Clock Speed -  may stay same  in a instance family.

Instance Family : Processor Speed /N.W Performance:  a1,t2, t3 [General Purpose]          c4, c5 [Compute Optimised]                   [Memory Optimized/RAM]           [Accelerated Computing/HW Accelerator]     [Storage Optimized/EBS]

Instance Size :  vCPU, Cores,  Memory(RAM)    :    nano, micro, small, medium, large, xlarge, 2xlarge, 4xlarge



30.5 Days


Large has 4GB RAM, 1 Core, 2 VCPUs

similarly, xlarge has 8 GB RAM, 2 Core, 4 VCPUs

n/w performance and Clock Speed -  may stay same  in a instance family.


Burst is related to EC2 Performance

Amazon EC2 allows you to choose between Fixed Performance Instances (e.g. M5, C5, and R5) and Burstable Performance Instances (e.g. T3). Burstable Performance Instances provide a baseline level of CPU performance with the ability to burst above the baseline.


New Generation is cheaper as compared to Old/deprecated - if other features stay same.






Saturday, April 10, 2021

AWS : Internet <-> Internet GW <-> VPC <-> Route Table <-> NACL <-> Security Group <-> EC2 Instance

 Data Flow inside AWS

Internet  :  Internet GW <-> VPC <-> Route Table   <->  NACL  <-> Security Group <-> EC2 Instance


VPC

Route Table : Once Data Arrives at Subnet, RT attached to Subnet decides where to route data traffic , It cannot block/unblock, it can just route
Data Traffic may want to come to My Subnet
Data Traffic may want to go from Subnet to Other Subnet or May want to Go to Outside World
Route to Local or Route to IGW or Route to NAT Gateway.
0.0.0.0.0 : Traffic meant for "NOT VPC Subnet"  -> Route to IGW or NAT
p.q.r.s/16  : "Subnet Traffic " -> Route Locally to Subnet

NACL : Once Data Traffic arrives at Subnet
It has to cross N/W Firewall - Subnet Firewall - known as NACL which may allow it or block it.
It checks Protocol Type, Port, Source/Destination (depending on Incoming/Outgoing Direction) and then allows or blocks, The rules are Numbered, If a Match is found, It can be DENY or ALLOW Rule and no further rules are processed.
Its stateless, You have to configure separate rule for incoming and outgoing and they both are independent of each other

Security Group :
Determines the traffic that can reach/leave your instance.
It is stateful 
It has Incoming and Outgoing Rules
But Incoming is related to Outgoing 
It has no DENY/ALLOW rule flag
All Rules are ALLOW by default
Rule says 
->  Allow PROTOCOL on PORT from SOURCE  - Incoming
->  Allow PROTOCOL on PORT from DESTINATION - Outgoing
SSH is TCP Protocol on 22
HTTP is TCP protocol on 80
PING in NCMP Protocol
If Incoming Rule allowed SSH on Port 80 and I did not mention Allow SSH on Port 22 for Outgoing, Even Then SSH will be allowed in Outgoing because its stateful, it remembers.
If Outgoing Rule is allowed, on PORT 80 and We did  not Configure HTTP on Incoming Side
Even then SSH will be allowed on that Machine



Thursday, April 1, 2021

Create EC2 Instance Steps - High Level Overview

 1. Choose AMI
2. Choose Instance Type
3. Configure Instance
4. Add Storage
5. Add Tags
6. Configure Security Group
7. Review
PEM = Private Key
Generate Password and Administrator - RDP Protocol (mstsc)

Azure - Pipeline - Add Approver for Stage

https://learn.microsoft.com/en-us/azure/devops/pipelines/process/approvals?view=azure-devops&tabs=check-pass