This message was deleted.

This error means that you have a dependency among your AWS resources that is not explicit in your Pulumi program in some way. Are you managing both the LaunchConfiguration and AutoScalingGroup in Pulumi? Can you share the changes you tried to make and the diff you are seeing?

Thanks, when looking at the diff it was much more obvious what the issue was. I had to manually delete an autoscaling group on AWS and refresh the stack. Do you, by chance, know how to properly configure autoscaling policies for a Fargate Service? I was configuring the service like below, but it seemed that it was creating an EC2 autoscaling group rather than a Service Auto Scaling policy: `const targetGroup = alb.createTargetGroup(

targetGroup-${envName}

, {`

port: 80,

targetType: "instance"

});

`const autoScalingGroup = cluster.createAutoScalingGroup(

insig-express-autoscaling-${envName}

, {`

targetGroups: [targetGroup],

subnetIds: awsx.ec2.Vpc.getDefault().publicSubnetIds,

templateParameters: {

minSize: fargate.desiredCount || 2,

maxSize: fargate.maxCount || 10,

defaultCooldown: fargate.defaultCooldown || 60

},

launchConfigurationArgs: {

associatePublicIpAddress: true

},

});

`autoScalingGroup.scaleToTrackAverageCPUUtilization(

keepAround50Percent-${envName}

, {`

targetValue: 50,

});

`const policy = autoScalingGroup.scaleToTrackRequestCountPerTarget(

onHighRequest-${envName}

, {`

targetValue: 2000,

targetGroup: targetGroup,

});

Hey @refined-vegetable-66224, I’ve got into Fargate Autoscaling dilemma too. Did you ever find a solution for it? I stumbled upon the fact that service’s task definition uses awsvpc network mode (required for the AWS Fargate launch type), and I must choose IP as the target type. This doesn’t work with

createAutoScalingGroup

method – under the hood it uses cloudformation template that expects that targetGroup will be of a different type -

Instance

.