AWS CloudFront | Amazon CloudFront | Content Delivery Network | OAI | Visual Explanations

[@Pythoholic]

Timelines for your convenience: 00:20 - What is Content Delivery Network? How does it work? 01:18 - Single Server Distribution architecture 06:00 - Amazon Cloudfront and How does it work? 09:56 - Edge Location and Regional Edge Caching. 14:36 - What is Origin? 17:10 - How does CloudFront serve request? 19:59 - Restriction access to Amazon S3 content by using an Origin access identity. 22:52 - Using EC2 instance as the origin for CloudFront. 23:36 - Using ALB as the origin for CloudFront. 24:48 - How can I restrict users in certain locations from accessing web content served by my CloudFront distribution? Please follow we in the links below to stay updated: 🙌 🍀Click on the link below to subscribe: tinyurl.com/qqebnwz 🍀Instagram: instagram.com/tougherapollo/ 🍀Twitter: twitter.com/TougherApollo1 🍀Discord: discord.gg/dsZ6Wdh 🍀Join me on Mixer - Link - mixer.com/BytoRade

[@everettscott4745]

This is by far the VERY BEST EXPLANATION on youtube, on CDNs, Edge Locations, and CloudFront. There really isn't any video on youtube as good as this for explaining CloudFront in detail. It even mentioned Lambda@Edge; absolutely fantastic. I've been searching youtube for such a long time, but the content was weak or inaccurate. I thoroughly enjoyed your introductory content on a CDN. Your content is excellent. Many thanks for this.

[@Pythoholic]

Wow, thanks!

[@sampritadas2576]

Thanks for the detailed explanation, one of the best content on this topic for sure!!

[@Pythoholic]

Thanks for the support

[@sanilkhurana3991]

Amazing content as always, well explained, with great graphics to make it easier to understand, thank you!

[@jzxynow2a8gs21]

good pacing & good production quality, kudos!

[@vinitasharma6846]

Explanation was simple and absolutely wonderful. Please do include case studies as well

[@Pythoholic]

Sure would take this point 🙂 thanks for the feedback

[@shrinivasjadhav6162]

Hi, I have cleared SAA c03. Your videos are amazing and very comprehensive. This the only channel which cleared all my concept thoroughly. Do you have videos for AWS SAP -02. I am pursuing for the professional certification.

[@Pythoholic]

Hello srinivas Many congratulations That's awesome , currently I don't have videos on that. But many congratulations once again

[@ananyachoudhary6163]

you are amazinggg dude!

[@Pythoholic]

thank u 🙏

[@JavierSanchez-co6gn]

Mate, this was a great and clear explanation! Do you have any videos about Cloudfront Caching?

[@Pythoholic]

Yes but it's more on the cookie part. Please check the Playlist

[@TheTandeddu]

Isn't KZbin distributed/Hosted on Google's Cloud offering? Good, video. Thank you for introducing the OAI; was wondering about that.

[@Pythoholic]

Yes it is

[@abhishekkumar-jo4en]

