Skip to main content


This walkthrough is aimed at first-time users of Argonaut. You will automate the deployment of an example application to Kubernetes (EKS) runtime on the AWS cloud using Argonaut.

The pre-requisites for this deployment are:

  • A GitHub account
  • An AWS account (free or paid)

1. Create an account

If it’s your first time using Argonaut, you must sign up for an account. You will then receive an email with an account activation link. Alternatively, if you already have one, log into your account.

2. Create your workspace

Each Argonaut account needs to be associated with one Argonaut workspace.

  1. Type in a name for your Workspace. This CAN be changed later.
  2. Click Next

Create your workspace

3. Connect your AWS account

You will be taken to the Connections page under Settings. Argonaut connects to AWS as an IAM user. Multiple connections to the same AWS account are not allowed.

Connect to your AWS account

  1. In the Connect Your Cloud section, select Account +
  2. Select Amazon Web Services and click Create AWS integration
  3. Log into your AWS account, if you aren’t already logged in.
  4. You’ll be redirected to the AWS CloudFormation's Create stack page.
  5. Note that the Create stack page is already populated with Argonaut-specific parameters.
  6. Click on the Create stack button.
  7. You should now see the new stack’s page on AWS CloudFormation dashboard.
  8. Navigate back to Connections page from your Settings.
  9. Scroll to Connect Your Cloud —> AWS.
  10. Click Refresh.
  11. You should see your newly connect AWS account ID.
  12. Against the AWS account ID, verify that the connection shows as Successful.

4. Connect your GitHub account

On the same screen, you will see a Version control option. Here, you can connect Argonaut to your GitHub or GitLab repository. For this demo, we use GitHub.

  1. In the Version Control section, click on Account +
  2. Choose GitHub, and click on the Connect button.
  3. Click on the GitHub account you’d like to connect with Argonaut. You’ll host your sample application on this account.
  4. Click on Install to install ArgonautBot on your chosen GitHub account.
  5. Enter your password, and click on Confirm Password.
  6. On successfully connecting your GitHub account, you’ll be redirected to the Version Control page that shows your GitHub account.

5. Create an AWS environment

Argonaut automatically sets up environments easily in minutes

  1. Select the Environments Tab from the sidebar.
  2. Click on Environment +
  3. Choose Amazon Web Services.
  4. Give your environment a name env.
  5. Choose your environment’s region. An environment's region CAN’T be changed later.
  6. Click on Create.

Create your AWS environment

To check if the environment creation was successful, navigate to the environment page from the sidebar, and look for your environment's name in the list. Ready environments have a green check symbol indicating the operational status.

6. Create an EKS cluster

To deploy your application on K8s, you need to first create a K8s cluster:

  1. Select Environments from the sidebar.
  2. Select the newly created env environment.
  3. Select the Infra tab from the top bar.
  4. Click on Resource +
  5. In the create resource form, Select EKS.
  6. Input the following values:
    1. Cluster Name as dev.
    2. Node group name as test.
    3. Instance Type t3.medium.
    4. Instance class as Spot.
    5. Desired Node Count as 3
    6. Set Nodes: Min as 3 and Max as 5.
    7. Set Disk Size as 50.
  7. Click on Create EKS. Create your cluster

7. Set up automatic deployment

  1. Fork the battleships repository into your GitHub account - the same account that you’ve connected to in Argonaut. The rest of the steps assume that the name of the forked repository is also battleships.
  2. On your Argonaut dashboard, click on Applications on your sidebar.
  3. Click Application + on the top right. Create your app
  4. Give it an application name, Battleship.
  5. In the Battleship application, select Pipeline +
  6. This takes you to our interactive deployment builder step. Here you will set the two stages of deployment - Build and Deploy stage.
  7. Enter a pipeline name as Test Pipeline.
  8. Select your Git account, battleships repository, and main branch.
  9. Build stage. You can access this by selecting the Build stage. Build stage configurations
    1. Set Build Config name as firstbuild
    2. In Path, fill ./Dockerfile.
  10. Deploy Stage. Select the Deploy stage.
    1. Set Service Type as Stateless.
    2. Ensure the correct environment and kubernetes cluster is chosen.
    3. Under Network Services, click Add Service.
      1. Fill your Hostname.
      2. Fill the port you want the application to run on in Container Port.
    4. Ensure that Resource Requests & Limits have values set by default.
    5. Click Commit to Repo.
  11. Once this is done, your app builds and deploy configurations are saved and ready to be deployed.
  12. Go to the Applications from the sidebar and select your app. Now click on Trigger Pipeline.
  13. You will see the status of deployment under Run History. You can also view the history of the Build and the Run stages independently below.
  14. Now, go to the Applications page and look for your application Battleship.
  15. Scroll right, and click the PREVIEW URL against Battleship. This is the URL where your Battleship application is being hosted.
  16. Mavigate to the URL you provided as Hostname. You should see the following screen:

Battleships index page

You’ve successfully deployed your example application using Argonaut! Let’s test whether your application is automatically deployed when you push a code change.

8. Test automatic deployment

You’re now ready to test if your app gets deployed automatically whenever any code change is pushed to it. Let’s make a code change, and view the app again.

  1. Git clone your forked battleships repository on your local machine.
  2. Make a code change, and push to remote.
  3. Check your application’s deployments on Argonaut dashboard: ApplicationsBattleshipRun History from the top bar.
  4. You’ll see an ongoing deployment against your commit ID.
  5. Once the deployment is complete, navigate to your service URL to test that your code change is live.

That’s it!

You just used Argonaut to successfully set up the automatic deployment of an example application on every code push. You can now connect your own app with Argonaut to automate its deployment.