Your video is fantastic and helpful . Do you have video to delete snapshot automatically based on tagging information example "Delete" - "2023-05-01" the snapshot should delete on the date I set l.
Thanks for watching, Perfect_Circle! 😊 I don't have a video about this, but you probably want to check out Data Lifecycle Manager: docs.aws.amazon.com/AWSEC2/latest/UserGuide/snapshot-ami-policy.html. That will let you set up retention policies based on age or count. Hope that helps!
Great tutorial! I had a couple questions if you don't mind :) 1) How to schedule a RDS instance? You mention that you can use this solution. What would be different here? Is it just a matter of placing a tag of the schedule on the RDS instance? 2) How does this solution compare to creating a Maintenance Window in AWS Systems Manager on the EC2 instances(s)? Thank you for your time!
Hi Shawn! 👋 1) I haven't tried this with an RDS instance yet, but as far as I know, yes, you'd just need to tag the instance, just like you would a "regular" EC2 instance. I don't see anything in the documentation about needing to do anything special for RDS. 2) Instance Scheduler will work with SSM Maintenance windows (but only for EC2 instances, not RDS), to start and stop instances for the window. There's a field for that in the schedule: docs.aws.amazon.com/solutions/latest/instance-scheduler-on-aws/schedules.html#ssm-maintenance-window-field Hope that helps! Thanks for watching! 🌟😊🙏
@@TinyTechnicalTutorials Thank you for your quick response. Do you have a preferred social media platform to connect? I have some ideas about technical content creation, and would like to share. Thanks again.
Hi Ahmed! 👋 I'd say the answer is "it depends." 😊 AWS Instance scheduler is the simpler way to go (it's easy to set up, you don't have to write code...), but if you need more control and have complex scheduling logic, etc., then EventBridge/Lambda would be the way to go.
Hi Prayas Finance! 👋 The parameter for "Instance Scheduler tag name" was set when you created the CloudFormation stack (see around 03:17 in the video). So you should be able to go back into that CloudFormation stack and look at the details (I've already deleted mine, and can't remember the exact tab/screen it's on, but it should be somewhere there in the stack itself). Hope that helps. Thanks for watching! 🙏🤓🌟
Great video! Can there be a second tag added for a patching schedule? For example, I want all of my machines to shutdown at 5pm Monday-Friday, but on the last Saturday of the month, I want them all on for patching. How would something like that work? Thank you.
Hi Rashan! 👋 Sorry for the slow response! I haven't tried that scenario myself, but it *should* be possible. You can have multiple periods in a schedule, and there are also fields for "days of the week" and "days of the month" that seem suited to a "last Saturday of the month" situation. You'll probably have to experiment a bit to get it just right, but here's the documentation if you need it: docs.aws.amazon.com/solutions/latest/instance-scheduler-on-aws/period-rules.html
@@TinyTechnicalTutorials Thank you for your response. I will go through the documentation and give it a try. I'm currently using System Manager Maintenance Windows with run commands/automation documents to handle the start/stop, but I'm curious to give this alternative a try. Thank you again.
Great tutorial! If I wanted to just set a time to shut of an instance and not have it automatically start, then would that simply be done by excluding a "begintime" keypair in the schedule item?
Upon revisiting to provide further feedback, I encountered significant confusion while following your video instructions, particularly on two aspects: Time Zone configuration. Settings within the Config Table on DynamoDB. I found myself needing to watch another RU-vidr's highly detailed video to resolve the time zone setup issue, as the scheduler wasn't functioning properly. Nevertheless, I eventually managed to address it. Regarding the Config Table modifications in DynamoDB, a crucial point to note is the hierarchy of parameters. There are three types: config, schedule, and period. When schedule applies to the instances, the scheduler first seeks the schedule tag on the Config Table. Initially, it looks for the schedule; hence, it's imperative to have the same parameters in the periods section of the schedule to identify the period type, as the scheduler targets it next. Within the period type, you establish the start and end times before configuring the time zone. It's crucial to ensure that the time zone configuration matches across both the config and schedule. Additionally, it's essential to note that the Scheduler and Instances must be in the same region-whether it's N. Virginia, Ohio, N. California, etc.-to ensure proper functionality; otherwise, it won't work as intended. Appreciate for the contents, it was huge help to configure my server's schedule.
Hi, unfortunatelly when i create Stack just like you showed in the video, it does not create any tables in DynamoDB. It hase been more than an hour since creating the stack and it says ConfigTable CREATE_COMPLETE. Would you have any advice on how to continue? Thank you. I am reffering to 6:50
@TinyTechnicalTutorials I have launched an EC2 insatnce from Mumbai Region set the timezones at every step to 'Asia/Kolkata' but the instance is not shutting down as expected. Instance is not encrypted.
@@TinyTechnicalTutorials Yes I was. If I wanted the instance to shut down at a particular time. The 'Begin Time' should be before my current time. Same with starting up, the 'Begin Time' should be before my current time. It'll still work even if you don't do this, but it will execute the schedule on the following day. (P.S. This is purely for testing purposes.) Thank you for the wonderful and clear tutorial.
Hi Sai! 👋 I haven't used books for AWS in a long time, as I find they get out of date quickly. But you can find all sorts of them on Amazon, from general overviews to specific services: www.amazon.com/s?k=amazon+web+services&crid=3PD1FWTAW2WW6&sprefix=amazon+web+service%2Caps%2C152&ref=nb_sb_noss_1.
Hi Sushant! 👋 Yes, you can use this for shutdown only (you don't have to use it for starting too). This tutorial is probably a little bit out of date, but it should have the right values you need in the database and such: www.pluralsight.com/cloud-guru/labs/aws/use-aws-instance-scheduler-to-shut-down-an-ec2-instance. Hope that helps! 🌟😊
Hi Felipe! 😊 I can't find an official list of zones for AWS Instance Scheduler, but found a good list for Athena. Perhaps these are universally used in all AWS services? docs.aws.amazon.com/athena/latest/ug/athena-supported-time-zones.html
Nice tutorial.....just one query here Lambda is stopping and starting the tagged instance based on Cron given in the DynamoDB table but how frequently or what makes Lambda to poll this cron data from database everytime to ensure that the timing is correct to take an action on tagged instance?
Hi Vinod! It's actually a CloudWatch event that invokes the Lambda function at the defined interval. You can check out more on "Step 1" here under the "Technical details" section: aws.amazon.com/solutions/implementations/instance-scheduler-on-aws/ Hope that helps! Thanks for watching! 😊🙏
@@TinyTechnicalTutorials Thanks, that makes sense..... can I also put it this way that without this Instance Schedular, a lot of things like setting up Lambda, and CloudWatch Event we were supposed to do it manually and now with Instance Schedular and with its CloudFormation script, it is all automated. Now DynamoDB is storing the cron data whereas in the traditional way, we had to manually configure the cron at the CloudWatch/EventBridge level?
I think that's a fair summary. It was possible to do all of this manually before, but with this solution, things are automated/magically set up for you. 🤓
@@TinyTechnicalTutorials I was architecting a similar solution using the old traditional approach for one of my use cases for my company and suddenly yours video tutorial on RU-vid popped up for me which really gave me some great idea. Thank you, I really appreciate your efforts. Keep up with good work.
AWS has a Free Tier that covers a lot of the core services for the 12 months of your account. You can find more details here: aws.amazon.com/free/. Hope that helps. Thanks for watching! 🤓🙏🌟
Hi, i want to automate my instance to schedule on and off on weekends. But the challenge is if the instance is using on Friday and Saturday it will automatically on. Can you please help me on this?
@@TinyTechnicalTutorials I want to off unused instance on weekends like Saturday and Sunday. Again if any instance is used on weekends the instance should be on automatically
