Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
    Maciej Walkowiak
    @gayanW - this is just a log from the AWS SDK that can and should be disabled. Take a look please at this video: https://youtu.be/Ts2a-YdN6vI?t=393
    @ddewaele I haven't tested it with Fargate/ECS but there was no effort (yet) to make Spring Cloud AWS work in any special way on Fargate
    Jukka Siivonen
    Should org.springframework.cloud:spring-cloud-starter-aws-secrets-manager-config:2.2.5.RELEASE exist in some Maven repository? Can't find it
    Spencer Gibb
    That's an error, 2.2.5 doesn't exist
    @jukkasi :arrow_up:
    it's fixed now
    Jukka Siivonen
    What is proper way to disable loading of all Spring Cloud (AWS) beans and stuff in my local development environment? I'm using Gradle dependencies spring-cloud-starter, spring-cloud-starter-aws-parameter-store-config,spring-cloud-starter-aws-secrets-manager-config. (versions 2.2.4) Now in application startup I get not so very nice stacktrace
    com.amazonaws.SdkClientException: Failed to connect to service endpoint: at com.amazonaws.internal.EC2ResourceFetcher.doReadResource(EC2ResourceFetcher.java:100) at com.amazonaws.internal.InstanceMetadataServiceResourceFetcher.getToken(InstanceMetadataServiceResourceFetcher.java:91) at com.amazonaws.internal.InstanceMetadataServiceResourceFetcher.readResource(InstanceMetadataServiceResourceFetcher.java:69) at com.amazonaws.internal.EC2ResourceFetcher.readResource(EC2ResourceFetcher.java:66) at com.amazonaws.util.EC2MetadataUtils.getItems(EC2MetadataUtils.java:402) at com.amazonaws.util.EC2MetadataUtils.getData(EC2MetadataUtils.java:371) at org.springframework.cloud.aws.context.support.env.AwsCloudEnvironmentCheckUtils.isRunningOnCloudEnvironment(AwsCloudEnvironmentCheckUtils.java:38) at org.springframework.cloud.aws.context.annotation.OnAwsCloudEnvironmentCondition.matches(OnAwsCloudEnvironmentCondition.java:38) at org.springframework.context.annotation.ConditionEvaluator.shouldSkip(ConditionEvaluator.java:108)
    Application starts though
    3 replies
    Jukka Siivonen
    Actually I don't need spring-cloud-starter at all. For config autostarters they seem to depend on aws-autoconfigure in version 2.2.4 but their repository have this dependency changed to aws-core instead which would probably lead to result I'm expecting, I believe aws-autoconfigure is the one causing this unwanted initialization
    Hey people, Any one can share me a sample code how to implement two sqsListeners for a single sqs queue like the following:

    class A{
    @SqsListener(value = "some-queue", deletionPolicy = ON_SUCCESS)
    public void onMessageReceived1(String payload, @Header(TYPE) String messageType) {}

    class B {
    @SqsListener(value = "some-queue", deletionPolicy = ON_SUCCESS)
    public void onMessageReceived2(@Payload SomeMessagePayload message, @Header(TYPE) String messageType) {}

    Aravind Parappil
    Question on spring-cloud-aws-parameter-store : If I change a value of a parameter stored in AWS Parameter Store, is there a way for the Spring Boot application to know of the updated value without having to restart? i.e., can parameters be dynamically updated?
    1 reply
    Hi people, question, i do not see support for aws on new spring-cloud 2020-0-0-rc1-aka-ilford, anyone had info about it?
    Spencer Gibb
    @nekperu15739 it is no longer part of the release train. The community maintainers will do releases on their own
    @spencergibb do you have a roadmap?
    im a bit worry about it, since, not able to update to 2.4.1 since has compatibility with spring-cloud-aws
    Spencer Gibb
    @nekperu15739 @maciejwalkowiak and @eddumelendez are the maintainers and will need to answer that question.
    @eddumelendez habla causa, no tendrán algún roadmap sobre spring-cloud-aws?

    Hi people, will version 2.2.6 be compatible with Spring Boot 2.4.x ?

    I'm currently blocked for using the Parameter Store with 2.2.5 because Spring-Boot removed org.springframework.boot.context.properties.ConfigurationBeanFactoryMetadata.

    Spencer Gibb
    @mgargadennec no it won't. There will need to be a new release by @maciejwalkowiak and @eddumelendez
    Andrey Chirkov

    Hello there! I was redirected to this channel from spring-boot. I am trying to upgrade my application from Spring Boot 2.3.x to 2.4.x and Spring Cloud from Hoxton to 2020.0.x accordingly. Using the compatibility matrix at https://spring.io/projects/spring-cloud I picked up new versions. I also use io.spring.dependency-management plugin in Gradle to resolve dependencies. The migration fails because of one of my dependencies, namely org.springframework.cloud:spring-cloud-starter-aws-parameter-store-config which can not be resolved correctly together with the new version of Spring Cloud. With the old version, it is resolved correctly as 2.2.4.RELEASE. With the new one, it looks like it can't be resolved the version at all, and gradle -q dependencyInsight --dependency spring-cloud-starter-aws-parameter-store-config --configuration compileClasspath shows the following output:

    org.springframework.cloud:spring-cloud-starter-aws-parameter-store-config: FAILED
          - Could not find org.springframework.cloud:spring-cloud-starter-aws-parameter-store-config:.
    org.springframework.cloud:spring-cloud-starter-aws-parameter-store-config FAILED
    \--- compileClasspath

    Here is my build.gradle snippet to reproduce the problem:

    plugins {
    //    id 'org.springframework.boot' version '2.3.4.RELEASE'
        id 'org.springframework.boot' version '2.4.1'
        id 'io.spring.dependency-management' version '1.0.10.RELEASE'
        id 'java'
    repositories {
        maven { url "https://repo.spring.io/milestone" }
    dependencies {
        implementation 'org.springframework.boot:spring-boot-starter'
        implementation "org.springframework.cloud:spring-cloud-starter-aws-parameter-store-config"
    dependencyManagement {
        imports {
    //        mavenBom "org.springframework.boot:spring-boot-starter-parent:2.3.4.RELEASE"
    //        mavenBom "org.springframework.cloud:spring-cloud-dependencies:Hoxton.SR8"
            mavenBom "org.springframework.boot:spring-boot-starter-parent:2.4.1"
            mavenBom "org.springframework.cloud:spring-cloud-dependencies:2020.0.0-RC1"

    If I set the version of the aforementioned spring-cloud-starter-aws-parameter-store-config explicitly the problem is gone. However, I would like to avoid this and stick to automated dependencies resolution provided by the io.spring.dependency-management plugin. What can I do to fix that? Maybe spring-cloud-starter-aws-parameter-store-config is deprecated and I need to switch to another dependency? Thanks!

    6 replies
    Spencer Gibb
    @chirkov86 please read the recent messages above yours about compatibility and waiting on a new release
    1 reply
    Mete Alpaslan Katırcıoğlu
    Hi @maciejwalkowiak and @eddumelendez. I have just noticed that spring-cloud-aws repository has been moved another repository. Could you please give some information about how we handle open issues for 2.x release and 3.x release? It would be event better to share some roadmap for project if possible.
    1 reply
    Jorge Bo
    Hi, is it ok to read messages from queue in a reactive project using @SqsListener ? I noticed that exceptions don't cause messages to be moved to dead letter
    Can anyone please give me an example for Knative eventing + AWS SQS using spring cloud stream?
    Joel Hess
    Is it still planned to release 2.3.0 (non-rc) this week?
    Quantum Fusion
    Are there any java recruiters in here?
    Santiago Ferrer Deheza
    Hi All! Has anyone encounter a problem when importing org.springframework.cloud:spring-cloud-starter-aws-parameter-store-config? As soon as I import it I get the error message Process finished with exit code 0 Right after starting my app, no logs, nothing (not even on debug mode). Tried it with both 2.3.x with HOXTON and 2.4.x with 2020.0.1. Thanks for the help!
    Is there support for AWS Basic Session Credentials? I need to pass in a session token in addition to the Access key and Secret key to access AWS resources via the Spring Cloud Config service I set up. Here's the docs I have been referring to: https://cloud.spring.io/spring-cloud-aws/2.2.x/reference/html/appendix.html
    If not how would I override the existing code to configure the Credentials Provider with the Basic Session Credentials https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/BasicSessionCredentials.html
    3 replies
    Hi, I would like to know how to implement SQS when the message is larger than 256 KB, explained in the following document section https://docs.spring.io/spring-cloud/docs/Hoxton.SR9/reference/htmlsingle/#sqs-support I was not able find any documentation or example implementation anywhere in the web, Kindly direct me where can I find the documentation or sample of how to implement in the spring-boot environment?

    Hi, I often getting below error message from aws-ec2 library.. could anyone please let me know how to disable it.

    com.amazonaws.SdkClientException: The requested metadata is not found at
        at com.amazonaws.internal.EC2CredentialsUtils.readResource(EC2CredentialsUtils.java:122)
        at com.amazonaws.internal.EC2CredentialsUtils.readResource(EC2CredentialsUtils.java:82)
        at com.amazonaws.util.EC2MetadataUtils.getItems(EC2MetadataUtils.java:400)
        at com.amazonaws.util.EC2MetadataUtils.getData(EC2MetadataUtils.java:369)
        at com.amazonaws.util.EC2MetadataUtils.getData(EC2MetadataUtils.java:365)
        at org.springframework.cloud.aws.core.env.ec2.AmazonEc2InstanceDataPropertySource.getProperty(AmazonEc2InstanceDataPropertySource.java:105)
        at org.springframework.boot.actuate.env.EnvironmentEndpoint.describeValueOf(EnvironmentEndpoint.java:144)
        at org.springframework.boot.actuate.env.EnvironmentEndpoint.lambda$describeSource$4(EnvironmentEndpoint.java:137)
        at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)

    This is the version of spring cloud AWS we are using

    +- org.springframework.cloud:spring-cloud-starter-aws-messaging:jar:2.2.1.RELEASE:compile
    [INFO] |  |  +- org.springframework.cloud:spring-cloud-starter-aws:jar:2.2.1.RELEASE:compile
    [INFO] |  |  |  +- org.springframework.cloud:spring-cloud-aws-context:jar:2.2.1.RELEASE:compile
    [INFO] |  |  |  |  \- org.springframework.cloud:spring-cloud-aws-core:jar:2.2.1.RELEASE:compile
    [INFO] |  |  |  |     +- com.amazonaws:aws-java-sdk-s3:jar:1.11.415:compile
    [INFO] |  |  |  |     +- com.amazonaws:aws-java-sdk-ec2:jar:1.11.415:compile
    [INFO] |  |  |  |     \- com.amazonaws:aws-java-sdk-cloudformation:jar:1.11.415:compile
    [INFO] |  |  |  \- org.springframework.cloud:spring-cloud-aws-autoconfigure:jar:2.2.1.RELEASE:compile

    I think recently we upgraded our spring boot version after that only we are getting this issue. This is polluting our logs and we doesn't know how to disable it. Any help would be really appreciated.

    5 replies
    Jorge Bo

    Hi, while migrating to Spring Cloud AWS 2.3 RC2 in order to test sqs integration, i noticed that the following code is complaing that MessageGroupId is not found.

    private List<MessageGroup> groupByMessageGroupId(final ReceiveMessageResult receiveMessageResult) {
                return receiveMessageResult.getMessages().stream()
                        .collect(Collectors.groupingBy(message -> message.getMessageAttributes()

    My code is using QueueMessageTemplate.convertAndSend with headers,

    headers.put(SQS_GROUP_ID_HEADER, "my-group");
      headers.put(SQS_DEDUPLICATION_ID_HEADER, "ddid");

    Are those headers still valid?

    1 reply
    Knut Schleßelmann
    java.lang.IllegalStateException: Could not register object [com.amazonaws.services.simplesystemsmanagement.AWSSimpleSystemsManagementClient@785a4557] under bean name 'configDataAWSSimpleSystemsManagement': there is already object [com.amazonaws.services.simplesystemsmanagement.AWSSimpleSystemsManagementClient@785a4557] bound
        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.registerSingleton(DefaultSingletonBeanRegistry.java:124)
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.registerSingleton(DefaultListableBeanFactory.java:1138)
        at io.awspring.cloud.autoconfigure.paramstore.AwsParamStoreConfigDataLocationResolver.lambda$registerAndPromoteBean$1(AwsParamStoreConfigDataLocationResolver.java:106)
        at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:176)
        at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:169)
        at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:143)
        at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:131)
        at org.springframework.boot.DefaultBootstrapContext.close(DefaultBootstrapContext.java:133)
        at org.springframework.boot.SpringApplication.prepareContext(SpringApplication.java:392)
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:325)
        at org.springframework.boot.builder.SpringApplicationBuilder.run(SpringApplicationBuilder.java:144)
        at org.springframework.cloud.stream.binder.DefaultBinderFactory.getBinderInstance(DefaultBinderFactory.java:338)
    Anyone ever seen this? We try to migrate to Spring Cloud 2020, SB 2.4 and Spring Cloud AWS 2.3. Now we dropped the dependency on the bootstrap context and tried to include the paramstore with
        import: "aws-parameterstore:"
    1 reply
    Hi people, question, im trying to use parameter store, however always pick up last version, is there a way to fetch specific version?
    Hi @maciejwalkowiak , im trying to follow your sample, https://github.com/awspring/spring-cloud-aws/blob/v2.3.0/spring-cloud-aws-samples/spring-cloud-aws-parameter-store-sample/src/main/resources/application.properties to do an integration test, however, in my case no matter how config spring.config.import AwsParamStoreProperties never pick up the values
    any ideas properties = {
    Eddú Meléndez Gonzales
    @nekperu15739 are you using spring cloud bootstrap dependency? those properties are declared in bootstrap.properties or application.properties? TBH, I prefer to declare the whole path in spring.config.import instead of let the libraries built it by itself, we have seen that it is very confusing for people when using aws.paramstore.* properties
    Habla causa(@eddumelendez ) yes, im using it, and not using files in deep, because, its just a sample of use, you could check the implementation here: https://github.com/Ryanair/guides-awspring-localstack-ssm/tree/feature/complete
    1 reply
    Alex Lavigne
    Hi everyone! I am a rookie of spring-cloud-aws .I am more familiar with the framework of dubbo.
    I have a question: What is the pros and cons of spring-cloud-aws vs spring-cloud-alibaba ?
    Alex Lavigne
    Which framework will be the future of spring-cloud and become the successor of spring-cloud-netflix ?
    Jeff Maxwell
    Is there a reason why AwsParamStoreBootstrapConfiguration and AwsSecretsManagerBootstrapConfiguration don’t support the use of an AWSCredentialsProvider?
    Note: for those services to get a handle on the AWSCredentialsProvider ContextCredentialsAutoConfiguration would have to be assigned as BootstrapConfigurations.
    Shawn White

    I'm new to Spring Cloud and AWS and having some issues resolving what I think is a conflict between AWS versions required by two different dependencies.

    I'm looking to use Spring Cloud for AWS 2.3.1 and it wants the AWS Java SDK version 1.11.951.
    In our project we have another dependency that is using AWS and it wants version 1.11.942.

    Using Gradle's dependency insights, it determines that the former version is what going to be used.

    However, we are getting the following exception when starting the service and its trying to create the simpleMessageListenerCotainer.

    Caused by: java.lang.NoSuchFieldError: CLIENT_ENDPOINT at com.amazonaws.services.sqs.AmazonSQSClient.executeGetQueueUrl(AmazonSQSClient.java:1216) ~[aws-java-sdk-sqs-1.11.951.jar:na] at com.amazonaws.services.sqs.AmazonSQSClient.getQueueUrl(AmazonSQSClient.java:1198) ~[aws-java-sdk-sqs-1.11.951.jar:na] at com.amazonaws.services.sqs.buffered.AmazonSQSBufferedAsyncClient.getQueueUrl(AmazonSQSBufferedAsyncClient.java:261) ~[aws-java-sdk-sqs-1.11.951.jar:na] at io.awspring.cloud.messaging.support.destination.DynamicQueueUrlDestinationResolver.resolveDestination(DynamicQueueUrlDestinationResolver.java:90) ~[spring-cloud-aws-messaging-2.3.1.jar:2.3.1] at io.awspring.cloud.messaging.support.destination.DynamicQueueUrlDestinationResolver.resolveDestination(DynamicQueueUrlDestinationResolver.java:38) ~[spring-cloud-aws-messaging-2.3.1.jar:2.3.1] at org.springframework.messaging.core.CachingDestinationResolverProxy.resolveDestination(CachingDestinationResolverProxy.java:92) ~[spring-messaging-5.3.6.jar:5.3.6] at io.awspring.cloud.messaging.listener.AbstractMessageListenerContainer.queueAttributes(AbstractMessageListenerContainer.java:328) ~[spring-cloud-aws-messaging-2.3.1.jar:2.3.1] at io.awspring.cloud.messaging.listener.AbstractMessageListenerContainer.initialize(AbstractMessageListenerContainer.java:302) ~[spring-cloud-aws-messaging-2.3.1.jar:2.3.1] at io.awspring.cloud.messaging.listener.SimpleMessageListenerContainer.initialize(SimpleMessageListenerContainer.java:116) ~[spring-cloud-aws-messaging-2.3.1.jar:2.3.1] at io.awspring.cloud.messaging.listener.AbstractMessageListenerContainer.afterPropertiesSet(AbstractMessageListenerContainer.java:269) ~[spring-cloud-aws-messaging-2.3.1.jar:2.3.1] at io.awspring.cloud.messaging.listener.SimpleMessageListenerContainer.afterPropertiesSet(SimpleMessageListenerContainer.java:50) ~[spring-cloud-aws-messaging-2.3.1.jar:2.3.1] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1845) ~[spring-beans-5.3.6.jar:5.3.6] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1782) ~[spring-beans-5.3.6.jar:5.3.6] ... 17 common frames omitted

    Is this due to the mismatched library dependencies on AWS even though gradle seems to resolve them to the version Spring Cloud is expecting?

    Or any other clues as to what might be going on here?

    Mikita Karaliou


    Just want to ask a couple of questions:

    • Are you interested in STS support? I see that we can use the default auth chain and it will work w/ STS, but there is no way to configure it in a "spring-way".
    • Do you have any milestones about Spring boot 2.4.x & 2.5.x? We are planning to migrate to the new Boot, but it looks incompatible for now.


    Tucker Buchy
    hey guys i'm hoping to use spring-cloud-aws-jdbc to connect to an RDS cluster with a read and write replica. But I'd also like my local environment to continue to function with a local postgres image. Is there a straightforward way to support this using this library? I'm not following how this can function together with DataSource
    Eric Turley

    I've just done an upgrade :

    • Spring Boot: 2.3.1.RELEASE to 2.4.6sd
    • Spring Cloud AWS Param store
      • from org.springframework.cloud : spring-cloud-starter-aws-parameter-store-config : 2.3.1.RELEASE <--- starter
      • to ...io.awspring.cloud : spring-cloud-aws-parameter-store-config : 2.3.0 <--- non-starter
    • Replacing the spring-cloud-dependencies bom with the io.awspring.cloud : spring-cloud-aws-dependencies bom

    Now, I'm getting:

    Error creating bean with name 'webSecurityConfig': Unsatisfied dependency expressed through method 'setContentNegotationStrategy'
    Caused by: java.lang.IllegalStateException: Client id must not be empty.
        at org.springframework.boot.autoconfigure.security.oauth2.client.OAuth2ClientProperties.validateRegistration(OAuth2ClientProperties.java:68)

    The Client id is fetched from a service, and it works prior to the changes.
    Is there a migration change I'm missing, maybe?

    1 reply