Yarkon Server – Run the Server for the First Time

At this point, we are ready to run the server for the first time, making sure that it is operational; then we will handle few basic setup tasks.

Run the application

Yarkon Server is a standard Unix binary. When run, it will start a web server listening on the port specified.

Important: the purpose of this step is to verify that the server is running. It is by no means a recipe to run it in a production environment. For that, please review the topic Set the server for Production.

To run the server, ssh to the server, cd to the folder where it is installed, and run it like so:

# Run the server like any Unix executable. The name of the executable is aphek
yarkon@yarkon-VirtualBox:/var/app/current/yarkon-server-trial.v309-304$ ./aphek
[14:46:12] INFO Connecting to sqlite DB:  database/aphek.db:aphek
[14:46:12] INFO
[14:46:12] INFO   ,-------------------------------------------------------------------.
[14:46:12] INFO   |                                                                   |
[14:46:12] INFO   |                                                                   |
[14:46:12] INFO   |     ##    ##    ###    ########  ##    ##  #######  ##    ##      |
[14:46:12] INFO   |      ##  ##    ## ##   ##     ## ##   ##  ##     ## ###   ##      |
[14:46:12] INFO   |       ####    ##   ##  ##     ## ##  ##   ##     ## ####  ##      |
[14:46:12] INFO   |        ##    ##     ## ########  #####    ##     ## ## ## ##      |
[14:46:12] INFO   |        ##    ######### ##   ##   ##  ##   ##     ## ##  ####      |
[14:46:12] INFO   |        ##    ##     ## ##    ##  ##   ##  ##     ## ##   ###      |
[14:46:12] INFO   |        ##    ##     ## ##     ## ##    ##  #######  ##    ##      |
[14:46:12] INFO   |                                                                   |
[14:46:12] INFO   |                                          Yarkon Admin Console     |
[14:46:12] INFO   |                                     Enterprise Edition v3.0.9     |
[14:46:12] INFO   |                                                                   |
[14:46:12] INFO   |     Environment: production (packaged)                            |
[14:46:12] INFO   |     Storage: s3                                                   |
[14:46:12] INFO   |     Server:  /console                                             |
[14:46:12] INFO   |     Client:  /                                                    |
[14:46:12] INFO   |                                                                   |
[14:46:12] INFO   |                                                                   |
[14:46:12] INFO   `-------------------------------------------------------------------'

If you see the start-up banner, the server is up and running. If you are running it on a non EC2 server, you can safely ignore any error messages related to EC2 – the application is optimized to run in EC2, but would operate normally outside of it.

Important: the application needs access to a licensing server, so make sure the network route to https://licensing.yarkons3.com is open to Yarkon Server.

By default, Yarkon Server listens on port 4830. You can change it by specifying the port when you start the application, like so:

# Run the server with specifying the port
yarkon@yarkon-VirtualBox:/var/app/current/yarkon-server-trial.v309-304$ PORT=8080 ./aphek

If you have Yarkon Server installed in a non EC2 environment, and decided to pass the API credentials to the server using environment variables, the command would be:

# Run the server with specifying the API credentials
yarkon@yarkon-VirtualBox:/var/app/current/yarkon-server-trial.v309-304$ AWS_ACCESS_KEY_ID="AKIAIPKRFP4S3EXAMPLE" AWS_SECRET_ACCESS_KEY="v/mEwFlxcRA2gvPBPKAmt95yWIwz/vJIJEXAMPLE" ./aphek

Yarkon set up

From a client machine, browse to the server and port where the server is installed. If you have your network permissions set up correctly, the browser should display the set up form.

The set up form of Yarkon creates your administrator account. Note that the user-name should be in the format of an email – this is so that the system can send you a new temporary password in case you forget it. If you do not expect to use this feature, you can provide any string that is formatted as an email address, it need not be attached to an inbox.

At this point, your set up is complete and the Yarkon system is ready to be used. You should see the the overview page of the Yarkon Admin Console application.

Important: After the set up is complete, the root URL will always open the client application. To access the Yarkon Admin Console as the system administrator, append “/console” to the application URL.

Verify the server can access S3

Using the Yarkon Server application, open the Buckets page. It should show a list of buckets, as defined by the policy you set in the step Set up the IAM role and policies.

Now open the Users page. It should include only one user, the administrator. By default, Yarkon always started in Shared security model, so the administrator user (as well as any other user) should have access to all buckets. Tp verify that, click the Actions button next to the user name in the table, and from the drop down menu choose the “View Buckets” option. In the form, you should see the same list of buckets you see in the Buckets page.

Proceed to the next step to update the CORS settings.

Next Step – Update CORS for S3
Go back to Getting Started