If you've installed the Codefresh runner on [EKS](https://aws.amazon.com/eks/) or any other custom cluster (e.g. with kops)in Amazon you need to configure it properly to work with EBSvolumesin order to gain [caching]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipeline-caching/).

> This section assumes you already installedtheRunner with default options:`codefresh runner init`

**Prerequesits**

`dind-volume-provisioner` deployment should have permissions to create/attach/detach/delete/get ebs volumes.

There are 3 options:

* running`dind-volume-provisioniner` pod on the node (node-group) with iam role

* k8s secret with [aws credentials format](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html) mounted to~/.aws/credentials (or`AWS_ACCESS_KEY_ID` and`AWS_SECRET_ACCESS_KEY` env vars passed) to the`dind-volume-provisioniner` pod

* using [Aws Identityfor Service Account](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html) iam role assigned to`volume-provisioner-runner` service account

Minimal policyfor`dind-volume-provisioner`:

Create Storage Classfor EBS volumes:

>Choose**one** of the Availability Zones you want to be usedfor your pipeline builds. Multi AZ configuration is not supported.

**Storage Class (gp2)**

**Storage Class (gp3)**

Apply storage class manifest:

Changeyour[runtime environment]({{site.baseurl}}/docs/administration/codefresh-runner/#full-runtime-environment-specification) configuration:

The same AZ you selected before should be usedin nodeSelector inside Runtime Configuration:

Choose the runtime you have just added and get its yaml representation:

Under`dockerDaemonScheduler.cluster` block add thenodeSelector`topology.kubernetes.io/zone:<your_az_here>`. It should be at the same level as`clusterProvider`and`namespace`. Also, the`pvcs.dind` block should be modified to use the Storage Class you created above (`dind-ebs`).

creationTime:'2019/12/11 11:30:00'

reuseVolumeSortOrder:'pipeline_id,trigger'

Update your runtime environment with the [patch command](https://codefresh-io.github.io/cli/operate-on-resources/patch/):

If necessary, delete all existing PV and PVC objects left from defaultlocal provisioner:

For an explanation of all other optionsrun`codefresh runner init --help` ([global parameter table](#customizing-the-wizard-installation)).

At this point the quick start wizard will start the installation.

creationTime:'2020/06/17 09:47:24'

description:'Runtime environment configure to cluster: my-aws-runner and namespace: cf'

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

Apply changes.

Step 1 - Make sure the OIDC provider is connected to the cluster

Step 2 - Create IAM role and policy as explainedin [https://docs.aws.amazon.com/eks/latest/userguide/create-service-account-iam-policy-and-role.html](https://docs.aws.amazon.com/eks/latest/userguide/create-service-account-iam-policy-and-role.html)

Step 3 - Annotate the`codefresh-engine` Kubernetes Service Accountin the namespace where the Codefresh Runner is installed with the proper IAM role.

Step 4 - Using the AWS assumed role identity

*Step 1* - Follow the installation instructions of the previous section

*Step 2* - Run`kubectl edit deployment runner -n codefresh-runtime` and add the proxy variables like this

*Step 3* - Add the following variables to your runtime.yaml, both under the`runtimeScheduler:` and under`dockerDaemonScheduler:` blocks inside the`envVars:` section

*Step 4* - Add`.firebaseio.com` to the allowed-sites of the proxy server

*Step 5* - Exec into the`dind` pod and run`ifconfig`