Now Cluster.addAsgCapacityProvider() need to be specified machineImageType to determine whether it is MachineImageType.AMAZON_LINUX_2 or MachineImageType.BOTTLEROCKET.
But this approach is not very intuitive.

Because when you create AsgCapacityProvider, you already can specify the machineImageType.

example create Bottlerocket autoscaling provider:

const capacityProviderBottlerocket = new ecs.AsgCapacityProvider(stack, 'providerBottlerocket', {
      autoScalingGroup: autoScalingGroupBottlerocket,
      enableManagedTerminationProtection: false,
      machineImageType: ecs.MachineImageType.BOTTLEROCKET, // <- machineImageType
    });

But now you have to specify machineImageType once at Cluster.addAsgCapacityProvider(capacityProviderBottlerocket, { machineImageType: ecs.MachineImageType.BOTTLEROCKET, }) again, which is very unintuitive.

const cluster = new ecs.Cluster(this, 'cluster', { vpc, });

const capacityProviderBottlerocket = new ecs.AsgCapacityProvider(stack, 'providerBottlerocket', {
      autoScalingGroup: autoScalingGroupBottlerocket,
      enableManagedTerminationProtection: false,
      machineImageType: ecs.MachineImageType.BOTTLEROCKET, // <- machineImageType
    });

cluster.addAsgCapacityProvider(capacityProviderBottlerocket, {
 machineImageType: ecs.MachineImageType.BOTTLEROCKET,
});

And if you create Bottlerocket autoscaling provider, but forgot to specify machineImageType at Cluster.addAsgCapacityProvider(), Bottlerocket Node will failed to register to ecs cluster.
root case is:

Proposed Solution

Let Cluster.addAsgCapacityProvider() not need to specify machineImageType.

cluster.addAsgCapacityProvider(capacityProviderBottlerocket, {
 machineImageType: ecs.MachineImageType.BOTTLEROCKET,
});

cluster.addAsgCapacityProvider(capacityProviderBottlerocket);

Other

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

This is a 🚀 Feature Request