We've generally found that this sort abuse rarely happens. Generally developers utilize our services as they are intended. And it is much easier to release new services and watch for abuse than to pro-actively restrict them before-hand.
There is nothing wrong with storing blobs in the database - it is one of the data types. But a database is not a replacement for AWS S3 either.
If we did find someone abusively using the database - especially if it was affecting the overall quality of service - we would reach out to them directly to address it.
Comments
We've generally found that this sort abuse rarely happens. Generally developers utilize our services as they are intended. And it is much easier to release new services and watch for abuse than to pro-actively restrict them before-hand.
There is nothing wrong with storing blobs in the database - it is one of the data types. But a database is not a replacement for AWS S3 either.
If we did find someone abusively using the database - especially if it was affecting the overall quality of service - we would reach out to them directly to address it.