jenkinsci / jenkinsci/ec2-plugin

[JENKINS-71655] JENKINS-65127 broke support for AMIs without instance metadata

Open
#1,902 1 comment 0 reactions 0 assignees View on GitHub
component:ec2-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
292
Forks
709
Avg merge
3d 16h
Merged PRs (30d)
4

Description

With the changes in JENKINS-65127 you cannot use the latest ec2-plugin to launch an AMI which doesn't support instance metadata. 

---
Originally reported by silentsnowman, imported from: JENKINS-65127 broke support for AMIs without instance metadata


  • assignee: thoulen
  • status: Open
  • priority: Minor
  • component(s): ec2-plugin
  • resolution: Unresolved
  • votes: 1
  • watchers: 3
  • imported: 2025-12-06

Raw content of original issue

With the changes in JENKINS-65127 you cannot use the latest ec2-plugin to launch an AMI which doesn't support instance metadata. 

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the EC2 plugin changes from JENKINS-65127 and the AMI launch path, then reproduce the failure with an AMI that lacks instance metadata. Confirm the expected behavior for that AMI and add coverage if the relevant test location can be identified; the issue is done when such AMIs can be launched again.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, java
Domain
cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.