Cost for AWS is significally higher than membership fees, EBSCO is funding additionally
Proposition: resources need to be ramped up to keep the development speed
Question: why do the dev teams not pay for their own environments?
Because the necessary environment is too big to be run on single machines
Maybe possible in a new architecture
AWS for EUREKA and OKAPI platform development
Expectation that there will be much reduced OKAPI support after the sunflower release, but will still need some
Current numbers include accounting for reserved instances
Current cost spreadsheet does not include all dev team environments
ID dev teams not included, they use ID infrastructure
GBV teams use GBV infrastructure - @Kemner-Heek, Kirstin going to check
Options that have been thoughts about
Reduce number of large DB - working on this, maybe can do 2
Cheaper instance types
Evaluating purchase of reserved instances - done
AWS cost optimization - done
Changing the dev roadmap - don’t move everything forward
Change timing of Eureka - could it be moved forward later
Members data center - move some instances to member data centers as opposed to AWS
Better pricing from AWS - continue working on this
Release environments - just keep one previous release, this is part of the later
How much do we plan/want to spend?
@Kathleen Berry notes we have previously kept spending to $20k/month for the last few years. Should have recommendations for change earlier
Since June 2024 coinciding with Eureka platform development, actual monthly costs approach $30,000/month.
No-Eureka estimate would be $273k
Yogesh can estimate which of the environments are logically central rather than per dev team (typically the rancher environments)
@Simeon Warner proposal: We direct those setting up community funded environments not to exceed $30k/month spending for the time being. This would still lead for deficit spending but would not dig us a deeper hole.
Agreement from @Boaz Nadav Manes@Rachael Kotarski@Mike Gorrell@Shawn Nicholson@spampell@Simeon Warner ; no votes against
ACTION - @Simeon Warner to follow up on CC slack
Additional support from @Kemner-Heek, Kirstin , @Joseph Grobelny