You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AWS changed image visibility for deprecated ones (ref). In short, non-owner user can only describe deprecated AMI by by specifying its ID.
AFAIK, for Debian 8/Centos 6/Centos 7, all matched results returned from image_search are all older than 2 years. Soon they will no longer visible in search query.
Impact:
Instance cannot be created for Debian 8/Centos 6/Centos 7.
End user can set image_id for such platform in their kitchen.yml as work-around. It's nice that the driver works out-of-box.
❔ Possible Solution
For end-of-life OS which doesn't have new AMI anymore, we can explicitly set their image_id.
⤴️ Describe alternatives you've considered
n/a
➕ Additional context
n/a
The text was updated successfully, but these errors were encountered:
🙍 Problem Statement
AWS changed image visibility for deprecated ones (ref). In short, non-owner user can only describe deprecated AMI by by specifying its ID.
AFAIK, for Debian 8/Centos 6/Centos 7, all matched results returned from image_search are all older than 2 years. Soon they will no longer visible in search query.
Impact:
End user can set image_id for such platform in their kitchen.yml as work-around. It's nice that the driver works out-of-box.
❔ Possible Solution
For end-of-life OS which doesn't have new AMI anymore, we can explicitly set their image_id.
n/a
➕ Additional context
n/a
The text was updated successfully, but these errors were encountered: