-
Notifications
You must be signed in to change notification settings - Fork 1
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
"Switch on-off" automation proposal #14
Comments
this is open for grabs I can help guide on it. it might be really fun! |
Would like to grab this! |
Adding some background here: The bastion works great. we use it for secure access to the DB. the client i use (Postico) can be configured to SSH tunnel so it's a seamless process to connect. Occasionally I set up a tunnel from a terminal. I connect for 2 reasons really.
The challenge is that the bastion as currently configured is in an auto-scaling group so it's designed to make it impossible to turn off. I can manually reconfigure the auto-scaling group but Terraform will change it back on the next push. The solution is deceptively simple. all that's needed to fix it is to set the min number of instances to 0 instead of 1 in the auto-scaling group. However, since it's a project referenced by a project referenced by a project and there are no variables to control this that's easier said than done... |
Possible Resourceshttps://github.com/hackforla/311-data/tree/dev/server/terraform |
More Context Regarding this as mentioned by - @jafow
|
A little bit of googling based on what you last mentioned @jafow . I came upon this
So what you are looking for is
|
After talking to @darpham . It seems like this is about the extent of the workflow file that is going to be needed to control the asg of the server |
Unassigning myself from this for the moment since I have not heard a response back on this in the last month and not sure where to go from here. |
Overview
What kind of repetitive thing do you have to do often and what is the benefit of automating it?
some HFLA projects use a bastion host for securing access to private resources (like databases or servers that do not face the public internet).
Running this bastion server all the time costs money, even though it's not always being used. This automation would set a timed or trigger-able action to launch and/or destroy one of these bastion servers when needed.
Ownership of Idea
Current State
"As-is" most likely something manual but could be partially automated
Future Development
Action Items/Research
Stakeholders
Impact - who benefits and how?
hfla projects using bastion hosts (ballotnav, 311, others?) will save $$ each month on hosting bill
Anticipated outcomes
Resources/Instructions
Language
Platform
Automation triggers (What starts it? What's it responding to?)
maybe both?
perhaps an action could run at 11:59PM PST every night and turn the bastion off.
then a person could launch it when they needed to
Input required (How much manual or custom input is required?)
a person should be able launch a bastion server by some github action -- an issue? a pr? a label? I dunno!
Output
(What's the desired result? What do we not want to see?)
Project size
The text was updated successfully, but these errors were encountered: