Re: How to access s3 when a prefix is restricted.
Thanks for your feedback.
5.14.2 beta with the fix was released meanwhile.
5.14.2 beta with the fix was released meanwhile.
- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- seino
Re: How to access s3 when a prefix is restricted.
Thanks for a reply.
I used the development version.
This problem was resolved.
I used the development version.
This problem was resolved.
- martin
Re: How to access s3 when a prefix is restricted.
This issue has been added to the tracker:
https://winscp.net/tracker/1712
I'm sending you an email with a development version of WinSCP to the address you have used to register on this forum.
https://winscp.net/tracker/1712
I'm sending you an email with a development version of WinSCP to the address you have used to register on this forum.
- seino
Re: How to access s3 when a prefix is restricted.
Thanks for a reply.
I upload the log.
I masked secret key etc.
I upload the log.
I masked secret key etc.
- martin
Re: How to access s3 when a prefix is restricted.
Please attach a full session log file showing the problem (using the latest version of WinSCP).
To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
- Guest
How to access s3 when a prefix is restricted.
Hi
When the following IAM policy is set, I could not access to S3 after Remote Directory is set to /bucket-name/folder1/ on WinSCP.
Could you tell me to access s3 in this case ?
"Action": "s3:ListBucket",
"Resource": "arn:aws:s3:::bucket-name",
"Condition": {
"StringLike": {
"s3:prefix": "folder1/*"
}
Error message in log file
(XXXXX is mask)
. 2018-12-12 11:30:21.693 [<?xml version="1.0" encoding="UTF-8"?>
. 2018-12-12 11:30:21.693 <Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>XXXXX</RequestId><HostId>XXXXX</HostId></Error>]
Enviroment
* WinSCP 5.13.5
* Windows 7
When the following IAM policy is set, I could not access to S3 after Remote Directory is set to /bucket-name/folder1/ on WinSCP.
Could you tell me to access s3 in this case ?
"Action": "s3:ListBucket",
"Resource": "arn:aws:s3:::bucket-name",
"Condition": {
"StringLike": {
"s3:prefix": "folder1/*"
}
Error message in log file
(XXXXX is mask)
. 2018-12-12 11:30:21.693 [<?xml version="1.0" encoding="UTF-8"?>
. 2018-12-12 11:30:21.693 <Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>XXXXX</RequestId><HostId>XXXXX</HostId></Error>]
Enviroment
* WinSCP 5.13.5
* Windows 7