Cloud-AWS | A collection of projects supporting AWS Integration | AWS library

If you are trying to access an s3 bucket with localstack via an aws api; you would need to withPathStyleEnabled flag turned on.

for eg:

Adding the lib aws-java-sdk-sts to the project solved the problem

You have declared 'org.springframework.boot' as the parent module of both modules. So if some jars and artifacts like 'com.amazonaws' do not exist in 'org.springframework.boot', they won't be resolved in your project. These dependencies are not announced in 'Spring' module in your project and whatever you have declared in it, can be found in 'org.springframework.boot', then resolved. If you do not declare a 'version' tag in your pom, I guess the version of the parent (here 2.6.1) will be considered for your module version.

Based on the error message, remove the JavaMailSender constructor argument in the NotificationService constructor (assuming you are not using that in the NotificationService).

In case you wanted to use the JavaMailSender in the NotificationService, you would need to create a Bean of type JavaMailSender which can be injected in the NotificationService. For AWS-SES, you can do so by defining the following bean in your configuration.

You are using a third party API. To use invoke Amazon Simple Queue Service (SQS) from a Java project, use the Official AWS SDK for Java V2. If you are not aware how to use this SDK, see this DEV Guide:

Developer guide - AWS SDK for Java 2.x

For AWS SQS specific information, see:

Working with Amazon Simple Queue Service

This has links to AWS Github where you will find POM dependencies, code, etc.

Spring Cloud AWS is now a community project, see: https://awspring.io/ The current release train of Spring Cloud (2020.x), where you can find Sleuth 3.x does not include/support it.

You should use io.awspring.cloud:spring-cloud-aws-messaging:2.3.x instead of org.springframework.cloud:spring-cloud-aws-messaging:2.2.x with the current release train of Spring Cloud (2020.x).

Because of these, Sleuth does not instrument Spring AWS Messaging directly but if you can use SQS in a way that integrates with Spring Integration/Messaging/Stream/something that is already instrumented, this could work; i.e.: I would try using QueueMessageChannel and the annotations, I don't think QueueMessagingTemplate will work.

Another thing you can do is manually instrument it and propagate tracing information in the headers, see: TraceSpringMessagingAutoConfiguration

See Spring Integration testing support documentation: https://docs.spring.io/spring-integration/docs/current/reference/html/testing.html#testing. The framework provides for us a MockIntegrationContext via @SpringIntegrationTest marker on the Spring JUnit test class. The MockIntegration factory lets us to create respective mocks and stub their handling logic. Then you can substitute endpoint beans with your mocks and so.

Seems it has been removed with the suggestion that org.springframework.boot.context.properties.ConfigurationPropertiesBean be used instead, as of June 23, 2020.

You can try to look into PostProcessors that executed on the very first stages of Spring Context initialization. For example, EnvironmentPostProcessor. It executes quite early and probably can help you to manage some properties/modify files before they will be loaded to context.

Note: if you want to use this code in some library that will be a part of another project, you should add such PostProcessor to spring.factories file. In other case it won't be added to configuration stage of another Spring.