Hi, I have an error with SQS max_message_size it's related with the AWS changes in August increasing the max size of the queue, all the details are here: https://github.com/hashicorp/terraform-provider-aws/issues/43692 Is there some information about progress on when it will be supported in pulumi? Here my workflow: I have SQS resource, created long time ago when I run refresh there's no problem, no conflict no changes. Then I run pulumi up and I get a diff "update [diff: ~maxMessageSize]" Checking the details return "maxMessageSize: 1048576 => 262144". In my code I don't have any max_message_size defined so I set one to "1048576" and get this error message:

expected max_message_size to be in the range (1024 - 262144), got 1048576.

I can solve it by setting to the previous max size that work so far for me but I prefer to keep with the default size of AWS. I will try updating next month again and see if it will be supported. Thanks for reading.

According to the GitHub releases, this change (TF-AWS version 6.8.0) was merged into pulumi-aws 7.4.0: https://github.com/pulumi/pulumi-aws/compare/v7.3.1...v7.4.0 Are you using 7.4.0 or newer?

Thank you for the reply, I'm using python environment according to my pip freeze pulumi_aws==6.78.0 which is pretty old Apr 2025. I thought the dependencies were updated when updating the pulumi version, I'm running v3.193.0. I will check the documentation there's maybe some missing action or misconfiguration on my side to keep my environment up to date.

After you upgrade your provider library, I believe that you need to up once to "apply" the provider version to each resource. You can confirm this by exporting the stack state; you'll see (at least) two AWS providers, and I'm betting that the one referenced from the SQS resource is the old one. I think this means that you need to "work around" the problem once, by either refreshing or resetting the default value explicitly in code (and them removing it afterwards, once the correct provider is set into the resource).