Workflow failure: cron

[pulumi-bot]

Workflow Failure

cron has failed. See the list of failures below:

• 2024-09-26T07:39:25.000Z

• 2024-09-27T07:43:52.000Z

[t0yv0]

      	* creating Auto Scaling Launch Configuration (example-aws-profile-role-py-nodeLaunchConfiguration-75f1fc3): operation error Auto Scaling: CreateLaunchConfiguration, https response error StatusCode: 400, RequestID: e086d096-0808-4bf2-a5ea-0b6437f55dc9, LimitExceeded: Launch Configuration limit exceeded - You may only have 200 launch configurations

[t0yv0]

Dug a bit deeper in here, it sounds like aws.ec2.LaunchConfiguration resource is discouraged.

https://docs.aws.amazon.com/autoscaling/ec2/userguide/launch-configurations.html

You can not call CreateLaunchConfiguration with new Amazon EC2 instance types that are released after December
31, 2022. In addition, any new accounts created on or after June 1, 2023 will not have the option to create new launch
configurations through the console. Starting on October 1, 2024, new accounts will not be able to create new launch
configurations by using the console, API, CLI, and CloudFormation. Migrate to launch templates to ensure that you don’t
need to create new launch configurations now or in the future. For information about migrating your Auto Scaling groups
to launch templates, see Migrate your Auto Scaling groups to launch templates.

However this example depends on it

eks:index:Cluster example-cluster-with-serviceiprange

With:

const cluster = new eks.Cluster(`${projectName}`, {
    vpcId: vpc.vpcId,
    publicSubnetIds: vpc.publicSubnetIds,
    desiredCapacity: 2,
    minSize: 2,
    maxSize: 2,
    nodeAmiId: "ami-0384725f0d30527c7",
    deployDashboard: false,
    enabledClusterLogTypes: [
        "api",
        "audit",
        "authenticator",
    ],
    kubernetesServiceIpAddressRange: "172.16.0.0/20"
});

There it is:

 +   pulumi:pulumi:Stack                           example-cluster-with-serviceiprang
 +   ├─ eks:index:Cluster                          example-cluster-with-serviceiprang
 +   │  ├─ eks:index:ServiceRole                   example-cluster-with-serviceiprang
 +   │  │  ├─ aws:iam:Role                         example-cluster-with-serviceiprang
 +   │  │  ├─ aws:iam:RolePolicyAttachment         example-cluster-with-serviceiprang
 +   │  │  ├─ aws:iam:RolePolicyAttachment         example-cluster-with-serviceiprang
 +   │  │  └─ aws:iam:RolePolicyAttachment         example-cluster-with-serviceiprang
 +   │  ├─ eks:index:ServiceRole                   example-cluster-with-serviceiprang
 +   │  │  ├─ aws:iam:Role                         example-cluster-with-serviceiprang
 +   │  │  └─ aws:iam:RolePolicyAttachment         example-cluster-with-serviceiprang
 +   │  ├─ eks:index:RandomSuffix                  example-cluster-with-serviceiprang
 +   │  ├─ aws:iam:InstanceProfile                 example-cluster-with-serviceiprang
 +   │  ├─ aws:ec2:SecurityGroup                   example-cluster-with-serviceiprang
 +   │  ├─ aws:ec2:SecurityGroupRule               example-cluster-with-serviceiprang
 +   │  ├─ aws:eks:Cluster                         example-cluster-with-serviceiprang
 +   │  ├─ aws:ec2:SecurityGroupRule               example-cluster-with-serviceiprang
 +   │  ├─ aws:ec2:SecurityGroup                   example-cluster-with-serviceiprang
 +   │  ├─ aws:ec2:SecurityGroupRule               example-cluster-with-serviceiprang
 +   │  ├─ aws:cloudformation:Stack                example-cluster-with-serviceiprang
 +   │  ├─ eks:index:VpcCni                        example-cluster-with-serviceiprang
 +   │  ├─ pulumi:providers:kubernetes             example-cluster-with-serviceiprang
 +   │  ├─ aws:ec2:SecurityGroupRule               example-cluster-with-serviceiprang
 +   │  ├─ kubernetes:core/v1:ConfigMap            example-cluster-with-serviceiprang
 +   │  ├─ aws:ec2:SecurityGroupRule               example-cluster-with-serviceiprang
 +   │  ├─ aws:ec2:LaunchConfiguration             example-cluster-with-serviceiprang
 +   │  ├─ aws:ec2:SecurityGroupRule               example-cluster-with-serviceiprang
 +   │  └─ pulumi:providers:kubernetes             example-cluster-with-serviceiprang

Perhaps since it's discouraged is why I could not easily find it in the Console.

I can restart for now.

@flostadler curious for your 2c here, should we track removing dep on aws.ec2.LaunchConfiguration, or did it make 3.x scope already. Thanks!

[t0yv0]

Keeps happening so coded a cleanup for these:

https://github.com/pulumi/aws-account-cleanup/pull/79

[t0yv0]

Applied cleanup. Should be bettter.