@tomasbedrich First of all, thanks a bunch for the AWS S3 integration, this is really cool!
Only downside, it checks the endpoint against AWS_DOMAIN and therefore cannot be used with other S3 compatible providers.
I’m a coder, although not Python, but it’s easy enough to circumvent the AWS_DOMAIN check condition in the config flow. Unfortunately, even after copying your integration to custom_components and rebooting the Yellow, the original component was loaded rather than my custom clone. So I can’t confirm it to work, but since all my other backups have no trouble at all talking to the S3 compatible bucket by Hetzner, I’m very confident it would.
How about replacing the hard check with a more subtle one. Maybe when entering a non-matching endpoint URL, just display a warning that this is untested and may or may not work instead of flat out refusing it?
Thanks a lot for considering this, I’m sure, many like me would be very happy about finally being able to create backups to compatible S3 endpoints!
Cheers, -sven