This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

I'm trying to set up logging for my Cloudfront distributions. In the AWS console I see a legacy s3 option, and then v2 CloudWatch, Kinesis and S3 options. In pulumi, with either the aws classic or the aws native (cloud control) module I only see options for s3 or kinesis. I would like to use Cloudwatch if I can as that's where all my ECS logs go. Is there a way to do this with pulumi?

After upgrading to Pulumi v3.122.0,

pulumi up

takes a LONG time (>20 minutes, even when making relatively few updates) with a Google Cloud Storage Bucket as the backend, also there is a LOT (hundreds of megabytes, to gigabytes) of traffic to Google Cloud during that time. The stack JSON as a set of bytes is ~3MiB, so it makes no sense that it would be doing THAT much I/O. Running

pulumi refresh

(with or without

--skip-preview

) is unaffected. Is this a known issue ? I wasn't able to really find anything documented on it. One thing that did come up was checkpoints, but during the time that excessive network I/O is happening no resources are being updated. Experiments to try: 1. Disable checkpointing 2. Use tracing

This message was deleted.

This message was deleted.

This message was deleted.