Spike: Make a plan for S3 storage management

[exalate-issue-sync]

Right now, we’re forever generating .fec files in s3 - eventually, we will run out of space. We need a plan to manage storage sustainably.

Q: What expectation/business need do we have for a user to be able to retrieve the .fec report as filed? This will need to be taken into consideration when we make a storage plan

QA Notes

null

DEV Notes

null

Design

null

See full ticket and images here: FECFILE-1949

[exalate-issue-sync]

Laura Beaufort commented: [~accountid:61b0b42cd5986c006a9e1c94] is this question on your radar for requirements meetings?

Q: What expectation/business need do we have for a user to be able to retrieve the .fec report as filed? This will need to be taken into consideration when we make a storage plan

[exalate-issue-sync]

akhorsand commented: [~accountid:5b92c509d0b4022bdc51bdf4] our last requirements conversation about this ended with no requirement for storing different versions of the report. This was back in 2022 however, so we can certainly revisit.

Also FYI we have two tickets in Design Review for informing the user that what they see in our system does not necessarily reflect what was submitted to FEC given how our data works. [https://fecgov.atlassian.net/browse/FECFILE-1539|https://fecgov.atlassian.net/browse/FECFILE-1539|smart-link] and [https://fecgov.atlassian.net/browse/FECFILE-1540|https://fecgov.atlassian.net/browse/FECFILE-1540|smart-link]