EC2 API request failed; retry again. Reason was: – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

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 ” EC2 API request failed; retry again. Reason was: ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cloud-aws, discovery, discovery-ec2, plugins and request.

Log Context

Log “EC2 API request failed; retry again. Reason was:” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         final Random rand = Randomness.get();
        final RetryPolicy retryPolicy = new RetryPolicy(
            (originalRequest; exception; retriesAttempted) -> {
               // with 10 retries the max delay time is 320s/320000ms (10 * 2^5 * 1 * 1000)
               logger.warn("EC2 API request failed; retry again. Reason was:"; exception);
               return 1000L * (long) (10d * Math.pow(2; retriesAttempted / 2.0d) * (1.0d + rand.nextDouble()));


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content