We encountered a platform outage due to a customer uploading several problematic archives on 1/19/2023.

These archives contained yum.repos.d files that were over 150M which was due to what appears to be errant data throughout. The same repo definition was added many times.

We need some sort of mechanism within ingress that would allow us to block a particular orgID from uploading until they resolve their problem with the archives. Ingress is the first logical place for it since we have the identity header available to us. 3scale and akamai do not currently have the ability to block an account/orgID in this manner at this time.

We also have a ticket open with the essentials team to attempt to block archives that have unreasonably high file sizes within.