This message was deleted.
# general
s
This message was deleted.
c
when I click
open in AWS console
from pulumi , this is what I get
q
Is pulumi using your credentials to create resources in AWS?
It's possible that pulumi is using a different one compared to the one you used to sign in to the console. So, your credentials don't sufficient permissions to use S3
c
it uses a accesskeyID and accessSecret that I created which is more like a user
q
Are the IAM policies the same?
c
yes we both administrators
q
Does both the users have a policy have the action
S3: ListAction
? It's a good idea to review the permissions for S3
c
The policy basically looks like this
Copy code
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "*",
      "Resource": "*"
    }
  ]
}
h
so the bucket is showing up but you don't have access to the files in it?
c
it does not show up. I can't see any resources that is listed in pulumi
h
is the screen shot you shared form the same issue ?
c
yes it is
h
i guess i am confused. the screen shot shows you don't have permissions error on a file in a bucket that's visible. but you are suggesting yo don't see any thing...
c
basically my aws console is showing no resources but these resources exist . I can verify because our staging environment that uses cloudfront is up
so I was able to get to that page by going to Pulumi and click "View on aws" it took me straight to the screenshot.
h
it doesnt make sense. any ways, i would get the AWS account number from the URN in Pulumi and make sure when you are logging in on AWS console, you are using the same account....