As Alexei mentioned, this is possible from SQL 2022. If you are on an older version of SQL Server I would recommend using File Gateway. Using a file gateway will simplify your backup and restore operations vs writing to local storage and using scripts to push the files to S3. Using command line tools to push large files to S3 can also be quite CPU intensive and will increase your overall backup time.
If you do need backups from S3 it can also be painful to have to pull them down to local storage to restore them.
File Gateway works as a file share that is backed by S3 storage. So you just write your backups to a UNC path and works with Ola's scripts. Restores also work directly from the File Gateway.
It does have a cost associated with it though. In our case, this was completely offset by reducing the amount of EBS storage we needed. We didn't need to duplicate our backup storage on the passive node. Also, you might not need quite as big a volume for the cache on the File Gateway.
Want more information on mysql backup to s3? Click the link below to contact us.