This message was deleted.

can you share your code?

It's a lot of code haha. Here's one such failure:

const s3_read_only_role = new aws.iam.Role("s3-read-only-role", {
  assumeRolePolicy: JSON.stringify({
    Version: "2012-10-17",
    Statement: [
      {
        Effect: "Allow",
        Principal: {
          Service: "<http://ec2.amazonaws.com|ec2.amazonaws.com>",
        },
        Action: "sts:AssumeRole",
      },
    ],
  }),
  description: "Allows EC2 instances to read from s3",
  forceDetachPolicies: false,
  inlinePolicies: [{}],
  managedPolicyArns: ["arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess"],
  maxSessionDuration: 3600,
  path: "/",
  tags: {
    role: "ec2ReadS3",
  },
  tagsAll: {
    role: "ec2ReadS3",
  },
});

did you update the aws library?

hi @white-processor-23859 so tags_all was incorrect - it's an output based property only

I can do that change, but do you know why it would stop working today?

if you have upgraded to a new version of pulumi-aws then that would have been the case

Got it. Let me see if I can roll back the aws version real quick

sorry this was the case, this was me that actually mad ethe change 🙂

no problem. I appreciate your help 🙂 . It was partially our fault too as we didn't have our aws version pegged...we had

^4.14.0

, so it opaquely updated, which explains the sudden failures.

@white-processor-23859 FWIW, swapping to defaultTags should actually fix the functionality as tagsAll actually caused an overwrite of tags on individual resources

removing the caret fixed the error!