High availability with Amazon S3 bucket region failover via CloudFront origin
Рет қаралды 2,525
Implement high availability with CloudFront origin failover of S3 bucket from one region to another region with the help of CloudFront Origin Group.
Timestamps:
00:00 Intro
00:29 Amazon S3 solution design for failover
01:43 Create Amazon S3 buckets in two regions
03:40 Create a CloudFront distribution
06:00 Upload object in Amazon S3 bucket
07:40 Make Amazon S3 bucket public
10:00 CloudFront Origin failover concept
10:47 Add another CloudFront origin
11:31 Create CloudFront origin group
12:23 Edit CloudFront cache behavior
13:12 Link CloudFront distribution to Route53
13:48 Simulate S3 region failover with http status code 404
16:49 Simulate S3 region failover with http status code 403
Link to Resources:
Bucket policy examples
docs.aws.amazon.com/AmazonS3/...
Host a static website on AWS S3 using Cloud Front Distribution and Route53
• Host a static website ...
@kendi6931 Жыл бұрын
Thanks Vibhor !👍
@ajsurkhi4468 2 жыл бұрын
Thanks for sharing a video. & showing lab & nice explanation
@deepakthankachan8443 3 ай бұрын
Hi, Thanks for sharing. Why does the 2nd bucket need to be publicly accessible? Can't both buckets be private (so only access via cloudfront is allowed) and have a bucket policy on each to only allow origin access identities declared in cloudfront? thanks
@hrishikeshkholamkar7104 5 ай бұрын
Hi sir, Can we implement failover on private bucket with the help of health check
@milindkhurd 2 жыл бұрын
Thanks Vibhor for a detailed video. Did you make the secondary bucket public to demonstrate S3 access of content only? It does nor have to be public for this setup to work. Is that right?
@tarvinder91 3 жыл бұрын
This was really helpful. Thanks for uploading. Though I am wondering if custom HTTP response codes will conflict with the origin failover.
@tarvinder91 3 жыл бұрын
I tested and the answer is that if u configure custom error code and origin failover for same error code, then on getting that error code from primary origin will first forward req to secondary origin. If request is satisfied, then ok, else custom error code would be returned to the user.
@vibhor-gupta 3 жыл бұрын
Your issue is resolved then
@ArunKumar-pm6fn 2 жыл бұрын
Hello Vibhav Nice explanation. Can you please make the tutorial for Cloudfront signed cookie.
@kayoutube690 2 жыл бұрын
Is this working for CloudFront that has lambda@edge integration?
@vibhor-gupta 2 жыл бұрын
Yes, it should
Vibhor Gupta - Product | Project | Technology
Рет қаралды 9 М.
Vibhor Gupta - Product | Project | Technology
Рет қаралды 2,9 М.
ОВР Шоу
Рет қаралды 9 МЛН
Vibhor Gupta - Product | Project | Technology
Рет қаралды 3,3 М.
Vibhor Gupta - Product | Project | Technology
Рет қаралды 15 М.
Vibhor Gupta - Product | Project | Technology
Рет қаралды 11 М.
AWS with Avinash Reddy
Рет қаралды 11 М.
AWS Route53 DNS Failover complete infra set-up | EC2, ELB, Route53 - High Availability | DR | Ubuntu
Dreametive _
Рет қаралды 4 М.
i-shoppers обзоры
Рет қаралды 2,1 МЛН
FISPECKT
Рет қаралды 238 М.
Toy Kid
Рет қаралды 29 МЛН