Overview

Use Yarkon to upload, download and share documents, manage buckets and create folders – anything that you normally do with S3 – with a fluent, intuitive and feature rich user experience, similar to what you have when using your PC. Drag & drop, context menus, copy-paste, multiple upload/download, it is all there.

Yarkon enables everyone in your organization to use your S3 storage without provisioning access to the AWS console/account and without sharing any sensitive keys with end users; all that while strictly following the permissions granted by the account administrator using the IAM service, and with full support to groups and roles.

Yarkon is integrated with the AWS Identity and Access Management (IAM) service.
You will not be able to complete the setup process without some simple yet required preparation work.

The system consists of two main modules:

  • Yarkon Web Client application, the front end used by all end users.
Yarkon Web Client
  • Yarkon Admin Console server, responsible for user permission management, and for serving the HTML files to the end clients. This module is hosted in our cloud.
Overview Page
Manage Users

To learn more about the client experience with Yarkon, please use the Demo Application - it is using the infrastructure of Yarkon Cloud and is functionally identical to it.

Yarkon Versions

Yarkon Cloud

Yarkon Cloud is an online service allowing you the user to access your AWS S3 buckets using our HTML5 based front-end application. All you need is a web browser.

End users never have to enter AWS access keys, or even be assigned any. They only get S3 permissions. No other AWS service permissions are ever exposed to end users.

Yarkon Server

Yarkon Server is a self-hosted solution, meaning that you (the customer) host it in your AWS account. It is a completely stand alone solution, that you run on an EC2 instance or a docker container within your VPC, and from thereon operates independently. Yarkon Server has no external dependencies.

Yarkon Server does not require access to any AWS access keys. The server gets its permissions through its assigned IAM role. This approach ensures that your security credentials cannot be accessed, even if the server is somehow compromised. They only get S3 permissions. No other AWS service permissions are ever exposed to end users.