In line with the purpose of DB Bastions and in order to reduce infra costs, we encourage all product teams to review their DB Bastion Instances currently running in tvlk-prod and other AWS accounts. Make sure the DB Bastion is running only when you need to troubleshoot your databases or execute ad-hoc queries. Once your task is finished, terminate the bastion.
DB Bastions were never meant to be run continuously. From inception, we have been placing them into an AutoScaling Group (ASG), so they can be easily launched and terminated as needed by altering the desired capacity parameter of the ASG. If every product team shuts off their idle DB Bastion, cumulative savings can be quite high.
aws \
autoscaling \
describe-auto-scaling-groups
aws \
autoscaling \
set-desired-capacity \
--auto-scaling-group-name {{name of your auto scaling group}} \
--desired-capacity 0
Here is the list of DB Bastions currently running in tvlk-prod account. If one or more instances listed belong to your product domain, check if you actually need them to be running 24/7.Please review your dedicated AWS accounts as well.
Total potential saving ~$1,026 / month in tvlk-prod alone (from data collected on April 6, 2020)
Original blog post:
https://29022131.atlassian.net/wiki/spaces/SI/blog/2020/04/06/1322254482/psa+Shut+down+DB+Bastions+to+reduce+cost