Пікірлер

• 
  @anoops7974Күн бұрын

  Thank you so much. I learnt a lot on ansible.

• 
  @Hdhshsbssjsjsj2 күн бұрын

  very good explaination.

• 
  @venugoutham41155 күн бұрын

  Wow! Very good explanation! I really enjoyed learning...thank you!

• 
  @codyshamloo35055 күн бұрын

  Great video, to the point. thanks..

• 
  @anantgaonkar94111 күн бұрын

  Thanks for the podcast, Very nicely done. Keep it up buddy

• 
  @stevejob67711 күн бұрын

  great session

• 
  @leeoswald979911 күн бұрын

  Another terrible Indian accent video.

• 
  @kolawolegabriel655814 күн бұрын

  @Pythoholic, you are gifted teacher. Please can you make an explicit vide on AWS S3 Accesspoint practical with full demo

• 
  @kolawolegabriel655814 күн бұрын

  @Pythoholic, you are gifted teacher. I appreciate your videos. Please can you make an explicit vide on AWS S3 Accesspoint practical with full demo

• 
  @kolawolegabriel655814 күн бұрын

  @Pythoholic, you are gifted teacher. Please can you make an explicit vide on AWS S3 Accesspoint practical with full demo

• 
  @kanishkjohari223814 күн бұрын

  so nicely explained. I am just starting to get into hosting and this really helped me

• 
  @abhijitjadhav445616 күн бұрын

  11 Videos are unhidden any update

• 
  @Pythoholic15 күн бұрын

  I will check and get back

• 
  @abhijitjadhav445616 күн бұрын

  Not able to see next video under this playlist

• 
  @Pythoholic15 күн бұрын

  I will update it . Thanks for the feedback

• 
  @anwar6971Ай бұрын

  Too elaborate and very, very ambiguous.

• 
  @Pythoholic23 күн бұрын

  Thanks for the feedback. Will try and improve

• 
  @anwar6971Ай бұрын

  Too elaborate and very, very ambiguous.

• 
  @DaveLau0313Ай бұрын

  The threshold is too high. As a beginner, I don't comprehend these.

• 
  @c-bass413Ай бұрын

  Great demo.

• 
  @arfatbagwan48Ай бұрын

  For each VPC that you want to associate with the Route 53 hosted zone, change the following VPC settings to true: enableDnsHostnames enableDnsSupport what about this require a hands on this to understand the concept 😶

• 
  @ravinamohite9031Ай бұрын

  Best tutorial ever 😊 Thanks u so much for provide us from scratching 🙏🏻😊

• 
  @thelazychewresearchАй бұрын

  Great video!

• 
  @priyatiwari6331Ай бұрын

  Wonderful explanation please make a more viedo for api gateway and ECS and batch services

• 
  @nerdy-zeig7774Ай бұрын

  So... its just a cloud version of a jump server?

• 
  @sergioz71332 ай бұрын

  🤭 Promo sm

• 
  @nickwales42612 ай бұрын

  This was useful but would have been nice to see you actually make a request to the service.

• 
  @maddysunshine41732 ай бұрын

  very helpfull Video

• 
  @pulenteria2 ай бұрын

  Como retiro mi dinero de esta web?? La tenia en Trust y paso a esta web por arte de magia

• 
  @sidds092 ай бұрын

  Thank you. Please add continuous updating process of the site. also do more projects.

• 
  @Pythoholic2 ай бұрын

  Thanks siddb09

• 
  @JamesBrown-lq5nn2 ай бұрын

  Good brief intro to hosted zones👍

• 
  @venkatrao78682 ай бұрын

  Amazing explanation and demo !!

• 
  @rupaPrajapati-hg1ni2 ай бұрын

  Hey I had a quick question can we still do this with Application load balancers ? or we have to have network load balancers for service endpoint creation at producer end.

