Migrating from Bucket to BucketV2 in Pulumi without losing data is becoming more difficult than it used to be in 2022 due to continued evolution and schema drift. Consider building support to make it more seamless to support users that need to perform the migration.

Technically there are a couple of things that could be done:

1. To overcome schema drift some code could be built to parse Bucket states into BucketV2 schema and automatically migrate them; this seems to be something that worked in 2022 but is not entirely seamless now as the schema of BucketV2 evolved separately. This would help users to simply rename Bucket to BucketV2 without moving deprecated inputs like serverSideEncryptionConfiguration to side-by-side resources and do a pulumi up.

2. Actually supporting moving deprecated inputs to side-by-side resources is a lot more involved since by default Pulumi does not correlate the states properly and will not send the prior Bucket's state to the new BucketServerSideEncryptionConfiguration resource. Document migrating aws.s3.Bucket to aws.s3.BucketV2 registry#5444 outlines manual steps but with some work it may be possible to partially automate them in a tool, possibly involving some form of automated import or refresh.

3. If nothing is done to simplify this scenario, migrating without losing data is still possible. We're finalizing a guide on how to do this.

Your feedback helps Pulumi team prioritize, please upvote this issue if you are affected by the migration and would like to see improved automated tooling support.

References:

• Resolve distinction between BucketV2 and Bucket #3803
• Document migrating aws.s3.Bucket to aws.s3.BucketV2 registry#5444
• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/version-4-upgrade
• https://www.pulumi.com/blog/announcing-v5.0.0-of-the-pulumi-aws-provider/#can-i-migrate-from-awss3bucket-to-awss3bucketv2