4 Answers
- Newest
- Most votes
- Most comments
0
Hey,
I think your problem is the policy type. You need to return the json string, rather than the object.
answered 5 years ago
0
Thanks!
Changing the last part to this fixed the issue by making the policy a string.
response = {
Role: 'my_role_arn',
Policy: JSON.stringify(policy),
HomeDirectory: '/my-bucket/in/myuser',
};
answered 5 years ago
0
PriorityITS:
Are you still seeing issues using Scope Down Policy with with your Custom Identity Provider integration? I'm not sure if you are aware, but with our recent logical directories for S3 feature you can control access by mapping S3 paths to end user visible paths. That way only those portions of your S3 bucket would be visible to them. Here are a few resources to get started:
- The announcement for this feature (for use cases where it's applicable): https://aws.amazon.com/about-aws/whats-new/2019/09/aws-transfer-for-sftp-now-supports-logical-directories-for-amazon-s3/
- Blog post on how to "chroot" your users to a designated folder:https://aws.amazon.com/blogs/storage/simplify-your-aws-sftp-structure-with-chroot-and-logical-directories/
- Building a data distribution service using logical directories:https://aws.amazon.com/blogs/storage/using-aws-sftp-logical-directories-to-build-a-simple-data-distribution-service/
Please let me know if you have any questions or want to provide me details on your use case over private message.
Thanks,
Smitha
answered 4 years ago
Relevant content
- asked 5 months ago
- asked 4 years ago
- asked 3 years ago
- asked 5 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 3 years ago