• 
  @Pythoholic2 ай бұрын

  As of recent updates, Application Load Balancers do support AWS PrivateLink. You can create an endpoint service in your VPC and specify an ALB as the service provider. This allows you to offer the applications behind your ALB privately to other VPCs through AWS PrivateLink. If there are any specific documentation you can refer i can help you better where they have mentioned dropping support.

• 
  @pavan90762 ай бұрын

  Any specific reason we are using Lambda or SQS before SNS, can't we send payload directly to SNS??

• 
  @Pythoholic2 ай бұрын

  You can definitely send payloads directly to Amazon SNS without using AWS Lambda or Amazon SQS. The choice to use services like Lambda or SQS before SNS often depends on the specific requirements of your architecture and the nature of the data processing involved. Here are some reasons why you might use AWS Lambda or Amazon SQS before sending a message to SNS: 1. **Data Processing with Lambda:** - **Complex Transformations:** If the payload needs to be processed or transformed before sending the notification, using Lambda is a common approach. For example, you might need to extract specific information from a larger dataset or format the message in a particular way. - **Conditional Logic:** Lambda allows you to implement complex logic to determine whether a notification should be sent. For instance, you might only want to trigger an SNS notification under certain conditions after inspecting the incoming data. - **Integration Logic:** Sometimes, the decision to send a notification via SNS depends on the results of integrating with other services. Lambda can handle these integrations (e.g., querying a database or calling an external API) before deciding to send a message to SNS. 2. **Decoupling with SQS:** - **Rate Limiting and Throttling:** If your system produces notifications at a high rate, you might use SQS to buffer these messages. This helps in managing throughput to SNS, especially if there are many subscribers or if the subscribers have rate limits. - **Reliability and Durability:** SQS provides a reliable queueing system that ensures that messages are not lost between your application and the notification service. If your system requires a high degree of reliability, using SQS as a buffer can help protect against data loss in case of transient errors. - **Retry Logic and Dead Letter Queues:** SQS can be used to manage retries in a more controlled manner. If a message fails to be processed or sent to SNS, it can be retried or moved to a Dead Letter Queue (DLQ) for further investigation. This helps in isolating problematic messages and ensures that your system remains resilient. 3. **Direct Use of SNS:** - **Simplicity:** If your application simply needs to send a notification with minimal processing, sending the payload directly to SNS is the simplest approach. This reduces the complexity and operational overhead of your architecture. - **Real-Time Notifications:** For scenarios where you need immediate notification without any delay, sending direct messages to SNS is preferable. This ensures that there is minimal latency between the event occurrence and the notification being sent out. 4. **Cost Considerations:** - Using Lambda or SQS introduces additional costs based on their usage (invocations for Lambda and the number of messages for SQS). Directly using SNS might be more cost-effective if the additional features provided by Lambda or SQS are not required for your use case. In summary, while sending payloads directly to SNS is a common and straightforward approach, using Lambda or SQS as intermediaries can provide additional flexibility, processing capabilities, and reliability features based on your specific needs.

• 
  @catchroniclesbyanik2 ай бұрын

  Based on the formula, if I have a requirement of 3000 rcu and 1000 wcu, the table will initially create 2 partitions. But why need 2, why not 1 ??. 1 partition is sufficient for the requirement. Assume data size is under 10 GB. Please anybody care to explain ??

• 
  @Pythoholic2 ай бұрын

  DynamoDB might start with 2 partitions instead of 1 for your requirements of 3000 RCUs and 1000 WCUs to better balance the load and improve performance consistency, even if one partition can technically handle the capacity. This approach also enhances fault tolerance and operational flexibility by distributing the workload across multiple partitions from the start.

• 
  @catchroniclesbyanik2 ай бұрын

  @@Pythoholic I think, I have figured out why 2 partitions are needed and not 1. One partition can deliver either 3000 rcu or 1000 wcu or mix of both (i.e. if it has 500 wcu it can have 1500 rcu). It is not possible for a partition to deliver both 3000 rcu and 1000 wcu. By this logic, if one partition delivers all the required 3000 rcu, one more partiton is required to deliver 1000 wcu. Since they are distributed equally among partitons, each partition will deliver 1500 rcu and 500 wcu.

