2 Answers
- Newest
- Most votes
- Most comments
0
It seems the reason this is occurring is because M4 instances use an Amazon Linux 1 AMI by default. It is possible to set the AMI to a v2 AMI in the Batch compute environment setup -- you need to look up the specific AMI for your region though.
It seems some instance types automatically pick a v2 AMI by default; hopefully this will be the case for M4 instances in the future as well.
answered 3 years ago
0
note that with the recent support for AL2, you don't need to look it up anymore - just specify AL2
answered 3 years ago
Relevant content
- asked 5 years ago
- AWS OFFICIALUpdated 2 years ago