[FOLIO-3559] Decomission old AWS resources Created: 11/Aug/22  Updated: 10/May/23  Resolved: 16/Aug/22

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: Peter Murray Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: DevOps Sprint 160
Development Team: FOLIO DevOps
RCA Group: TBD

 Description   


 Comments   
Comment by David Crossley [ 11/Aug/22 ]

Regarding "folio-snapshot-test" – no, we actually use that for "testing" when doing new configuration changes and stuff.

Comment by Peter Murray [ 12/Aug/22 ]

Ah, okay. Does it need to be running all the time?

Comment by Oleksii Petrenko [ 12/Aug/22 ]

Hello Peter Murray 

All these environments are in us-east1 region.

Kitfox team is responsible for Rancher env that are placed in us-west2 region.

Please find responsible team for it

Thank you

Comment by David Crossley [ 12/Aug/22 ]

The folio-snapshot-test could be idle. We use it irregularly. 

What needs to be done to bring it back when we need it? Is that just to start it via the AWS EC2 UI?

Comment by Peter Murray [ 12/Aug/22 ]

Thanks Oleksii Petrenko — I'll take it from here.

David Crossley: You can just put it in the "Stopped" state....it'll stay that way until needed again ("Start"). We won't pay for CPU costs, but will pay a minimal cost for the EBS volumes...that little bit helps!

Posted a link to Slack and I'll plan to take these down on Tuesday morning.

Comment by Peter Murray [ 16/Aug/22 ]

folio-iris and folio-juniper instances terminated.

Generated at Thu Feb 08 23:29:01 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.