This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Hey good morning. We are currently storing our pulumi file in an S3 bucket. This bucket is encrypted using a KMS key. When running

pulumi login <s3://mybucket>

I get this error: error: problem logging in: read ".pulumi/meta.yaml": blob (key ".pulumi/meta.yaml") (code=Unknown): AccessDenied: Access Denied status code: 403, request id: 8N5AVCW0D0CF17DY, host id: VsmKrytuAAGUIU+pdQ6ZrikCcdD7uGxRru7oauhI+MOgIijUlWxp4YnNtRDptX9c4Z02GSvDcXA= Im assuming its because the access key that im using needs permissions updated..If this is the case what IAM permissions are needed to perform this ?

This message was deleted.

Hi! I am trying to setup Pulumi with Azure backend (Blob Storage) using az login from this documentation: https://www.pulumi.com/docs/concepts/state/#azure-blob-storage It is mentioned that "The Azure account must have the Storage Blob Data Contributor role or an equivalent role with permissions to read, write, and delete blobs." I have a contributor role on my account, and can manage blob storage and its containers, but I am getting: "RESPONSE 403: 403 This request is not authorized to perform this operation using this permission." Two questions: • Is Pulumi looking EXACTLY for this role to be assigned to the logged-in account? • Is it possible to setup this in a way, that only the READER role is required, so I could use Preview but not Up? (local machine development)

This message was deleted.

Is there a way to use podman with pulumi? Use case: 1. Have a podman (OCI) image get built (can be done outside of pulumi script if needed) 2. Push it to ECR 3. Use it as a lambda image