What needs improvement with Amazon S3?

AWS ( /products/amazon-aws-reviews ) should provide more attractive and comprehensive documentation, especially while integrating Amazon S3 with other AWS services like Elemental MediaConvert. Currently, the documentation can be difficult to understand, requiring additional resources such as AI, YouTube videos, or other aids. … No direct connector is available to connect Amazon S3 with other tools like MicroStrategy. So, I have to use a third party and connect to it. The solution's cost should be improved. The solution's performance needs to increase for small objects. Amazon S3 is excellent for large projects, but its performance can be comparatively slower for fewer small objects. … It is difficult to retrieve files in an emergency because the public cloud has data limits for immediate downloads so they often take twelve hours. We need better, immediate control of our content. The cloud and on-premises solutions should sync all data. Infrastructure services could be improved to provide free education related to the solution's features. For example, developers who do not have experience building games could learn how to do so with free support. … The pricing and licensing are pretty complex. It needs to be simplified. They have no development environment. That means that even during the development time, we are paying. The initial setup can be a bit complex. It would be helpful if there were more templates available. … The only pain point is migrating the life cycle policy because if someone is a newbie, they cannot easily create the life cycle policy. This is because there are multiple, additional ways. If I want to store data for one month, they have the option to Glacier over it. With Glacier, you have addition policies for one year or four years. The option will not be there. So you would need to use a UI process over it.