AWS Elastic Cloud Compute
cloud AWS

5 minutes


go back go back go back
module AWS Elastic Cloud Compute
📎
home home

Introduction to Elastic Cloud Compute

Knowing EC2 is fundamental to understand how the cloud works!!

EC2 Configuration Options
Configuration ItemOptions
Operating SystemLinux, Windows, MacOS
How much compute power (cores)1,2,4,8,16 cores
How much random-access memory (RAM)4GB, 8GB, 16GB
Which type of storage
Persistent Network Storage (EBS)
Persistent Network Storage with File System (EFS)
Non-Persistent Hardware Storage (EC2 Instance Store)
Network CardSpeed of Card, Public IP Address (AWS Elastic IP)
Security GroupEC2 Security Group
Bootstrap/Startup ScriptEC2 User Data

EC2 User Data

It is possible to bootstrap our instances using an EC2 User Data Script, or simply known as Startup Script. Bootstrap means launching commands when the machine starts up. Note: EC2 user data is used to automate boot tasks such as:

Note: EC2 UserData script with root user privilages.


EC2 - Instance Type

Specialized EC2 instance can be used for different requirements. It follows the following naming convensions.

"Sample Instance Type"

Following is the list of popular instance type:


General Purpose

Great for diversity of workload such as web servers or code repositories. It is a balance between: Compute, Memory, Network. E.g. “t2.micro”.



Compute Optimized

It is great for compute-intensive tasks that require high peformance processors. Some common tasks done using compute instance are as follows:



Memory Optimized

Fast peformance for workload that process large datasets in memory.



Storage Optimized

Great for storage intensive tasks, that require high, sequential read & write access to large datasets on local storage.



Introduction to Security Groups

They are fundamental of network and security in AWS. They control how traffic is allowed into or out of our EC2 Instance (only!).

"Sample Instance Type"


They Regulate the following items:
1. Access to Port
2. Authorised IP ranges - IPv4 & IPv6
3. Control of inbound network (from other to the instances)
4. Control of outbound network (from the instance to others)


Security Groups - Notes
Notes:
1. SG can be attached to multiple instances
2. SGs are locked down to a region/VPC combination
3. Does “live outside” the EC2 - if traffic is blocked by an SG, then EC2 will not see/log it
4. It’s good to maintain one seperate security group for SSH access.
5. If your application is not accessible (timeout), then its might be a security group issue
6. If your application gives a “connection refused” error, then its an Application issue or it hasn’t started up.
7. All INBOUND traffic is BLOCKED by default
8. All OUTBOUND traffic is AUTHORISED by default