Generally, deploy from master or release candidate isn't any different from deploying the release in terms of the steps that need to be taken.

Note that distros built from release, release-candidate and nightly branches are placed on the https://repo.elastio.com server. Whereas distros built from development branches (master and feature branches) are stored on the https://repo.elastio.us server. You should update the download link according to your desired branch.

Deploy from master

Linux

1. Deploying the Elastio cli

sudo /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/elastio/elastio-stack/master/scripts/install-elastio.sh) $0 $1" -- -b master

-b here stands for branch

2. Deploy / Update the Red Stack (if needed)

Run aws configure to connect the AWs account, where the Red Stack will be deployed, if outside the AWS account.

Set the environment variable to pull artifacts from master:

export ELASTIO_ARTIFACTS_SOURCE=ci:master

Then run

elastio stack deploy --tenant-name dev.staging.elastio.us

--tenant-name for internal use is dev.staging.elastio.us.

3. Create a vault

elastio vault deploy <example_name>

Please note: vault deploy command will require ECS service linked role in the account. It’s created per account and can be already present. If not you need to run

aws iam create-service-linked-role --aws-service-name ecs.amazonaws.com

Windows

1. Deploying the Elastio cli and drivers

Set-ExecutionPolicy Bypass -Scope Process -Force; iex ((New-Object System.Net.WebClient).DownloadString('https://repo.elastio.us/master/cli/install.ps1'))

Set-ExecutionPolicy Bypass -Scope Process -Force; iex ((New-Object System.Net.WebClient).DownloadString('https://repo.elastio.us/master/drivers/install.ps1'))

2. Deploy / Update the Red Stack (if needed)

Run aws configure to connect the AWs account, where the Red Stack will be deployed, if outside the AWS account.

Set the environment variable to pull artifacts from master:

$env:ELASTIO_ARTIFACTS_SOURCE="ci:master"

Then run

elastio stack deploy --tenant-name dev.staging.elastio.us

--tenant-name for internal use is dev.staging.elastio.us or your own.

3. Create a vault

elastio vault deploy <example_name>

Please note: vault deploy command will require ECS service linked role in the account. It’s created per account and can be already present. If not you need to run

aws iam create-service-linked-role --aws-service-name ecs.amazonaws.com

Deploy from release-candidate

Linux

1. Deploying the Elastio cli

sudo /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/elastio/elastio-stack/master/scripts/install-elastio.sh) $0 $1" -- -b release-candidate

-b here stands for branch

2. Deploy / Update the Red Stack (if needed)

Run aws configure to connect the AWs account, where the Red Stack will be deployed, if outside the AWS account.

Set the environment variable to pull artifacts from master:

export ELASTIO_ARTIFACTS_SOURCE=release-candidate

Then run

elastio stack deploy --tenant-name dev.staging.elastio.us

--tenant-name for internal use is dev.staging.elastio.us.

3. Create a vault

elastio vault deploy <example_name>

Please note: vault deploy command will require ECS service linked role in the account. It’s created per account and can be already present. If not you need to run

aws iam create-service-linked-role --aws-service-name ecs.amazonaws.com

Windows

1. Deploying the Elastio cli and drivers

Set-ExecutionPolicy Bypass -Scope Process -Force; iex ((New-Object System.Net.WebClient).DownloadString('https://repo.elastio.com/release-candidate/cli/install.ps1'))

Set-ExecutionPolicy Bypass -Scope Process -Force; iex ((New-Object System.Net.WebClient).DownloadString('https://repo.elastio.com/release-candidate/drivers/install.ps1'))

2. Deploy / Update the Red Stack (if needed)

Run aws configure to connect the AWs account, where the Red Stack will be deployed, if outside the AWS account.

Set the environment variable to pull artifacts from master:

$env:ELASTIO_ARTIFACTS_SOURCE="release-candidate"

Then run

elastio stack deploy --tenant-name dev.staging.elastio.us

--tenant-name for internal use is dev.staging.elastio.us or your own.

3. Create a vault

elastio vault deploy <example_name>

Please note: vault deploy command will require ECS service linked role in the account. It’s created per account and can be already present. If not you need to run

aws iam create-service-linked-role --aws-service-name ecs.amazonaws.com