This message was deleted.
# getting-started
s
This message was deleted.
b
do you have aws credentials configured for that bucket?
g
I think so, I can use the AWS CLI to list, put, get
b
can you create that file
.pulumi/stacks/dev.json
?
g
Yes, I can create that object via
aws s3api put-object
b
interesting, Pulumi just uses the AWS SDK so I can't understand why that wouldn't work
g
I have tried cranking the verbose level, but I don't get any additional output
Looks like level 7 may have something extra to say https://github.com/pulumi/pulumi/blob/master/pkg/backend/filestate/state.go#L209, I will try that one specifically
hmm, cannot seem to get that logging line to fire
b
--logtostderr --verbose
should do it
g
Thanks, that got the verbose logs out!
Unfortunately, no additional information in them
b
what does
aws sts get-caller-identity
return? do you have any env vars set that might be conflicting?
g
I get a valid response with my token in it
I am wondering if I have misconfigured the
bucket-path
b
how have you set it?
g
pulumi login <s3://s3>.[aws-region].<http://amazonaws.com/[bucket-name]|amazonaws.com/[bucket-name]>
b
did you try just
pulumi login <s3://bucket-name>
?
g
Just tried that and got a new error!
@billowy-army-68599 That was it! Thank you for helping me step through that
b
No worries, Would you mind opening an issue for this in github.com/pulumi/pulumi? There’s no reason I can think of that the fully qualified bucket name shouldn’t work
g
I would be happy to, I opened a docs PR for a minor wording change that would have helped me