Using AmazonSQSExtendedClient with AmazonSQSAsync

Question

So the way I understand it is that through using AmazonSQSExtendedClient, the payloads that are over 256kb will get stored into a temp bucket (see the guide here). I'm having a bit of trouble implementing this with AmazonSQSAsync. Because of the way that current system is set up, I'm currently using AmazonSQSAsync, like so:

@Bean
@Primary
AmazonSQSAsync amazonSQSAsync() {
   return AmazonSQSAsyncClientBuilder
            .standard()
            .withEndpointConfiguration(
                    new AwsClientBuilder.EndpointConfiguration(
                            endpoint_url,
                            signin_region))
            .build()
}

Now I want to replace this with the extended client to handle the payloads that are over 256kb. I have something like this so far:

@Bean
@Primary
AmazonSQS amazonSQSWithExtendedClient() {
    final AmazonS3 s3 = AmazonS3ClientBuilder.defaultClient()

    final BucketLifecycleConfiguration.Rule expirationRule =
            new BucketLifecycleConfiguration.Rule()
    expirationRule.withExpirationInDays(14).withStatus("Enabled")
    final BucketLifecycleConfiguration lifecycleConfig =
            new BucketLifecycleConfiguration().withRules(expirationRule)

    s3.setBucketLifecycleConfiguration(temp_bucket, lifecycleConfig)

    // Keep this part
    final ExtendedClientConfiguration extendedClientConfig =
            new ExtendedClientConfiguration()
                    .withLargePayloadSupportEnabled(s3, temp_bucket)

    final AmazonSQS sqsExtended = new AmazonSQSExtendedClient(AmazonSQSClientBuilder
            .standard()
            .withEndpointConfiguration(
                    new AwsClientBuilder.EndpointConfiguration(
                            endpoint_url,
                            signin_region))
            .build(), extendedClientConfig)

    return sqsExtended
}

Is there any way that I can make the extended client work with AmazonSQSAsync or at least have some workaround?

Did you find a solution to this? – Alasdair Ross Jul 10 '20 at 15:58 — Alasdair Ross, Jul 10 '20 at 15:58
@sparkhee93 Did u find a solution for your problem? – Amol Kshirsagar Feb 21 '22 at 02:56 — Amol Kshirsagar, Feb 21 '22 at 02:56

score 1 · Answer 1 · answered Dec 17 '20 at 14:12

1

If you configure your JMS bean, you can solve this kind of problem. Do something like that: https://craftingjava.com/blog/large-sqs-messages-jms-spring-boot/

answered Dec 17 '20 at 14:12

Victor Tripeno

144
1
2
11

Using AmazonSQSExtendedClient with AmazonSQSAsync

1 Answers1