2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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.
répondu il y a 3 ans
0
note that with the recent support for AL2, you don't need to look it up anymore - just specify AL2
répondu il y a 3 ans
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an