Karteikarten
Cloud Setup
Karten in diesem Stapel (44)
- 1AWS Access Types- Management Console Access
- Programmatic Access - 2AWS Access Tools- Management console (MCA)
- API (PA)
- SDK (PA)
- Command line interface (PA) - 3VPC- Virtual Private Cloud
- Customer's own network within AWS
- Connects to corporate network through VPN or DX (direct connect)
- Housed within region - 4VPC Components- Availability Zone
- Subnet
- Load balancer
- EC2
- Security Group
- IGW
- NAT gateway
- Databases (RDS)
- NACL (optional) - 5Subnet- Allows VPC to span across multiple AZs
- Public or private
- Houses EC2s and RDS
- Protected by NACL
- Private by default - 6IGW and NAT- Internet Gateway (IGW) connects subnets to Internet - become public
- Network Address Translation (NAT) connects private subnets & databases to internet - 7Databases (RDS)- Housed within private subnets
- Primary and secondary
- Connected through synchronous data replication - 8Load Balancer (ELB)- Distributes traffic between 2 availability zones
- 9Security Group (SG)- Similar to firewall - network security at instance level
- Everything inbound denied by default; customer must whitelist sites
- Stateful - one rule for both inbound & outbound - 10Network Access Control List (NACL)- Optional
- Security at subnet level
- Requests can come in and out; customer chooses which ones to deny
- Stateless - rules needed/apply for both inbound & outbound (like passport) - 11Direct Connect (DX)- Option to connect VPC to corporate site
- Fiber-optic connection
- Consistent bandwidth, higher availability, critical workloads - 12CGW and VGW- Customer Gateway
- Virtual Gateway
- Connected thru VPN or DX
- Connect corporate network to AWS VPC - 13Edge LocationRegions located far away from the customer's VPC where customers are requesting services
- 14Amazon Simple Storage Service (S3)Cloud storage service located outside of VPC but still within region
- 15Cloudfront- CDN (Content Distribution Network)
- Service used to get customer's content to users outside of region by caching items from EC2 or S3 origin in edge locations - 16Distribution- Where and how video/content gets placed in cache
- 2 types for Cloudfront
- Customers can choose local or global distribution, depending on customer location - 17RTMP Distribution Type- 1 of 2 types of Cloudfront distribution
- Used for streaming content - 18Web Distribution Type- 1 of 2 types of Cloudfront distribution
- Used for all content that is not streaming-related - 19Route 53Edge distribution/routing service with 4 main routing policies
- 20Geolocation Routing Policy- Routing policy for Route 53
- Requests are re-routed from user's current region to home region where data is stored
- Can be used for users (ie Germans) who have data laws requiring that their data be stored in their primary location - 21Latency-Based Routing Policy- Routing policy for Route 53/edge locations
- Requests are sent to closest or most available region to user (aka whichever can be reached the fastest) - 22Weighted Round Robin Routing Policy- Routing policy for Route 53/edge locations
- X% of traffic is routed to Region A, while the remaining % is routed to Region B
- Exact copies of services/content are kept in each region, but customer chooses which ones get which % of traffic
- Can be used for customers testing out new service - 23Uptime/SLA- SLA=Service Level Availability
- Used to describe amount of time that machines are operational and available
- Measured in 9's (99.99%)
- Route 53 has near-100% SLA uptime - 24Failover Routing Policy- Routing policy for Route 53/edge locations
- Route 53 performs health check on primary region - if passes, sends traffic to primary region. If fails, sends to secondary region. - 25Instance Families- General purpose
- Compute optimized
- GPU optimized
- Memory optimized
- Storage optimized - 26General purpose instances- Balanced performance
- Websites, web apps, dev, code repos, micro services, business apps - 27Compute optimized instances- High CPU performance
- Front-end fleets, web servers, batch processing, distributed analytics, science & engineering apps, ad serving, MMO gaming, video encoding - 28GPU optimized instances- High-end GPU
- Amazon AppStream 2.0, video encoding, ML, high performance databases, science - 29Memory optimized instances- Large RAM footprint
- In-memory databases, data mining - 30Storage optimized instances- High I/O, high-density
- NAS, data warehousing, NoSQL - 31S3 Storage Classes- Standard
- Standard Infrequent Access
- Infrequent Access 1 Zone - 32Standard Storage Class- Redundantly stored across entire EC2 region
- Copies in each AZ
- S3 availability: 4 9's (99.99)
- S3 durability: 11 9's (99.999999999) - 33Standard Infrequent Access Storage Class- Infrequently requested data
- Redundantly stored across entire region
- S3 availability: 3 9's (99.9)
-S3 durability: 11 9's (99.999999999) - 34Infrequent Access 1 Zone Storage Class- Infrequently requested data that is easily reproduced
- Most cost-effective
- Stored in only 1 AZ in region - 35EBS Availability- Durable & automatically replicated in AZ in which it was created
- Copied multiple times within single AZ - if something happens to one instance, others are available
- AMI (Amazon Machine Image): backup of EBS instance - 36Snapshots (EBS)- Backup of EBS volume
- Used in the case of AZ failure
- Point-in-time snapshots that recreate new volumes at any time - 37ELB Types- Classic
- Application
- Network - 38Classic Load Balancer- Previous gen for HTTP, HTTPS, and TCP
- Distributes traffic in even percentages
- Not ideal - 39Application Load Balancer- Distributes traffic to individual apps based on URL path (www.google.com/shopping vs. www.google.com/photos)
- Same instance, different containers/apps
- Achieved thru listeners (follow rules to distribute to target group)
- Also called layer 7 routing - 40Network Load Balancer- Single static IP address per AZ
- Good for sudden volatile traffic patterns
- Ideal for apps that require extreme performances - 41Auto-Scaling Components- Launch configuration
- Auto-scaling group
- Auto-scaling policy - 42Launch Configuration- Asks what will be scaled
- Establishes launch settings
- AMI
- Instance type
- Security groups
- Roles - 43Auto-Scaling Group- Asks where launch will take place
- Deployment settings
- VPC and subnets
- Load balancer
- Min and max instances
- Desired capacity
- Takes place b/t 2 EC2 instances in AZ
- Has min/max parameters - 44Auto-Scaling Policy- Asks when launch will take place
- Policy settings
- Scheduled
- On-demand
- Scale-out policy
- Scale-in policy
Informationen
- Beschreibung
- CPC Digital Technologies Karteikarten am Cloud Setup, erstellt von Alyssa Lindley am 20/05/2022.
- Erstellt von
- Alyssa Lindley
- Aufrufe
- 0
- Bewertung