To repro, setup an AWS logs integration with elastic agent running in EC2 and the S3+SQS input. You will likely see SQS errors like this:
sqs ReceiveMessage failed: operation error SQS: ReceiveMessage, https response error StatusCode: 403, RequestID: cb57783a-505f-5099-9160-23b8eea8ddbb, api error SignatureDoesNotMatch: Credential should be scoped to a valid region.
We believe this is due to changes in the SDK brought in with #31224. It looks like the SQS endpoint SigningRegion is not being set in the SDK configuration.
The reason for this appears to be that we are using a custom endpoint resolver when building the S3/SQS configuration. At this point it's unclear to me why we aren't just using the default resolver here. I can't see what benefits we get by maintaining the custom version.
To repro, setup an AWS logs integration with elastic agent running in EC2 and the S3+SQS input. You will likely see SQS errors like this:
We believe this is due to changes in the SDK brought in with #31224. It looks like the SQS endpoint
SigningRegionis not being set in the SDK configuration.The reason for this appears to be that we are using a custom endpoint resolver when building the S3/SQS configuration. At this point it's unclear to me why we aren't just using the default resolver here. I can't see what benefits we get by maintaining the custom version.