Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Andy Dior VP of Product
    @DwyerBandEmpire_twitter
    I apologize if this has been covered, but I was looking at the Spring Cloud roadmap and noticed this in the 2020.0.0-M1 release: Spring Cloud AWS and Spring Cloud GCP are no longer part of the release train. They will continue to be part of Hoxton as long as it is supported – at least thru June of 2021. (https://spring.io/blog/2020/04/17/spring-cloud-2020-0-0-m1-released). Having read through a few PRs in the project, it looks like Spring Cloud AWS 3.0 will be a major release. Is it just the case that Spring Cloud AWS is no longer part of the Spring Cloud release train?
    Spencer Gibb
    @spencergibb
    @DwyerBandEmpire_twitter yes, it will be released on it's own. It will move to a new github org and have a new maven groupid and new package names (all still undecided yet)
    1 reply
    Juan Carlos Ledesma
    @juancarlos_la_twitter

    Hi guys. I want to implement concurrency (multiple workers) in the SqsListeners. I already have several projects that use that same implementation (as a library). Ideally, keep the implementation with the annotation (@SqsListener) and make the changes in the configuration class

    I read an AWS documentation about that, but it's a bit old, so I don't know if I need to change my implementation, or if there is a way to set the concurrency attributes in the config class.

    Link: https://aws.amazon.com/blogs/developer/using-amazon-sqs-with-spring-boot-and-spring-jms/

    The following is the implementation that I currently have, but I don't know how to set the concurrency attributes:

    Config class

    public class SqsConfig {
    
        @Bean
        public QueueMessagingTemplate queueMessagingTemplate(AmazonSQSAsync amazonSQSAsync) {
            return new QueueMessagingTemplate(amazonSQSAsync);
        }
    
        @Bean
        public AmazonSQS sqsClient() {
            return AmazonSQSClientBuilder.defaultClient();
        }
    }

    Consumer class:

    @Service
    public class Consumer implements ISqsStandardConsumer{
    
        @Override
        @SqsListener("SQS-concurrency-test")
        public void receiveStandardMessage(String message) {
            System.out.println(message);
        }  
    }

    I really appreciate your comments

    2 replies
    Mete Alpaslan Katırcıoğlu
    @mkatircioglu
    spring-cloud-aws is using cloud.aws prefix for configuration properties. Would it be good to rename as spring.cloud.aws in next major release 3.0.0.M1? What do you think? @maciejwalkowiak @eddumelendez
    2 replies
    Pedro Marques
    @pedrorlmarques_twitter

    Hello I don't know if this is a bug or simple spring cloud aws doesn't support this.
    In order to have access to my aws account from AWS CLi, I have to login through a npm app called aws-azure-login and this redirects me to my organization login page and creates and all the information necessary on .aws/config file and .aws/credentials.



    .aws/config

    

[profile landing-zone-iam]
    azure_tenant_id=7e4c72b8-86d8-4e4a-90d8-4f7b7b2513c4
    azure_app_id_uri=https://signin.aws.amazon.com/saml
    azure_default_username=email@email.com
    azure_default_role_arn=
    azure_default_duration_hours=10

    .aws/credentials

    

[landing-zone-iam]
    aws_access_key_id=ASIAVAXUICQBJKDAHRSU
    aws_secret_access_key=z+uN+nklhHLC5RbAQQK8AnMgIV8vAbFIr3iJR5Cg
    aws_session_token=FwoGZXIvYXdzEGsaDGWJ/5ZJZgsV3mRkaiKpAttDP2k7Pkcog04eQvT64bqtTf6cyGW5A+tGBC1vCo6HWnqFQCorPTyaftKk4EDvlenwMk8tYBMgtuGk+I9fMcuFpczuEipEKC4Bmbff9NlwZf7NyqY0xMLG28SQG7p9RZ2OX7mQ0OxT9r7xGCpmt6+nuuykHQRM+vjIAejFu8IgOJvxsYqCB+LuNkgVeT9gEjxAsJKKpD3wyJbiyDCJd+RVDEW+smxQ1fO3PqAX0H9F8MOJfaKpzb8m6bMKgWH59Vg9yb6wW5SnoKcR9m/kt546VO1FYwpnEgWHk/chFivey0iBTxWHz3CMA8ga7e5jtmFNt2/vPLZCoXHyyE194l9i7oPbOGNQn/gpkLF7B43N+s/t/KQe8Uek+xp4tjEtar2+nxFZfZTFLyiclKn5BTIq5dpEXmpQmCkCNgjkpx+kBXNESDnoGu0sTSBleltUemcqZkOT3I9PRC8o
    aws_expiration=2020-08-20T20:02:04.000Z

    [app-dev]
    role_arn=arn:aws:iam::792079637043:role/admin-role
    region=eu-west-1
    source_profile=landing-zone-iam
    external_id=1234
    role_session_name=session_name

    I can use the cli e.g aws s3 ls - -profile app-dev and I have results

If I try to use spring cloud aws I cannot run the application 



    application.properties

    

spring.application.name=demo-aws
    cloud.aws.stack.auto=false
    cloud.aws.credentials.use-default-aws-credentials-chain=true
    cloud.aws.region.use-default-aws-region-chain=true
    cloud.aws.credentials.profile-name=app-dev

    Exception:


    Caused by: com.amazonaws.SdkClientException: Unable to load region information from any provider in the chain
    at com.amazonaws.regions.AwsRegionProviderChain.getRegion(AwsRegionProviderChain.java:59) ~[aws-java-sdk-core-1.11.792.jar:na]

Does Spring Cloud AWS support this kind of authentication ? 


    ctruzzi
    @ctruzzi
    Hello all,
    I am trying to figure out if there are any Spring Bean Scopes that work with Spring Cloud AWS for the entire process of a @SqsListener call. I'd like to autowire certain data through the call cycle but it appears like request doesn't work and I don't believe any of the other scopes by default support that.
    Corneil du Plessis
    @corneil

    I'm trying to deploy a Spring Boot application to AWS Beanstalk. A year ago I wrote an article on how to do it but now those same instructions fail: https://www.baeldung.com/spring-boot-deploy-aws-beanstalk
    I've tried with an without Spring Cloud AWS enabled. In the one profile I exclude:

      org.springframework.cloud.aws.autoconfigure.cache.ElastiCacheAutoConfiguration,\
      org.springframework.cloud.aws.autoconfigure.context.ContextCredentialsAutoConfiguration,\
      org.springframework.cloud.aws.autoconfigure.context.ContextInstanceDataAutoConfiguration,\
      org.springframework.cloud.aws.autoconfigure.context.ContextRegionProviderAutoConfiguration,\
      org.springframework.cloud.aws.autoconfigure.context.ContextResourceLoaderAutoConfiguration,\
      org.springframework.cloud.aws.autoconfigure.context.ContextStackAutoConfiguration,\
      org.springframework.cloud.aws.autoconfigure.jdbc.AmazonRdsDatabaseAutoConfiguration,\
      org.springframework.cloud.aws.autoconfigure.mail.MailSenderAutoConfiguration,\
      org.springframework.cloud.aws.autoconfigure.messaging.MessagingAutoConfiguration,\
      org.springframework.cloud.aws.autoconfigure.metrics.CloudWatchExportAutoConfiguration

    In the other profile I only excluded:

    org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration,\
      org.springframework.boot.autoconfigure.liquibase.LiquibaseAutoConfiguration,\
      org.springframework.cloud.aws.autoconfigure.cache.ElastiCacheAutoConfiguration,\
      org.springframework.cloud.aws.autoconfigure.mail.MailSenderAutoConfiguration,\
      org.springframework.cloud.aws.autoconfigure.messaging.MessagingAutoConfiguration

    So the AmazonRdsDatabaseAutocConfiguration should be active.
    I tried with the RDS database as part of Beanstalk application and as a separate RDS database instance.

    It can't be this difficult.

    Davy De Waele
    @ddewaele
    I know it is possible to retrieve ec2 instance data : https://cloud.spring.io/spring-cloud-aws/reference/html/#using-instance-metadata) when using spring-cloud-aws, but is there also a way to retrieve ECS / Fargate meta data when your spring boot service is running in an ECS / Fargate container ?
    Gayan Weerakutti
    @gayanW

    Adding spring-cloud-starter-aws-secrets-manager-config to 2.3.4.RELEASE - Hoxton.SR8, project throws the following:

    com.amazonaws.util.EC2MetadataUtils : Unable to retrieve the requested metadata (/latest/meta-data/instance-id). 
    Failed to connect to service endpoint: 
    
    com.amazonaws.SdkClientException: Failed to connect to service endpoint: 
            at com.amazonaws.internal.EC2ResourceFetcher.doReadResource(EC2ResourceFetcher.java:100) ~[aws-java-sdk-core-1.11.792.jar:na]
    ....
    
    Caused by: java.net.SocketTimeoutException: connect timed out

    But downgrading the springCloudVersion to Hoxton.SR6 do fix it.

    chiragbhalodia
    @chiragbhalodia
    @edwardbrighton84 Did you get answer on this? I need similar thing
    Maciej Walkowiak
    @maciejwalkowiak
    @pedrorlmarques_twitter sorry for late reply. I believe this is related to spring-cloud/spring-cloud-aws#617 - but this PR cannot be merged in the current form. If you feel like you can pick it up it would be nice
    @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
    @jukkasi
    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
    @spencergibb
    That's an error, 2.2.5 doesn't exist
    @jukkasi :arrow_up:
    it's fixed now
    Jukka Siivonen
    @jukkasi
    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
    @jukkasi
    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
    nikhithagoli
    @nikhithagoli
    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
    @aravindparappil46
    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
    Charly
    @nekperu15739
    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
    @spencergibb
    @nekperu15739 it is no longer part of the release train. The community maintainers will do releases on their own
    Charly
    @nekperu15739
    @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
    @spencergibb
    @nekperu15739 @maciejwalkowiak and @eddumelendez are the maintainers and will need to answer that question.
    Charly
    @nekperu15739
    @eddumelendez habla causa, no tendrán algún roadmap sobre spring-cloud-aws?
    mgargadennec
    @mgargadennec

    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
    @spencergibb
    @mgargadennec no it won't. There will need to be a new release by @maciejwalkowiak and @eddumelendez
    Andrey Chirkov
    @chirkov86

    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
       Failures:
          - 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" }
        mavenCentral()
    }
    
    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
    @spencergibb
    @chirkov86 please read the recent messages above yours about compatibility and waiting on a new release
    1 reply
    Mete Alpaslan Katırcıoğlu
    @mkatircioglu
    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
    @jorgebo10
    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
    PJ
    @pjiocnic
    Can anyone please give me an example for Knative eventing + AWS SQS using spring cloud stream?
    Joel Hess
    @joelhess
    Is it still planned to release 2.3.0 (non-rc) this week?
    Quantum Fusion
    @quantum-fusion
    Are there any java recruiters in here?
    Santiago Ferrer Deheza
    @saferrer
    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!
    Charles
    @cwagnello
    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
    nick
    @srikanthnair:matrix.org
    [m]
    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?
    VelDeveloper
    @VelDeveloper

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

    error
    com.amazonaws.SdkClientException: The requested metadata is not found at http://169.254.169.254/latest/meta-data/public-hostname
        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
    @jorgebo10

    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()
                                .get(MessageSystemAttributeName.MessageGroupId.name())))
                        .values().stream().map(MessageGroup::new).collect(Collectors.toList());
            }

    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
    @kschlesselmann
    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
    spring:
      config:
        import: "aws-parameterstore:"
    1 reply
    Charly
    @nekperu15739
    Hi people, question, im trying to use parameter store, however always pick up last version, is there a way to fetch specific version?
    Charly
    @nekperu15739
    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
    Charly
    @nekperu15739
    any ideas properties = {
    "spring.config.import=aws-parameterstore:",
    "aws.paramstore.prefix=/myProject",
    "aws.paramstore.name=myService",
    "spring.profiles.active=myProfile",
    "cloud.aws.region.use-default-aws-region-chain=true",
    "cloud.aws.stack.auto=false",
    "logging.level.com.amazonaws.util.EC2MetadataUtils=error",
    "logging.level.io.awspring.cloud.paramstore.AwsParamStorePropertySource=debug"
    }