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

Scale service at start and end of day #853

Closed
chriswilty opened this issue Mar 4, 2024 · 0 comments · Fixed by #854
Closed

Scale service at start and end of day #853

chriswilty opened this issue Mar 4, 2024 · 0 comments · Fixed by #854
Assignees
Labels
infra/devops Related to infrastructure or project config

Comments

@chriswilty
Copy link
Member

I've noticed that AWS costs are about $3.50 per day when the fargate service and load balancer are up and running.

We can reduce these costs by bringing the service down at end of day, then up again at start of next, plus only having the service available mon-fri. At this stage it's unclear how that will affect availability of the load balancer, so we might need to bring that up/down as well, unless Fargate manages that for us.

In the UI, we might need to show some sort of "webapp is offline" page when the service is down, instead of showing the full app with a "could not reach service" message in the chat panel. Need to investigate this, but in any case it might be better as a separate issue.

@chriswilty chriswilty added the infra/devops Related to infrastructure or project config label Mar 4, 2024
@chriswilty chriswilty added this to the Remote deployment milestone Mar 4, 2024
@chriswilty chriswilty self-assigned this Mar 4, 2024
@chriswilty chriswilty linked a pull request Mar 6, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infra/devops Related to infrastructure or project config
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant