Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.
To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).
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;
Find & fix Elasticsearch problems
