We inherited a way of naming s3 objects which might have been fine in its original context, but is not optimal for AWS. For S3, we should not be prefixing all of our s3 objects with "service-" because it pushes everything onto one partition, which will affect search speeds as we scale. Change the name format to "-service"
Note: This PR is has a matching PR on the api side. They should be checked in at the same time. Also, testing this is hard because we've used up our message quota on staging.
Description
We inherited a way of naming s3 objects which might have been fine in its original context, but is not optimal for AWS. For S3, we should not be prefixing all of our s3 objects with "service-" because it pushes everything onto one partition, which will affect search speeds as we scale. Change the name format to "-service"
Note: This PR is has a matching PR on the api side. They should be checked in at the same time. Also, testing this is hard because we've used up our message quota on staging.
Security Considerations
N/A