Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stop instance from starting #454

Open
kenlawrie1 opened this issue May 4, 2023 · 3 comments
Open

Stop instance from starting #454

kenlawrie1 opened this issue May 4, 2023 · 3 comments
Labels
enhancement triaged Has been triaged by solutions team

Comments

@kenlawrie1
Copy link

Hi,

We have been running Instance Scheduler for a while now with out too many issues

Once minor issue I have just found, that is costing us money, is if we manually power off an instance that isn't required for a while, and it has a schedule tag attached to it, it automatically starts again the next day.

Is there and option, the opposite to the retain_running, where if an instance was manually powered off, it will remain off?

I know we can just remove the tag, but this is difficult to remember to do, a better option would be to remain off indefinitely if manually powered off.

Thx :-)

@CrypticCabub CrypticCabub added enhancement triaged Has been triaged by solutions team labels May 4, 2023
@CrypticCabub
Copy link
Member

Hi @kenlawrie1

We do not currently support this use case, but it is a very interesting one to consider. I have added it to our backlog for further review by the team.

If anyone else would also like to see this feature added, please upvote the original post by clicking on the 'thumbs-up' emoji.

@aws-solutions aws-solutions deleted a comment from easante817 May 30, 2023
@CrypticCabub
Copy link
Member

CrypticCabub commented May 30, 2023

please stay on-topic when commenting on issues

@johancarstens
Copy link

johancarstens commented Oct 15, 2024

Hi, I am currently doing this in version v1.5.5 for EC2 and RDS and v3.0.5 (only tested on EC2) of instance scheduler by simply deleting the begintime and only defining an endtime in the period.

Have been using this for some time now in our DEV account to stop instances and RDS at night.

Instances tagged with this schedule must be started manually which is exactly what we need.

e.g:

{
  "type": {
    "S": "period"
  },
  "name": {
    "S": "za-stoponly-1730-mo-su"
  },
  "description": {
    "S": "za-stoponly-1730-mo-su"
  },
  "endtime": {
    "S": "17:30"
  },
  "weekdays": {
    "SS": [
      "mon-sun"
    ]
  }
}

INFO : Scheduling decision for EC2:i-xxxxxxxxxxxxx (instance-schedule-testing): action: SchedulingAction.STOP reason: State transition from any to ScheduleState.STOPPED

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement triaged Has been triaged by solutions team
Projects
None yet
Development

No branches or pull requests

3 participants