AWS Setup – Shared Security – Yarkon Cloud
When using the Shared Security Model, all users have the same access permission, meaning that they can all see the same buckets, and perform the same actions.
If you want different users to have different permissions, you need to set up Yarkon to use the Integrated Security Model instead. Follow this guide to get it done.
We cover the following steps:
- Setting up the AWS user and policy required for the Yarkon Admin Console.
- Subscribing to the service, and provisioning the administrator account.
- Adding the users to Yarkon and verifying that the proper permissions are set.
- Setting up CORS on the target buckets.
When done, you should have the AWS organization set up, the Yarkon Admin Console set up and fully operational, with the end-users being able to access S3 buckets limited by the access policies you defined, using the Yarkon Web Client.
Note: the guide assume good working knowledge of AWS and the AWS console, as well as the required services: S3, IAM.