Post a reply

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

Ryan Smith

Ok. I'll Try to get the vendor to add those and see if it works.

It's maddening cause if I could just get them to actually put in a little effort and look at some logs this would probably be solved in 5–10 mins but instead they want to be stubborn and lazy.
martin

You definitely need s3:ListBucket permission, probably also s3:GetBucketLocation.
Ryan Smith

Oops Sorry I was already doing that. I will attach a log and this is what I think is the problem I'm pretty sure they only have this allowed and I think WinSCP needs more rights than this to connect and put. But since I can't see their end and they refuse to help. I'm trying to find the minimum rights WinSCP needs to open and put to a location.
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "s3:putObject"
            ],
            "Resource": [
                "arn:aws:s3:::bucket-name/*"
            ]
        }
    ]
}
Ryan Smith

S3 bucket permissions needed to access with WinSCP

We have a S3 bucket with a vendor that setup us to only send files too.

It works with the CLI but I can't get it work with WinSCP no matter how much I try and the vendor is being unhelpful giving us the we do not work with 3rd party tools response.

Can anyone tell me the Minimum Permissions WinSCP needs to put to a subdirectory in the bucket or even just access it? I get access denied on the open and I can't even get the GUI to connect to test the paths for script.