**Step 3:** Get the YAML representation of the runtime you just added:

* Get a list of all available runtimes:

* Get a list of all available runtimes:

* Select the runtime you just added, and get its YAML representation:

* Select the runtime you just added, and get its YAML representation:

**Step 4:** Modify the YAML:

* In`dockerDaemonScheduler.cluster`, add`nodeSelector: topology.kubernetes.io/zone:<your_az_here>`.

> Make sure you define the same AZ you selectedfor Runtime Configuration.

* Modify`pvcs.dind` to use the Storage Class you created above (`dind-ebs`).

* In`dockerDaemonScheduler.cluster`, add`nodeSelector: topology.kubernetes.io/zone:<your_az_here>`.

> Make sure you define the same AZ you selectedfor Runtime Configuration.

* Modify`pvcs.dind` to use the Storage Class you created above (`dind-ebs`).

Here is an example of the`runtime.yaml` including the required updates:

Here is an example of the`runtime.yaml` including the required updates:

**How to**

1. Make sure target the correct cluster:

* Make sure target the correct cluster:

1. Install the Runner with additional options:

* Specify the zonein which to create your volumes,for example:`--set-value=Storage.AvailabilityZone=us-west-2a`.

* (Optional) To assign the volume-provisioner to a specific node,for example, a specific node group with an IAM role that can create EBS volumes,`--set-value Storage.VolumeProvisioner.NodeSelector=node-type=addons`.

* To use [encrypted EBS volumes](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html#EBSEncryption_key_mgmt){:target="\_blank"}, add the custom value`--set-value=Storage.Encrypted=true`.

* If you already have a key, add its ARN via`--set-value=Storage.KmsKeyId=<key id> value`. Otherwise a key is generated by AWS.

* Install the Runner with additional options:

* Specify the zonein which to create your volumes,for example:`--set-value=Storage.AvailabilityZone=us-west-2a`.

* (Optional) To assign the volume-provisioner to a specific node,for example, a specific node group with an IAM role that can create EBS volumes,`--set-value Storage.VolumeProvisioner.NodeSelector=node-type=addons`.

* To use [encrypted EBS volumes](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html#EBSEncryption_key_mgmt){:target="\_blank"}, add the custom value`--set-value=Storage.Encrypted=true`.

* If you already have a key, add its ARN via`--set-value=Storage.KmsKeyId=<key id> value`. Otherwise a key is generated by AWS.

Here is an example with _all_ the options configured:

Here is an example with _all_ the options configured:

For descriptions of the other options, run`codefresh runner init --help` ([global parameter table](#customizing-the-wizard-installation)).

{:start="3"}

1. When the Wizard completes the installation, modify the runtime environment of`my-aws-runner` to specify the necessary toleration, nodeSelector and disk size:

* When the Wizard completes the installation, modify the runtime environment of`my-aws-runner` to specify the necessary toleration, nodeSelector and disk size:

* Run:

* Modify the file`my-runtime.yml` as shown below:

{:start="4"}

1. Apply changes.

* Apply changes.