Hello team, I'm having trouble with

pulumi refresh

hanging (over an hour without changing) when I run it. Prior, I ran a

pulumi cancel

and it returned 409 - the update has already completed. I'm using pulumi v3.121.0. I have checked my AWS credentials and they are working. I'm using pulumi to manage 129 resources which are 4 ECS tasks and all the related cluster/security setup.

pulumi delete

seems to hang as well. Are there any other commands I can try or is the only option to delete the stack items manually?

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Hi everyone, I'm trying to upgrade EKS NodeGroup from AL2 to AL2023, based on documentation:

Update the node group in place. Pulumi does this by first creating the new replacement nodes and then shutting down the old ones which will move pods to the new nodes forcibly. This is the default behavior when node groups are updated.

It seems does not happen to me. The preview shows the strategy is

replace

instead of

update

-> entire nodeGroup will be deleted first, then creating new nodeGroup, instead of update node by node.

pulumi:pulumi:Stack: (same)
    [urn=urn:pulumi:stack::eks::pulumi:pulumi:Stack::stack]
    --aws:eks/nodeGroup:NodeGroup: (delete-replaced)
        [id=stack:test-upgrade]
        [urn=urn:pulumi:stack::eks::aws:eks/nodeGroup:NodeGroup::test-upgrade]
    +-aws:eks/nodeGroup:NodeGroup: (replace)
        [id=stack:test-upgrade]
        [urn=urn:pulumi:stack::eks::aws:eks/nodeGroup:NodeGroup::test-upgrade]
      ~ amiType: "AL2_x86_64" => "AL2023_x86_64_STANDARD"
    ++aws:eks/nodeGroup:NodeGroup: (create-replacement)
        [id=stack:test-upgrade]
        [urn=urn:pulumi:stack::eks::aws:eks/nodeGroup:NodeGroup::test-upgrade]
      ~ amiType: "AL2_x86_64" => "AL2023_x86_64_STANDARD"

Am I missing something?

This message was deleted.

Hey good morning. We are currently storing our pulumi file in an S3 bucket. This bucket is encrypted using a KMS key. When running

pulumi login <s3://mybucket>

I get this error: error: problem logging in: read ".pulumi/meta.yaml": blob (key ".pulumi/meta.yaml") (code=Unknown): AccessDenied: Access Denied status code: 403, request id: 8N5AVCW0D0CF17DY, host id: VsmKrytuAAGUIU+pdQ6ZrikCcdD7uGxRru7oauhI+MOgIijUlWxp4YnNtRDptX9c4Z02GSvDcXA= Im assuming its because the access key that im using needs permissions updated..If this is the case what IAM permissions are needed to perform this ?

This message was deleted.

This message was deleted.