Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
    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
    Hi people, question, is there any plan to move to "aws-sdk-java-v2"?
    Jon Hines

    Hi all! I am in the middle of migrating a boot 2.3.8 app to 2.5.2. and as part of that, migrating all of my spring cloud components to the latest (2020.0.3)

    this requires me to upgrade all of my AWS dependencies as well to the new io.awspring.cloud (version 2.3.1). Previously my app was using AWS secrets mgr to fetch secrets as part of the bootstrap prop config.

    I am trying to migrate the app to instead use spring.config.import=aws-secretsmanager:/secret_name_here. but my application just cant seem to resolve aws-secretsmanager as a property source:

    File extension is not known to any PropertySourceLoader. If the location is meant to reference a directory, it must end in '/' or File.separator cannot be found.

    2 replies
    Jon Hines

    to that point above, i tried following this example: https://github.com/awspring/spring-cloud-aws/blob/2.3.x/spring-cloud-aws-samples/spring-cloud-aws-secrets-manager-sample

    but that did not work out of the box for me as well (same error). not sure if anyone else is running in to similar issues


    Hi all! I am using spring-boot-2.3.6. In my app I have an SQS consumer which is subscribed to SNS, It can also receive messages directly from an SQS producer.

    Since it receives messages from both SNS & SQS, I am not sure using both @Payload & @NotificationMessage can serialize the object, or is there any other way to serialize the object.

    Example code for your reference,

    Method - 1
                value = QUEUE_NAME_PROPERTY,
                deletionPolicy = SqsMessageDeletionPolicy.ON_SUCCESS
        public void accountConsumer(
                @Headers Map<String, Object> headers,
                @Payload @NotificationMessage Account payload
        ) {
                // Dispatch message to the handler.
    Method - 2
                value = QUEUE_NAME_PROPERTY,
                deletionPolicy = SqsMessageDeletionPolicy.ON_SUCCESS
        public void accountConsumer(
                @Headers Map<String, Object> headers,
                @Payload Account payload,
                @NotificationMessage Account payload
        ) {
                // Dispatch message to the handler.
    Method - 3
                value = QUEUE_NAME_PROPERTY,
                deletionPolicy = SqsMessageDeletionPolicy.ON_SUCCESS
        public void accountConsumer(String message) {
    // Parse header from message
    // Get body from message and use objectMapper to convert the string message into Java Object
                // Dispatch message to the handler.

    Which one we can use to consume messages from SNS & SQS. Or is there any other standard way to consume messages from both? Any help would be really appreciated.

    Hi All. I'm getting this error and would like to know what is my best option resolving it asap. Are there milestone/nightly builds that I can use? awspring/spring-cloud-aws#108
    For those wondering. I managed to resolve it by just making sure that I only have 1 import in my config. So only 1 of these: spring.config.import=aws-secretsmanager:/secret/mysecret
    @eddumelendez @maciejwalkowiak Can i get your support for the above issue? Raised the same in stackoiverflow https://stackoverflow.com/questions/68933821/how-to-serialize-message-from-spring-cloud-sqs-listener-to-listen-messages-from as well
    Florian Kremser
    Hi! Is there a way, or is this planned, to have on-the-fly updates of parameters using spring-cloud-starter-aws-parameter-store-config and also support versioning of parameters?
    Hi developers. Thanks for this amazing project. One of the issues that I need to be fixed (SNS FIFO attributes) is available in 2.3.2 but the artifact doesn't seem to be in any public repos. Is there another repo I can use to fetch the artifact?
    Patrick Gotthard
    Hi. Are there any plans to update the documentation on spring.io or awspring.io? It seems that both documentations are not up to date and/or complete. I wonder whether awspring 2.3.1 is compatible with Spring Boot 2.5.x because I have no problem so far using this combination.
    1 reply
    @VelDeveloper I'm just spitballing here. Have you tried to have two separate listeners for SNS and SQS and then delegate the business logic to a service? Or does that fail because they are both pointing to the same queue?
    @eduanb Is that possible? A message will not be consumed by both the listeners?
    Is there any reference for using RequestMetricCollector in aws-java-sdk along with spring-cloud-aws?