cloudyr / cloudyr/aws.ec2metadata
Kibana Fails to Fetch Logs After Upgrading EC2 Metadata to IMDSv2
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 12
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
I am running an ELK stack with Kibana hosted on EC2 instances. These instances have an IAM role attached that includes permissions like DescribeInstances.
After updating the EC2 instance metadata version from IMDSv1 to IMDSv2, logs are no longer appearing in the Kibana UI. Additionally, the Kibana documentation does not mention support or compatibility with IMDSv2.
Issue Observed:
Logs stop appearing in Kibana after switching to IMDSv2.
Kibana displays the following error:
403: Forbidden. You cannot use Index Management because license information is not available at this time.
Steps Taken:
Verified IAM role permissions (unchanged).
Checked Kibana logs for more details.
Looked for relevant documentation but found no mention of IMDSv2 support.
Expected Behavior:
Kibana should continue to retrieve and display logs normally after enabling IMDSv2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file or test is identified in the report. Start by reproducing the EC2 IMDSv2 upgrade scenario and reviewing the Kibana 403 error and available logs; the issue is complete when Kibana retrieves and displays logs normally and the repository documents its IMDSv2 compatibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, elasticsearch
- Domain
- cloud, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100