CloudFront

• 낮은 대기 시간과 높은 전송 속도로 안전하게 콘텐츠 전송
• Content Delivery Network(CDN) : distributed network servers which delivers web pages based on their geographical location. (구글.com, kr , uk 등)
• aws shield standard 포함됨(ddos 공격 방어)
• 비용 절감 가능
• 대규모 전송 가능, 페타바이트 이상

Core Components

• Origin : The location where all of original files are located. ex) S3 Bucket, Ec2 Instance, ELB or Route 53
• Edge Location : The location where web content will be cached. This is different than an AWS Region or AZ(읽고 쓰기 가능)
• Distribution : A collection of Edge locations which defines how cached content should behave
  

Distribution

• is a collection of Edge Locations. ex) S3, EC2, ELB, Route53
• Web, RTMP(for streaming media)
• can serve up custom error pages(ex: 404)
• Geo Restriction to blacklist or whitelist to specific countries

Lambda@Edge

• to override the behavior of request and reponses

Protection

• default is that allows everyone to have access
• OAI(Original Identity Access) : A virtual user identity that will be used to give your CloudFront Distribution permission to fetch a private object
• Signed URLs : temporary access to cached objects not same with presigned URL)
• Signed Cookies : advantage of using a Cookie is you want to provide access to multiple restricted files.

TTL

• defines how long until the cache expires

Relational Database Service(RDS)

• Aurora, MySQL, MariaDB, PostgreSQL, Oracle, MSQL
• can't SSH into the VM running the db
• Multi-AZ is an option, 한 az가 대기할때 copy 가능(Synchronous)

Encryption

• older version 사용 못 할수도 있음
• KMS 로 관리됨 (Key Management Service)

RDS - Backup

• Automated Backups : 1~35 days, automated backups, manual snapshots
• Restoring Backups : 다시 복원시킬때는 새로운 instance 가 만들어짐 (endpoint 도)

Multi AZ

• Automatic Failover protection : 다른 AZ로 바로 복구
• Synchronous replication (highly durable)
• Only db engine on primary instance is active
• always span two AZ within a single Region

Read Replicas

• multiple copies 가능한데, 이것들은 오직 reads 만 허용함. (primary db 의 performance 향상시키기위해)
• primary RDS 와 replica 는 asynchronous (병렬적, 동시에 x) 로 작동한다.(highly scalable)
• 문제가 생기면 manually 백업 instance
• can be within an AZ, cross-az, or cross region

Aurora (Severless)

• serverless is inexpensive option
• Fully Managed and really fast
• high-end db, cost-effectiveness
• can span multiple regions via Aurora Global DB
• infrequent db usage is more ideal

Scaling

• Storage is autoscaling
• 알아서 늘어남 필요한만큼

Avalability

• 한 az는 2개의 copies 만들수있음

Fault Tolerance and Durability

• Aurora Backup and Failover is handled automatically
• 다른 aws 계정에 스냅샷 공유 가능
• Storage is self-healing

Serverless

• automatically start up, shut down, and scale capacity up or down
• 너가 쓴 만큼 자동으로 청구

Redshift

• petabyte scale solution for Data Warehousing
• Business Intelligence
• Online Analytics Processing System
• Columnar Storage : important factor in optimizing analytic query performance because it drastically reduces the overall disk I/O requirements and reduces the amount of data you need to load from disk(SQL-like Queries)
• can be loaded from S3, EMR, DynamoDB...
• 병렬처리 가능(Asynchronously)

Data Warehouse

• Online Analytical Processing : multiple records at the same time, you save memory because you fetch just the columns of data you need instead of whole rows.
• built to store large quantities and enable fast, complex queries
• long transaction

Node Types

• Dense Compute(dc) : best for high performance, but less storage
• Dense Storage(ds) : clusters in which you have a lot of data

Processing

• Massively parallel processing(MPP)
• automatically distributes
• add new nodes easily

Backups

• default -> 1day, Retention period can be up to 35 days
• different region snapshot replicate available

Security

• Encrypted using SSL, KMS

Availability

• Single-AZ
• To run Multi-AZ, you would have to run multiple RedShift Clusters in different AZs with same inputs.
• Snapshots can be restored to a different AZ in the event an outage occurs

Dynamo DB

• doesn't use SQL
• Fully managed, multi-region, durable db, backup and restore, in-memory caching, Consistent Reads
• All data is stored on SSD storage spread across 3 diff regions

Consistency

• Eventual Consistent Reads(Default Option) : when copies are updated, 다른 원본이나 copy들이 다 동일해지는건 아님(다른 데이터 읽기 가능), 하지만 결국에 동일해짐( within a second)
• Strongly Consistent Reads : 모든 데이터가 동일해질때까지 읽기 불가