AWS recently introduced support for specifying a CustomAmiId per instance type within an InstanceTypeConfigs block for an InstanceFleet. This enhancement provides the flexibility to use different AMIs with different EC2 instance types within a single instance fleet, which is particularly useful for diverse workloads that may require different configurations or software packages.
AWS Support Example:
Here's an example of how AWS supports this feature:
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
Description
AWS recently introduced support for specifying a CustomAmiId per instance type within an InstanceTypeConfigs block for an InstanceFleet. This enhancement provides the flexibility to use different AMIs with different EC2 instance types within a single instance fleet, which is particularly useful for diverse workloads that may require different configurations or software packages.
AWS Support Example:
Here's an example of how AWS supports this feature:
Affected Resource(s) and/or Data Source(s)
Potential Terraform Configuration
References
https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-instance-fleet.html#:~:text=Example%3A%20Add%20a%20task%20node%20to%20a%20running%20cluster%20with%20multiple%20instance%20types%20and%20multiple%20custom%20AMIs
Would you like to implement a fix?
None