Open leovegoda opened 2 months ago
+1
+1
+1 as long as we can cap the max amount of spin up to avoid a giant bill
+1 as long as we can cap the max amount of spin up to avoid a giant bill
+1
+1
On Thu, Mar 14, 2024 at 17:12 Arnold Nipper @.***> wrote:
+1 as long as we can cap the max amount of spin up to avoid a giant bill
+1
— Reply to this email directly, view it on GitHub https://github.com/peeringdb/peeringdb/issues/1561#issuecomment-1998491098, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFA2YQWSKBP4MD7MCF33J3TYYIHCZAVCNFSM6AAAAABEHMXK6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJYGQ4TCMBZHA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Is your feature request related to a problem? Please describe. Followup from https://github.com/peeringdb/peeringdb/issues/1466
Switch www.peeringdb.com to ECS/Fargate
Who is affected by the problem? Improve operational efficiency
What is the impact? Improve site responsiveness and better manage costs
Are there security concerns? No
Are there privacy concerns? No
Describe the solution you'd like Deployment based on the tests done for Followup from https://github.com/peeringdb/peeringdb/issues/1466
Do you think this feature will require a formal design? Yes as per Followup from https://github.com/peeringdb/peeringdb/issues/1466
Describe alternatives you've considered Do nothing
Could this feature request need support from the Admin Committee? No
What is the proposed priority? To be decided by the Operations Committee
Provide a rationale for any/all of the above Improve site responsiveness and better manage costs