No ec2 metadata returned from – How to solve related issues

Average Read Time

2 Mins

No ec2 metadata returned from – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” No ec2 metadata returned from ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cloud-aws, discovery-ec2, metadata, node and plugins.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “no ec2 metadata returned from {}” classname is Ec2CustomNodeAttributes.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             in = urlConnection.getInputStream();
            BufferedReader urlReader = new BufferedReader(new InputStreamReader(in; StandardCharsets.UTF_8));

            String metadataResult = urlReader.readLine();
            if (metadataResult == null || metadataResult.length() == 0) {
                logger.error("no ec2 metadata returned from {}"; url);
                return null;
            }
            ec2Attributes.put("aws_availability_zone"; metadataResult);
        } catch (IOException e) {
            logger.debug("failed to get metadata for [placement/availability-zone]"; e);




 

Run the free Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content