AWS Amazon EKS Error Codes

You don't have permissions to perform the requested operation. The IAM principal making the request must have at least one IAM permissions policy attached that grants the required permissions. For more information, see Access management in the IAM User Guide.

This exception is thrown if the request contains a semantic error. The precise meaning will depend on the API, and will be documented in the error message.

These errors are usually caused by a client action. Actions can include using an action or resource on behalf of an IAM principal that doesn't have permissions to use the action or resource or specifying an identifier that is not valid.

The specified parameter is invalid. Review the available parameters for the API request.

The request is invalid given the state of the cluster. Check the state of the cluster and the associated operations.

Amazon EKS detected upgrade readiness issues. Call the ListInsights API to view detected upgrade blocking issues. Pass the force flag when updating to override upgrade readiness errors.

A service resource associated with the request could not be found. Clients should not retry such requests.

The specified resource is in use.

You have encountered a service limit on the specified resource.

The specified resource could not be found. You can view your available clusters with ListClusters. You can view your available managed node groups with ListNodegroups. Amazon EKS clusters and node groups are Amazon Web Services Region specific.

Required resources (such as service-linked roles) were created and are still propagating. Retry later.

These errors are usually caused by a server-side issue.

The service is unavailable. Back off and retry the operation.

The request or operation couldn't be performed because a service is throttling requests.

At least one of your specified cluster subnets is in an Availability Zone that does not support Amazon EKS. The exception output specifies the supported Availability Zones for your account, from which you can choose subnets for your cluster.