• 
  @catchroniclesbyanik2 ай бұрын

  The thing which is missing from most documentation online, is its not 3000 rcu and 1000 wcu. Its 3000 rcu or 1000 wcu or a mix of both. By this logic, one partition won't be able to handle that load. You must need two. I got this information from an AWS Events video posted on YT about DynamoDB.

• 
  @AbhayAR2 ай бұрын

  U are a man or james bond ?

• 
  @glennadams70472 ай бұрын

  Best explanation of endponts ! Well done sir !!!

• 
  @narongritsrisawang36102 ай бұрын

  very helpful thank you :D <3

• 
  @kirodezno122 ай бұрын

  Great video, thanks! Keep up with the good work!

• 
  @abibhavana2 ай бұрын

  Do You have Cloudfront failover hands on lab

• 
  @Pythoholic2 ай бұрын

  No sir not yet. Will make one soon

• 
  @abibhavana2 ай бұрын

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

• 
  @Pythoholic2 ай бұрын

  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.

• 
  @ZobiaKhan-mc1fs2 ай бұрын

  19:00 bookmark

• 
  @vivekgc20512 ай бұрын

  Please provide the slides of all video ... Please

• 
  @saleemnashawaty31792 ай бұрын

  Thank you Chief

• 
  @StMarc-ow4wz3 ай бұрын

  This video should be removed to avoid wasting others' time.

• 
  @Pythoholic3 ай бұрын

  Point taken. Will try and improve. Sorry for the inconvenience

• 
  @ankitnegi1633 ай бұрын

  nice video

• 
  @root-User3 ай бұрын

  Lovely explanation. This has cleared all my doubts related to Graph Database. God bless you

• 
  @TechJedi0073 ай бұрын

  Not sure why, but I created the alarm, created a topic, and subscribed to the topic. I'm still unable to get any notifications even though the metrics I set were really low after running the stress test.

• 
  @sachinadi67153 ай бұрын

  This is an eye opener when it comes to ansible.. thanks for making this content @pythoholic

• 
  @Pythoholic3 ай бұрын

  Glad you enjoy it!

• 
  @MrLala123213 ай бұрын

  Beautiful job, really appreciate it. Subscribed!

• 
  @FaltuKaam-vq7ko3 ай бұрын

  nicely explained.

• 
  @StMarc-ow4wz3 ай бұрын

  This video could have been completed in 3 minutes if the creator did not keep repeating what he said.

• 
  @Pythoholic3 ай бұрын

  Thanks for the feedback I will surely keep this in mind

• 
  @agni48693 ай бұрын

  awsome course and very clear explanation with aws. so much helpful

• 
  @jagan19573 ай бұрын

  I don't know where to start and where to end but in this video you have talked about a lot of pertinent and pragmatic things that are relatable to any professional in the IT world. When I watched a few videos related to the AWS course, I realized that your videos were a class apart from the rest by giving vivid visualization. You are an inspiration for me. I passed out from 2011, joined Indian Navy as an officer but for some reason had to quit and come back home. Took a three month rest and then found a good job in Bangalore and started my career in 2012. I also had a lot of ups and downs and more importantly I too was laid off from my startup(Silicon Valley) a few months back as part of a big downsizing exercise but as I had the skills and self-confidence, I was jumping with joy on the day of layoffs that I had broken from the shackles of this company rather than feeling dejected about it. I am currently puruing the AWS entry level certifications and finding your content really great. I wish you all the very best and hope that you will be one of the finest content creators in this decade as there is a huge potential for online education.

• 
  @Pythoholic3 ай бұрын

  Thanks a lot Jagan for your wonderful story that you shared and its also so amazing that you are still going on after facing a lot of issues in your life as well. I am sure you will get all the things you want from life. I am really happy that i could help you in any way possible. May be my job as a content creator was just that. I will try my best to provide good content and share what i know with the best of my abilities. Thanks again :)