Thanks — but I don’t think this is the right thing. In S3 you set the bucket lifecycle configuration to active Intelligent Tiering — and then you have to separately configure Intelligent Tiering to active ARCHIVE/DEEP_ARCHIVE for those objects. In S3 console it’s a completely separate section of the UI. Separate API as well.
No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.