Briefly, this error occurs when there is a mismatch between the signer set in the Elasticsearch configuration and the actual signer used by AWS. This could be due to an outdated signer or incorrect configuration. To resolve this issue, you can either update the signer to the latest version or correct the signer in the Elasticsearch configuration. Make sure to use the correct signer that matches with your AWS service. Also, ensure that the AWS credentials are correctly set in the Elasticsearch configuration.
This guide will help you check for common problems that cause the log ” wrong signer set for [cloud.aws.ec2.signer] or [cloud.aws.signer]: [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: request.
Log Context
Log “wrong signer set for [cloud.aws.ec2.signer] or [cloud.aws.signer]: [{}]” classname is AwsEc2Service.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
if (awsSigner != null) {
logger.debug("using AWS API signer [{}]"; awsSigner);
try {
AwsSigner.configureSigner(awsSigner; clientConfiguration);
} catch (IllegalArgumentException e) {
logger.warn("wrong signer set for [cloud.aws.ec2.signer] or [cloud.aws.signer]: [{}]"; awsSigner);
}
}
AWSCredentialsProvider credentials;
