AWS pt 0 Flashcards
1
Q
AWS EC2
A
- Operating System (OS): Linux, Windows or Mac OS
- CPU: Compure power and cores
- RAM: random access memory
- Storage space (network attached (EBS & EFS), Hardware (EC2 Instance Store))
- Network card: speed of the card, Public IP
- Firewall: SG
- Bootstrap script (at first launch): EC2 User Data
2
Q
AMI
A
- Customized EC2 (Packages)
- Buy and sell these (Public: AWS, MarketPlace: 3rd Parties)
- Use snapshots to transfer
- EC2 Image builder: Fancy UI to build and test AMIs (Free)
3
Q
EBS
A
- Network drive: to access (persist) data when EC2 is terminated
- One instance at a time
- Bound to a specific AZ
- Delete on termination: To counter this we have snapshots
- Snapshots (Back up):
- Allows you to transfer to a different AZ
4
Q
EC2 Instance Store
A
- Better than EBS (Temporary use) however Lose once you stop
- Risk losing data if hardware fails (up to you for backup)
5
Q
EFS
A
- Quickly scales for heavy workloads with fast output
- Shared network file system (Multiple EC2 instances at a time)
- Multi-AZ
- Highly available, scalable, expensive, pay per use, no capacity planning
- EFS Infrequent access: Lower cost for those that aren’t accessed, auto decided
6
Q
Problems solved with cloud
A
- Flexibility: Change resource types
- Cost effectiveness: Pay as you go, for what you use
- Scalability: Accomodate larger loads by making hardware stronger or adding additional nodes
- Elasticity: Ability to scale out and scale in when needed (Acquire resources as needed)
- High availability and fault-tolerance: Build across data centers
- Agility: Rapidly develop, test and launch software applications
6
Q
FSX
A
- 3rd Party file server
- FSX Lustre (Linux)
- FSX WW File server
7
Q
ELB
A
- Manage load balancer (Multiple servers)
- High availability
- Health Checks
- Across different zones
1. ALB: HTTP (Layer 7)
2. NLB: TCP/UDP protocols (Uses Elastic IP, High performance) (Layer 4)
3. Gateway Load Balancer (GLB): GENEVE Protocol (Layer 3), Firewall, Intrustion detection
8
Q
ASG (Auto Scaling Group)
A
- min-max number of machines corresponding to need
- Replace unhealthy instances
- Manual Scaling
- Dynamic Scaling: Responds to changing demands
- Simple/Step scaling: Cloudwatch (Threshold is triggered) -> Increase/decrease accordingly
- Target Tracking scaling: Make sure the CPU is at a certain level
- Schedule scaling: Anticipate with usage patterns
- Predictive scaling: Predict future traffic
9
Q
S3 Buckets (Objects)
A
- Globally unique but regionally defined
- Objects (body: metadata, tags: key/value pair, version ID: versioning is enabled (at bucket level))
- Its an object storage service not a database storage service
10
Q
S3 Buckets (Security)
A
- IAM policies
- Bucket Policies (Allow/Deny, JSON, public access (Hosting websites))
- Control lists (Buckets and objects)
11
Q
S3 Buckets (Replication)
A
- Must enable versioning
- Cross Regional (availabiliy), same region replication
- Good for dynamic content that needs to be availble with low latency
- Files are uploadrd real time
- Reads only
12
Q
S3 Storage Classes
A
- High durability:** Across multi-AZs (No loss of objects) **(Same for all classes)
- Availability: Varies on storage classes
- General Purpose:
- Frequent Access: Low latency and high throughput, sustain 2 concurrent facility failures
13
Q
S3 Storage Infrequent
A
- Infrequent Access: Rapid access when needed
- Standard Infrequent Access: Disaster recovery
- One Zone Infrequent Access: Secondary backup of on premise data
14
Q
S3 Storage Glacier
A
- Amazon Glacier:
- Low cost meant for archiving/back up - Glacier Instant Retreival:
- Instant retreival
- Data accessed once a quarter (min storage 90 days) - Glacier Flexible Retreival:
- Waiting time to review the data (different in three classes max 5-12 hours)
- min storage 90 days - Glacier Deep Archive:
- Waiting time (12-48 hours)
- min storage 180 days
