The insights-ros-ingress performs the minimal requirements for receiving an upload, transforming it to a ros-supportted structure and copying it to ros-data bucket.

The purpose of the spike to confirm the original ingress service has no further responsibilities in this context, e.g. no validation for the upload itself (see https://github.com/redhatinsights/insights-storage-broker as one of the points to explore).

Examine the origin insights-ingress-go configuration and compare them to the insights-ros-ingress service to identify responsibility that wasn't converted.