You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AmazonSNSExtendedClient constructor calls one of the S3BackedPayloadStore constructor which always set the sseAwsKeyManagementParams to null. So there is no point of setting this param. one of the solutions could be to call the second parameterized constructor of S3BackedPayloadStore which accepts the sseAwsKeyManagementParams.
The text was updated successfully, but these errors were encountered:
The withServerSideEncryption method in ExtendedClientConfiguration is not functioning correctly because the appropriate constructor in AmazonSNSExtendedClient.java is not being invoked. This call should be altered from:
S3Dao s3Dao = new S3Dao(this.snsExtendedClientConfiguration.getS3Client());
to:
S3Dao s3Dao = new S3Dao(clientConfiguration.getS3Client(),
clientConfiguration.getServerSideEncryptionStrategy(),
clientConfiguration.getObjectCannedACL());
as it is implemented in AmazonSQSExtendedClient.
Created a fix for this here #20
Till it is merged and this workaround can be used create a custom AmazonSNSExtendedClient say AmazonSNSExtendedClientCustom with the following constructor
public AmazonSNSExtendedClientCustom(SnsClient snsClient, SNSExtendedClientConfiguration snsExtendedClientConfiguration,
PayloadStore payloadStore) {
}
and create the object as following
final S3Dao s3Dao = new S3Dao(extendedClientConfig.getS3Client(),
extendedClientConfig.getServerSideEncryptionStrategy(),
extendedClientConfig.getObjectCannedACL());
final PayloadStore payloadStore = new S3BackedPayloadStore(s3Dao, extendedClientConfig.getS3BucketName());
client = new AmazonSNSExtendedClientCustom(SnsClient.builder()
.region(Region.EU_WEST_1)
.build(),
extendedClientConfig,
payloadStore);
AmazonSNSExtendedClient constructor calls one of the S3BackedPayloadStore constructor which always set the sseAwsKeyManagementParams to null. So there is no point of setting this param. one of the solutions could be to call the second parameterized constructor of S3BackedPayloadStore which accepts the sseAwsKeyManagementParams.
The text was updated successfully, but these errors were encountered: