Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors when trying to upload upload an asset to s3 #28

Closed
tfhartmann opened this issue Jun 2, 2017 · 5 comments
Closed

Errors when trying to upload upload an asset to s3 #28

tfhartmann opened this issue Jun 2, 2017 · 5 comments

Comments

@tfhartmann
Copy link

Hi,

Thanks for creating this plugin! We recently switched to it, but have been getting a Access Denied error, and are trying to figure out why. The IAM user that upload the access hasn't changed, just the gem we use to upload the asset. I've attached an example of the policy attached to the IAM user, is there a set of permissions that this plugin needs? I suspect PEKAC on my part, so any help would be much appreciated! Thanks again!

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "s3:*"
            ],
            "Resource": [
                "arn:aws:s3:::our-bucket/prefix/path/*"
            ]
        }
    ]
}
@joshdholtz
Copy link
Member

@tfhartmann Not a problem! Glad you like it 😊 This is almost an exact copy of what was in fastlane proper (if that is what you are referring to switching from). I originally created that plugin in fastlane proper but it made more sense to pull out as a plugin for faster updating 😉

So there MIGHT be something that changed between that one (that I think you switched from) and this one. This one MIGHT be using a newer version of the AWS ruby gem which could have done things differently 🤔 I can take a look at the old code and new code to possibly see what could be causing this.

@joshdholtz
Copy link
Member

@tfhartmann Where you able to figure this out yet?

@joshdholtz
Copy link
Member

Closing issue due to no activity

@matthewweldon
Copy link

@joshdholtz @tfhartmann
Did you guys figure out the exact privileges that are needed on the bucket? I keep getting access denied.

@REPTILEHAUS
Copy link

Also getting permissions errors. looks like this is inactive so uploading via CURL might be the best solution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants