List of supported clouds > Amazon EKS
This document describes details specific to using your existing Amazon EKS cloud with Juju.
See more: Amazon EKS
When using the Amazon EKS cloud with Juju, it is important to keep in mind that it is a (1) Kubernetes cloud and (2) not some other cloud.
See more: Cloud differences in Juju
As the differences related to (1) are already documented generically in our Tutorial, How-to guides, and Reference docs, here we record just those that follow from (2).
| Juju points of variation | Notes for the Amazon EKS cloud |
|---|---|
| setup (chronological order): | |
| CLOUD | |
| requirements: | – |
| definition: | Cf. kubeconfig file.  Starting with Juju 3.0, because of a bug caused by the fact that the juju client snap is strictly confined but the EKS cloud CLI snap is not, you must run the add-k8s command with the ‘raw’ client. See note in How to add a Kubernetes cloud. |
| - name: | user-defined |
| - type: | k8s |
| - authentication types: | [oauth2, clientcertificate, userpass] |
| - regions: | [TO BE ADDED] |
| - cloud-specific model configuration keys: | operator-storage (string) Sets the storage class used to provision operator storage. workload-storage (string) Sets the preferred storage class used to provision the workload storage. |
| CREDENTIAL | |
| definition: | Cf. kubeconfig file. |
| CONTROLLER | |
| notes on bootstrap: | – |
| other (alphabetical order:) | |
| CONSTRAINT | Not applicable. |
| PLACEMENT DIRECTIVE | |
<machine> |
TBA |
subnet=... |
 |
system-id=... |
|
zone=... |
TBA |
| MACHINE | Starting with Juju 3.1, only IMDSv2 instances are supported. > See more: [Amazon ` |
| RESOURCE (cloud) Consistent naming, tagging, and the ability to add user-controlled tags to created instances. |