Published by maciejwalkowiak almost 3 years ago
This version solves bumps a spring-messaging
dependency to 5.3.13. Previous Spring Cloud AWS versions relied on spring-messaging
that suffered from a security vulnerability (https://github.com/awspring/spring-cloud-aws/issues/206). If you relied on Spring Cloud AWS to determine spring-messaging
version, please update to Spring Cloud AWS 2.3.3.
Big thanks to contributors and @MatejNedic & @eddumelendez for reviews and support!
π https://docs.awspring.io/spring-cloud-aws/docs/2.3.3/reference/html/index.html
Published by maciejwalkowiak about 3 years ago
Thanks to @neiljbrown @shawnjohnson @SergeiKhmelevSPA @joaomlneto for improving the reference documentation!
π http://docs.awspring.io/spring-cloud-aws/docs/2.3.2/reference/html/index.html
Published by maciejwalkowiak over 3 years ago
Bugfix release:
Published by eddumelendez over 3 years ago
On the top of changes in 2.3 RC2, in Spring Cloud AWS 2.3 we added:
FIFO queue support introduced in Spring Cloud AWS 2.3 RC2 is not compatible with the AmazonSQSBufferedAsyncClient
used by default in SQS integration. When FIFO queues are used, we recommend creating custom SQS client bean, otherwise a warning message will be logged. Related issues:
Published by maciejwalkowiak over 3 years ago
Spring Cloud AWS 2.3 is compatible with Spring Boot 2.4 and Spring Cloud 2020.0. It's a first release in the new community driven organisation awspring
- which means that module group ids and package names have changed from org.springframework.cloud.aws
to io.awspring.cloud
.
Find most important changes organised by Spring Cloud AWS module:
ClientConfiguration
ClientConfiguration
used when initializing AWS clients, can be now defined by creating a bean with name "com.amazonaws.ClientConfiguration.BEAN_NAME".
Itβs also possible to provide ClientConfiguration for particular integration by defining a bean of type ClientConfiguration
and a name specific to the integration, for example for SQS client, the bean name must be sqsClientConfiguration
.
In order to speed up startup times applications that do not use EC2 instance data, ContextInstanceDataAutoConfiguration
is disabled by default. To enable it, set cloud.aws.instance.data.enabled
to true
.
AWS SDK has been upgraded to 1.11.951
For each integrated AWS service you can configure Spring Cloud AWS to use a custom endpoint using configuration properties. For example:
cloud.aws.s3.endpoint=http://localhost:4566
cloud.aws.sqs.endpoint=http://localhost:4566
cloud.aws.rds.endpoint=http://localhost:4566
Using custom endpoint can be especially useful when using Localstack in integration tests.
XML Configuration is now deprecated and is going to be removed in the major version upgrade.
In addition to global region configuration, each integration can have a different region set statically. Read More
@EnableXXX
annotations@EnableXXX
annotations have been deprecated. We recommend using Spring Boot auto-configurations.
Each service can be now enabled/disabled with enabled
property.
DefaultAWSCredentialsProvider
and DefaultAWSRegionProviderChain
are used now by default. cloud.aws.credentials.use-default-aws-credentials-chain
and cloud.aws.region.use-default-aws-region-chain
properties were dropped.
To simplify project setup for applications that do not use CloudFormation support, CloudFormation related auto-configurations have been disabled by default. To enable CloudFormation support in Spring Cloud AWS you must add following dependency that will trigger ContextStackAutoConfiguration
:
<dependency>
<groupId>com.amazonaws</groupId>
<artifactId>aws-java-sdk-cloudformation</artifactId>
</dependency>
SES support has been extracted from context
module to separate spring-cloud-aws-ses
module. There is also a dedicated starter spring-cloud-aws-ses-starter
.
Spring Cloud AWS comes with basic support for AWS Cognito, simplifying configuring OAuth2. Read More
spring.config.import
introduced in Spring Cloud 2020.0 Read More
javax.validation:validation-api
spring.config.import
introduced in Spring Cloud 2020.0 Read More
javax.validation:validation-api
SimpleMessageListenerContainer#isQueueRunning
method is now visible to extending classes. #350
SqsListener
argument #295
queueStopTimeout
can be configurable via SimpleMessageListenerContainerFactory #504 #507
SqsMessageHeaders
in SqsListener
. Added ApproximateFirstReceiveTimestamp
, ApproximateReceiveCount
and SentTimestamp
headers #296
ObjectMapper
instance, use one present in the application context #533, #522, #540SimpleStorageResource
sets content-type
property on the S3 object metadata #262
@NotificationMessageMapping
handles properly special characters #645
Make RDS instance name configuration more flexible. For example, for instance name test
, instead of setting cloud.aws.rds.test.username=user
property you must now set:
cloud.aws.rds.instances[0].db-instance-identifier=test
cloud.aws.rds.instances[0].username=user
Removed spring-cloud-aws-actuator
module. Instead we recommend using the dependency to micrometer-registry-cloudwatch
directly. #571
Published by eddumelendez almost 4 years ago