Open vedantroy opened 3 years ago
This is currently a limitation of the underlying implementation in how launch configurations get created: https://github.com/pulumi/pulumi-awsx/blob/5dab49f887e3fdfc20e008bdeb2c27a2ed4dda96/nodejs/awsx/autoscaling/launchConfiguration.ts#L59
@leezen, correct me if I am wrong, is the solution to allow the spot by allowing the value as undefined?
placementTenancy: args.placementTenancy,
Currently, from my understanding, the only workaround for me is to create from scratch:
keen to know whether it is possible to allow undefined value?
Thanks
@kororo That sounds right, though I haven't had a chance to trace through the code to verify that that will work as intended. Definitely open to taking a PR here!
I am trying to launch a ECS cluster that is backed by an auto-scaling group that uses spot instances.
To do this, I use the following code:
Expected behavior
Something akin to this should work (a ecs cluster should be created that is backed by an auto-scaling group that launches spot instances).
Current behavior
Running
pulumi up
results in the following error: "* Error creating launch configuration: ValidationError: Placement tenancy is not supported for spot instances.".I tried explicitly setting
placementTenancy
toundefined
, but that did not work either.Steps to reproduce
The code is @ the top of this post.
Context (Environment)
I want to launch ECS clusters backed by spot instances, and I can't do this with Pulumi right now.