This message was deleted.

sparse-intern-71089

10/05/2021, 11:16 AM

This message was deleted.

gentle-diamond-70147

10/05/2021, 4:08 PM

can you confirm your access keys are still valid with the aws cli directly? e.g.

aws s3 ls

quaint-portugal-34880

10/05/2021, 4:13 PM

Yes, And cmds like aws s3 --profile my-profile ls s3://my-state-bucket works fine

quaint-portugal-34880

10/05/2021, 4:15 PM

I tried to run with --verbose 10 as well but no debug info

gentle-diamond-70147

10/05/2021, 4:16 PM

Can you confirm that state file exists in the bucket?

aws s3 ls <s3://my-state-bucket/.pulumi/stacks/test-stack.json>

or in the AWS Console

quaint-portugal-34880

10/05/2021, 4:17 PM

Yes it does and I can copy it to my local computer

quaint-portugal-34880

10/05/2021, 4:23 PM

I found the problem I was logged in to the wrong bucket I had done pulumi login s3://my-state-buckets with an extra s instead of my-state-bucket

quaint-portugal-34880

10/05/2021, 4:23 PM

The pulumi login cmd didn't respond with an error when I logged in to an non-existing bucket

gentle-diamond-70147

10/05/2021, 6:00 PM

Hmm, yea, that's unfortunate.

127 Views

Open in Slack

Previous Next

Pulumi Community

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.