[Fix] Change S3 logger to accept more authorization methods for AWS

[danieldabate]

This PR solves issue #3997 by making environment credentials optional for S3 logger, so they can be taken from different alternative sources like K8S service accounts.

[saqib-ahmed]

@danieldabate @HenryHengZJ

Can we please add unit/integration tests to prevent this sort of regression in future?

[HenryHengZJ]

However, others still have the same problem even though with this fix, are you guys still experiencing the problem? I was suspecting because it doesnt accept credentials: undefined?

I opened a PR (#4166) to only set credentials when both keys are found

[danieldabate]

How have you tested it? It is not yet included in the latest release, right?

[HenryHengZJ]

Yep, its not in open source yet, but I've tried to push this in a separate private docker image for enteprise, same problem

[danieldabate]

I tested locally in a rush and probably did something wrong, sorry for the trouble 🙏

[HenryHengZJ]

nono i was just wondering thats all, because I was not able to test it out, so asking here and see if others still faces same problem