วีดีโอ

Thank you Rupesh!

Hari, Savings plan is discount which applied on top of your ec2 instance. You don't need to claim it. Check this aws.amazon.com/savingsplans/compute-pricing/

Thank you Shanawaz!

Thank you Vinny!

Thank you Kajol for the feedback, will improve the voice quality for upcoming videos.

@S Kularatna I didn't get your question, can you elaborate little more?

@@clouddeepdive let’s say I have 10 Ebs volumes not attached to any instance in available state and has been there for more than 2 years gp2 16gb size. Would it be significant cost

10 EBS 16 GB Gp2 volume will cost you around $16 per month ( 2 year - close to $385) calculator.aws/#/createCalculator/EBS

Thank you Rohit!

Thank you Usha for watching this video, hope you liked it and subscribed to the channel. Here is the answer to the question you asked - Savings Plans is available in 3 different payment options. The No Upfront option does not require any upfront payment, and your commitment will be charged purely on a monthly basis. The Partial Upfront option offers lower prices on Savings Plans. With this option you be charged at least half of your commitment upfront and the remaining will be charged on a monthly basis. With the All Upfront option, you will receive the lowest prices and your entire commitment will be charged in one payment. Source - aws.amazon.com/savingsplans/faq/

Thank you Ayush, hope you subscribed to the channel!

Great to hear Srinivasan that it helped you to reduce your AWS cost!

Thank you Nasirul! There is no minimum number which you need to purchase, you can purchase one RI or many based on your workload. Here is AWS documentation on how to purchase AWS EC2 RI - docs.aws.amazon.com/AWSEC2/latest/UserGuide/ri-market-concepts-buying.html Let me know if you still have any question.

Thank you Danish! Happy to know these videos are helping you to prepare for the exam. Feel free to reach out to me if you have any questions!

Hi Manoj, You want to check list of RIs purchased under your account? Please let me know if I misunderstood your question. Checkout this link - docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithReservedDBInstances.html#USER_WorkingWithReservedDBInstances.WorkingWith

@@clouddeepdive Yes , thanks for sharing link. I can see my running RIs RDS instance and their status.

AWS Instance Scheduler support only Start/Stop of EC2/RDS. - docs.aws.amazon.com/solutions/latest/instance-scheduler/welcome.html If you want to automate RDS scaling then you need to write something custom, I am not aware of any existing solution right now, will do some research and share if I will find any existing solution.

Hi Yeko, As this solution use different AWS services like Lambda, DynamoDb it will cost you money, how much depends on the usage.

In AWS documentation it is mentioned that it costs around 10 dollars per month to run this.

Thank you Swapnil for watching! Can you elaborate more on this - "if instance is in running state, than I want job to skip that instance and do not stop them" I am not clear on the question you have.

@@clouddeepdive So lets the requirement is to start 50 instances every sunday 6pm and stop at mid night. so 1st sunday, lets say all 50 are in stop state, job is going to start them all. at midnight, it is going to stop all 50. But next sunday at 6pm, when job tried to start all 50, 10 were already running, so job is going to start only 40 instances. But at midnight, job must stop only those 40 which it started at 6pm and do not touch those 10 in running state. so essentially, when it comes stop the instances, it should stop only those previous job started.

Just checking if this is possible.

For this you need to play with the tags on those instances. Instance scheduler works based on the tags you have on the resource.

Thank you 👍 Hope you subscribed ! Keep learning !

Thank you Sharath for watching this video. Hope you subscribed to our channel as well. Stop and Start will be like boto3 function which will be called from Lambda based on the timings you provide. You need to make sure you are not running any critical workload which fall on this schedule. Here is the AWS documentation on this - docs.aws.amazon.com/solutions/latest/instance-scheduler/welcome.html

@@clouddeepdive thank you very much for you reply it was very helpful

Thomas what AWS documentation is talking in this is you can create private hosted zone and then create a A record. Instead of using AWS issues domain name you can use custom domain defined in route53 private zone. Now when you try to resolve it from VPC both of these options should be enabled. Reason is whenever you send a DNS resolution query it first goes to route53 and if no hosted zone then it goes to outside DNS. If you don’t enable these options then it won’t use R53 to resolve DNS query Check this video for more information th-cam.com/video/qCxfukA50y4/w-d-xo.html

you can do that by adding a different period and use that in your schedule or by editing exiting period you are using.

Thank you ! Hope you subscribed to the channel as well!

You're welcome!

Thanks for the feedback, will try to make a video on the same.

Thank you for your feedback, will work on the same.

Glad you liked it!

Will try

Glad it was helpful!

Thank you so much 😀

Thank you Vinay ! Please let us know if you are interested in learning any specific topic, will try to record video on that. Also please subscribe to our channel, I am working on new AWS networking series which will help everyone to learn AWS networking concepts. I will cover upto level-400 concepts which will help you to clear Advanced networking certification as well.

@@clouddeepdive try to explain how to push metrics from eks cluster to AWS Prometheus

@@vinaygowda7413 sure will work on that.