Can we cache a some paths like /profile/*, /setting/* etc which is in one of the target groups of ALB. CLOUDFRONT will be in Front of ALB. and Alb has different FrontEnd application's as a target groups for different paths. ( This should be default * ) no caching for other applications

[@ajaysinghpanwar6308]

The content shown in the video is very useful for preparing AWS certification. @pythoholic please also share its pdf version so that it can be quickly revised if required.

[@Pythoholic]

Thanks for the support. Yeah sure it can be done

[@tshaylatte9502]

Thank you. Very useful

[@arfatbagwan48]

What about WAF at edge location

[@satishgadale3946]

If we are using ALB as a origin for distribution, EC2 Instances need not to be Public. mentioned at 23:53

[@mahadevanh]

nice tutorial. can you explain how will it work for dynamic content and hosting APIs? what is the benefit?

[@zcarfanatic]

Really great content here. Are you sure about not being able to use Static web-site S3 hosting bucket as an origin for CDN? (15:41) I'm fairly certain we did just that in a lab for the certification training. I could be wrong. Edit: ok, I see you went on to explain that is a custom origin config. Very nice...

[@akashachra7982]

Really nice explanation ✌🏻

[@Pythoholic]

Glad you liked it

[@akashachra7982]

Pythoholic yes i really liked it and waiting for the practical part and will also share after that

[@snaidu70]

at 18:09 the explanation is wrong. When a user types in a URL, it goes to the Domain Name Server for resolution. In this case, if the DNS is configured in AWS, it is Route 53. Route 53 should be configured to redirect the request to the edge location (using either latency or geo-proximity)

[@Pythoholic]

Yes technically you are correct, but the explanation is not wrong but may be insufficient. Please don't be so harsh :D just kidding, yes it does the route to DNS to resolve it but only if you have one. This was an overview of the explanation for simple understanding. Thanks for the feedback. It helps me keep myself in check.

[@buntybanik8614]

I am trying to follow this series, but the episodes are not in seq manner, so I'm finding it difficult

[@Pythoholic]

Oh ok. I have kept them in sequence, i will try to talk to youtube for this playlist settings.

[@akshaysharma-ji2xw]

Brother thank you for clearing the doubts I want to know is there any pop quiz like resources where i can test my knowledge before going for exam

[@Pythoholic]

Thanks for that, sorry currently i dont have that now, but u can try google or digital training cloud or whizlabs for the test paper. Please cover test papers before going to exam.

[@ranjeethnadella643]

If the user is closer to Origin, still accessing through edge location is recommended?

[@Pythoholic]

Not essentially. If u are using cloud front in realtime u must understand u are paying for the resources that you are using. Every request that is made costs you. So if your users are not far away from you and they are not facing lag or performance issues then its ok to not use it.

[@ranjeethnadella643]

@@Pythoholic will system decide how end user has to be serviced? Direct origin or though edge location. Am I right?

[@Pythoholic]

I think mostly the design team will decide if this application has to be served only in our region or it has to be wide spread. If the application grows they have to be scaled to meet the demand. The system decides when we have apolicy attached to it. May not be in this case. Unless u have a automation in place. Mostly it works with asg. With cloud front u decide what is the static content that is most widely used and which has become a bottleneck , for that we try and distribute it with cloudfront

[@abibhavana]

Do You have Cloudfront failover hands on lab

[@Pythoholic]

No sir not yet. Will make one soon

[@abibhavana]

@@Pythoholic you are one of the best channel to learn AWS. Can you tell some simple projects for beginner and intermediate

[@Pythoholic]

Here are some simple AWS project ideas 1. **Deploy a Static Website on S3:** - **Objective:** Learn how to use Amazon S3 to host static web resources like HTML, CSS, and JavaScript files. - **Key Services:** Amazon S3, AWS IAM, Route 53 (optional for custom domain). - **Steps:** 1. Create an S3 bucket and enable static website hosting. 2. Upload the static web files to the S3 bucket. 3. Update the bucket policy to make the content publicly accessible. 4. (Optional) Configure a custom domain using Route 53. 2. **Simple Web Application with DynamoDB:** - **Objective:** Develop a simple web application that uses DynamoDB to store data. - **Key Services:** AWS Lambda, Amazon API Gateway, Amazon DynamoDB, AWS IAM. - **Steps:** 1. Create a DynamoDB table to store data (e.g., a simple CRUD for tasks or notes). 2. Implement Lambda functions to handle CRUD operations on the DynamoDB table. 3. Use API Gateway to create RESTful endpoints for the Lambda functions. 4. Secure the application using appropriate IAM roles. 3. **Deploy a Python Flask App to Elastic Beanstalk:** - **Objective:** Learn how to deploy a simple Python Flask application using AWS Elastic Beanstalk. - **Key Services:** AWS Elastic Beanstalk, Amazon RDS (optional for a database). - **Steps:** 1. Develop a simple Flask application on your local machine. 2. Package the application with any dependencies and a configuration file (`requirements.txt` and `.ebextensions`). 3. Deploy the application to Elastic Beanstalk using the EB CLI or the AWS Management Console. 4. (Optional) Add an RDS database and connect it to your application. 4. **Serverless Image Resizer:** - **Objective:** Create a serverless application that automatically resizes images uploaded to S3. - **Key Services:** AWS Lambda, Amazon S3, Amazon SNS or SQS, AWS IAM. - **Steps:** 1. Create an S3 bucket to upload images. 2. Implement a Lambda function triggered by S3 events to resize images using a library like Pillow. 3. Store the resized images in a different S3 bucket or the same bucket with a different prefix. 4. Configure any necessary permissions and roles for Lambda to access S3. 5. **Basic CloudWatch Dashboard:** - **Objective:** Set up a CloudWatch dashboard to monitor the performance and health of AWS services. - **Key Services:** Amazon CloudWatch. - **Steps:** 1. Identify which metrics are important for your application or environment. 2. Create a CloudWatch dashboard and add widgets to visualize these metrics. 3. Set up CloudWatch alarms to notify you of any critical changes in the metrics. 6. **Simple Notification System:** - **Objective:** Implement a notification system using SNS to send messages to subscribed endpoints. - **Key Services:** Amazon SNS, AWS Lambda (optional), AWS IAM. - **Steps:** 1. Create an SNS topic. 2. Subscribe email addresses or phone numbers to the SNS topic. 3. Publish messages to the topic either manually from the AWS console or programmatically using AWS SDKs. 7. **Lambda Function to Process Logs:** - **Objective:** Develop a Lambda function to process log files uploaded to S3. - **Key Services:** AWS Lambda, Amazon S3, AWS IAM. - **Steps:** 1. Create an S3 bucket for log file uploads. 2. Write a Lambda function to parse log files (e.g., for error monitoring or usage statistics). 3. Set up an S3 event notification to trigger the Lambda function when new logs are uploaded.

[@Raakidevi]

well explained but demo would have give better understanding..

[@Pythoholic]

There is a demo as well

[@linkshri]

@@Pythoholic Could you please share the Demo url. I dont find it here. Thanks again.

[@jaypatz3541]

Need help i need amazon account veriefied can make cloudfront.. anyone here please?.

[@pranotidesai5084]

This is just reading out your slides. I wish you could explain things instead.

[@Pythoholic]

Thanks a lot pranoti. I will keep this as a feed back and improve on it. Please check out thr newer videos I have made changed