Hi

Recently our internal git failed what effected our production as the Config Server was not able to checkout configs for all services.
To resolve it we decided to use S3 bucket as a fallback, however, after I set up the bucket and upload our config files from Git I noticed that it doesn't work... with a bit of reading through the documentation I found that S3 bucket require to have file names in a specific format: <service_name>-<profile>.yml
However, in our Git we have a single file with just the name of the service and multiple profiles inside what perfectly supported by YAML and the config service is able to extract a specific profile from such file.

Additionally, our service name and profile names include dashes eg:
Service name: notification-service.yml
Profile: qa54-nsapce25-docker which refer to:
qa65 - QA environment
nsapce25 - specific nsapce within EKS / Kubernetes
docker - means service run from docker, and not from local code

so having a file with a name like "notification-service-qa54-nsapce25-docker.yml" doesn't work in S3 either