MatejNedic

Hey @dantonyuk , I think we should apply different approach to this problem. We should use Secrets Manager Secret staging labels that are tied to Secret. Check [versions](https://docs.aws.amazon.com/secretsmanager/latest/userguide/getting-started.html#term_version). After that...

Hi @dantonyuk , 1. You can add any named [staging label](https://docs.aws.amazon.com/secretsmanager/latest/apireference/API_UpdateSecretVersionStage.html) you want. Problem is when it is AWSCURRENT and AWS moves it to AWSPREVIOUS it will delete your label....

Hey @hpoettker, I already have PR mostly done but since you spent time on this in past I think you should finish it. Just something to note I would recommend...

Hey, sorry for the delay I was on vacation and some other things took priority. I am currently in process of polishing tests and will have PR soon.

Will commit sample in following days

Tried it against real AWS integration works as expected.

Hey @v1nc3n4 , Thanks for opening issue! We are going to rewrite sqs integration in 3.x. so we are going to look at supportimg reactive streams then.

Hey @amrutprabhu tnx on reporting, Indeed this is a bug since CredentialsProvider is never taken into consideration when `AWSSecretsManager` client is being [created](https://github.com/awspring/spring-cloud-aws/blob/1579a1387d3161413b8787e03d212a5075604f4f/spring-cloud-starter-aws-secrets-manager-config/src/main/java/io/awspring/cloud/autoconfigure/secretsmanager/AwsSecretsManagerBootstrapConfiguration.java#L67). This explains why `DefaultAWSCredentialsProviderChain` is used. ParameterStore...

Yes this is fixed in 3.0. Was thinking about adding same feature to 2.4.x or just modyfing docs since 3.0 is active now.

Hey @amrutprabhu, Tnx for helping out! If you check the 2.4.x branch, beans are being registered [here](https://github.com/awspring/spring-cloud-aws/blob/1579a1387d3161413b8787e03d212a5075604f4f/spring-cloud-starter-aws-secrets-manager-config/src/main/java/io/awspring/cloud/autoconfigure/secretsmanager/AwsSecretsManagerConfigDataLocationResolver.java#L77). As you can see `CredentialsProperties` are not not registered only `AwsSecretsManagerProperties` and `AWSSecretsManager`...