You will not be able to complete the setup process without some simple yet required preparation work.
See the Getting Started guide for the complete details.
The system consists of two main modules:
- Yarkon Web Client application, the front end used by all end-users.
- 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.
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 Server is available through a Monthly Subscription, with few tiers to accommodate different usage levels. Please see the Pricing page for the full details.
Yarkon is using your S3 account. You will incur the standard AWS S3 fees, depending on your specific usage and network/API utilization. AWS publishes its S3 fees here: Amazon S3 Pricing. Using Yarkon will not make a difference to your current S3 cost.
The FREE Trial of Yarkon Server is available from this site.
Using the details you provide, a downloadable package – with a trial license key specific to you included – will be automatically built, and a link to it will be sent to your email. Please allow a few minutes for the process to complete.
Once you have downloaded the package, follow the detailed Getting Started guide to complete the setup process.
The FREE Trial is fully functional and identical to the paid release; you can have up to 10 users. The trial license expires after 30 days from the time it was first deployed.
If you choose to deploy your trial onto an AWS EC2 server, you will have to pay AWS for the instance and any additional infrastructure you provision for running the service. This amount depends on the type of EC2 instance you provision and your usage profile. This AWS cost is charged by Amazon. For the purpose of this FREE Trial, you can provision a basic t2.small Unix instance, and expect to pay about $20 monthly in AWS infrastructure services.
Upgrading from the FREE Trial to the paid monthly subscription is done from the Yarkon Admin Console.
Upgrading to Paid Subscription
You are done with your FREE trial and decided to subscribe to Yarkon?
To upgrade your account, go to the Account tab of the Yarkon Admin Console and click the “Upgrade Now” button.
You will be taken to our website, and presented with a standard credit card payment form, where you could choose your appropriate service tier – see the Pricing page for the full details. Payments are processed in real time, and your account will be updated once the payment clears, usually within a minute or less. A new license key file will then be sent to the email you provided, to replace the trial license. There is no need to reinstall the server. The monthly subscription will be charged on every monthly anniversary of the first payment.
The recommended setup of Yarkon, capable of handling up to 500 users, would cost about $45 monthly in AWS infrastructure services.
We are always sad to see you go, but we understand that sometimes the product is not a good fit or does not work for everyone.
If you are subscribed to the Monthly Plan, you can cancel your subscription using the Yarkon Admin Console – go to the Account tab of the Yarkon Admin Console and click the “Close Account” button.
You can cancel anytime, but we do not currently offer refunds for any partial month.
To get started with Yarkon Server, follow the detailed Getting Started guide available. It will lead you through the process of setting up the service using the FREE Trial, securing the server and adding end users to the system.
Yarkon Server can be customized to match your brand (skinned) and enhanced using the available API.
You can customize the following:
- Branding (white-label).
- Scripting – using the API.
- Features – easily turn on and off features available to the end users.
The Security Model controls user access to the S3 buckets. Yarkon supports different Security Models.
In case you want to use the Integrated Security Model, you need to have your organization set up in IAM.
For your convenience, an example of such an organization is provided here: Setting up the users in AWS and granting them permissions to access buckets using Groups and Policies.
Frequently Asked Questions
- How does your service work?
When users log in to Yarkon, the Yarkon Server authenticates them using their username and password credentials. Once their identity is verified and confirmed, the server will authorize the users with AWS S3, and if needed, with AWS IAM. See Security Models for more about the authorization process.
- How are users added to the system?
Users are managed by the administrator, using the Yarkon Admin Console server application. The administrator can add as many end-user accounts as needed, and remove them when they no longer require access to AWS S3. The end-users themselves do not need access to the Yarkon server, or to the AWS Dashboard.
- As the system administrator, how do I access the Admin Console?
After the system is set up, the root URL will always open the client application, the Yarkon HTML Browser. To access the Yarkon Admin Console application, simply append a “/console” to the application URL. For instance, if the domain name you set up for the application is “https://yarkon.mycompany.com”, then to access the Yarkon Admin Console application, use “https://yarkon.mycompany.com/console”. It will present the Login screen, which will prompt for your Administrator Credentials. End users will not be able to login with their credentials.
- How do end-users access their S3 buckets with Yarkon?
End-users are using the Yarkon Web Application. This is a client side HTML5 application, running inside a user’s browser. To be able to use the application, a user only needs to provide her username and password. The username is the user’s email, the password can be managed by the user herself. For more about the client application and its feature, see the Demo.
- Where are user passwords kept?
In Yarkon Server, the user passwords are kept in a database, set up in one of two main configurations, chosen by you: local or shared. By default, a local database on the same EC2 is used, making it a secure and cost-effective implementation. In case you want to use more than one Yarkon Server (for instance, for high availability and redundancy), a shared database is used. You can bring your own database, or use AWS RDS in the same way we do for Yarkon Cloud. The password are hashed using the Bcrypt algorithm using a random salt.
- How do end-users get access to their S3 buckets?
The Yarkon Admin Console does not have access to your API credentials. It gains access to S3 resources based on the permissions granted to it through the role used for the EC2 instance. No API credentials are ever shared with any user and are ever sent over the internet to a client machine. Following AWS strictest security recommendations, clients only get short-lived temporary credentials.
- Do you require an Email server?
The product enables the end-users to self service their credentials, meaning that an end-user can reset her password in case it is lost. In this case, the email server is used to securely and confidentially communicate the newly auto-generated, temporary password to the user.
You can set the email integration to None – but if you do so, users will not be able to reset their own password, and when a new user is created, the administrator will have to communicate their new password to them.
- Can I use my GMail account as an Email server?
You can, but you should not. Even though Gmail is the fastest way to get started with sending emails, it is by no means a preferable solution. Gmail expects the user to be an actual user and not a robot/application, so it runs heuristics for every login attempt and blocks anything that looks suspicious. Being that this is an enterprise product, having access to an Email server is expected and required. Use the same Email server you use for your other automated emails.
- Can I use AWS SES as an Email server?
Absolutely. You can use SES as a service – the machine role created for Yarkon Server should have access to the API by default.
Alternatively, you can also use SES as SMTP – follow this document from Amazon on how to obtain your credentials; use the appropriate endpoint for the Server Name. Use the aforementioned SMTP credentials for the Username and Password. The Send From field must be a verified email address you can send from. Use the Display Name field to add a user friendly name.
- Do you offer a free trial?
We offer a FREE tier for Yarkon, but we also offer a FREE Trial for any edition of Yarkon. If you only want to see the system in action, use the Demo Application.
- Where can I see the user manual for the client application?
We add to our documentation all the time, and enhance it as needed. To get a good understanding of how to use the Yarkon web client application, please check out the tour: Demo.
- What are the known limitations of Yarkon?
See the limitations page for a list of current known limits on using Yarkon.
- Suppose I encounter an issue, can you help?
Absolutely. We have a good experience with organizations being able to set up the application without assistance, but your situation might be unique. Please contact us with any question you might have.
- I have a question that is not on this FAQ, can you add it?
We can, but first please check the full list of Frequently Asked Questions. If the answer to your question is not there, please contact us. If we think the answer to your question could benefit others, we will add it to the FAQs.