|
45 | 45 | {"shape":"ServerException"},
|
46 | 46 | {"shape":"ResourceInUseException"},
|
47 | 47 | {"shape":"ResourceNotFoundException"},
|
48 |
| - {"shape":"InvalidRequestException"} |
| 48 | + {"shape":"InvalidRequestException"}, |
| 49 | + {"shape":"ThrottlingException"} |
49 | 50 | ],
|
50 | 51 | "documentation":"<p>Associates an encryption configuration to an existing cluster.</p> <p>Use this API to enable encryption on existing clusters that don't already have encryption enabled. This allows you to implement a defense-in-depth security strategy without migrating applications to new Amazon EKS clusters.</p>"
|
51 | 52 | },
|
|
63 | 64 | {"shape":"ServerException"},
|
64 | 65 | {"shape":"ResourceInUseException"},
|
65 | 66 | {"shape":"ResourceNotFoundException"},
|
66 |
| - {"shape":"InvalidRequestException"} |
| 67 | + {"shape":"InvalidRequestException"}, |
| 68 | + {"shape":"ThrottlingException"} |
67 | 69 | ],
|
68 | 70 | "documentation":"<p>Associates an identity provider configuration to a cluster.</p> <p>If you want to authenticate identities using an identity provider, you can create an identity provider configuration and associate it to your cluster. After configuring authentication to your cluster you can create Kubernetes <code>Role</code> and <code>ClusterRole</code> objects, assign permissions to them, and then bind them to the identities using Kubernetes <code>RoleBinding</code> and <code>ClusterRoleBinding</code> objects. For more information see <a href=\"https://kubernetes.io/docs/reference/access-authn-authz/rbac/\">Using RBAC Authorization</a> in the Kubernetes documentation.</p>"
|
69 | 71 | },
|
|
563 | 565 | {"shape":"ServerException"},
|
564 | 566 | {"shape":"ResourceInUseException"},
|
565 | 567 | {"shape":"ResourceNotFoundException"},
|
566 |
| - {"shape":"InvalidRequestException"} |
| 568 | + {"shape":"InvalidRequestException"}, |
| 569 | + {"shape":"ThrottlingException"} |
567 | 570 | ],
|
568 | 571 | "documentation":"<p>Disassociates an identity provider configuration from a cluster.</p> <p>If you disassociate an identity provider from your cluster, users included in the provider can no longer access the cluster. However, you can still access the cluster with IAM principals.</p>"
|
569 | 572 | },
|
|
868 | 871 | {"shape":"ServerException"},
|
869 | 872 | {"shape":"ResourceInUseException"},
|
870 | 873 | {"shape":"ResourceNotFoundException"},
|
871 |
| - {"shape":"InvalidRequestException"} |
| 874 | + {"shape":"InvalidRequestException"}, |
| 875 | + {"shape":"ThrottlingException"} |
872 | 876 | ],
|
873 | 877 | "documentation":"<p>Updates an Amazon EKS cluster configuration. Your cluster continues to function during the update. The response output includes an update ID that you can use to track the status of your cluster update with <code>DescribeUpdate</code>\"/>.</p> <p>You can use this API operation to enable or disable exporting the Kubernetes control plane logs for your cluster to CloudWatch Logs. By default, cluster control plane logs aren't exported to CloudWatch Logs. For more information, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/control-plane-logs.html\">Amazon EKS Cluster control plane logs</a> in the <i> <i>Amazon EKS User Guide</i> </i>.</p> <note> <p>CloudWatch Logs ingestion, archive storage, and data scanning rates apply to exported control plane logs. For more information, see <a href=\"http://aws.amazon.com/cloudwatch/pricing/\">CloudWatch Pricing</a>.</p> </note> <p>You can also use this API operation to enable or disable public and private access to your cluster's Kubernetes API server endpoint. By default, public access is enabled, and private access is disabled. For more information, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html\">Amazon EKS cluster endpoint access control</a> in the <i> <i>Amazon EKS User Guide</i> </i>.</p> <p>You can also use this API operation to choose different subnets and security groups for the cluster. You must specify at least two subnets that are in different Availability Zones. You can't change which VPC the subnets are from, the subnets must be in the same VPC as the subnets that the cluster was created with. For more information about the VPC requirements, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/network_reqs.html\">https://docs.aws.amazon.com/eks/latest/userguide/network_reqs.html</a> in the <i> <i>Amazon EKS User Guide</i> </i>.</p> <p>You can also use this API operation to enable or disable ARC zonal shift. If zonal shift is enabled, Amazon Web Services configures zonal autoshift for the cluster.</p> <p>Cluster updates are asynchronous, and they should finish within a few minutes. During an update, the cluster status moves to <code>UPDATING</code> (this status transition is eventually consistent). When the update is complete (either <code>Failed</code> or <code>Successful</code>), the cluster status moves to <code>Active</code>.</p>"
|
874 | 878 | },
|
|
886 | 890 | {"shape":"ServerException"},
|
887 | 891 | {"shape":"ResourceInUseException"},
|
888 | 892 | {"shape":"ResourceNotFoundException"},
|
889 |
| - {"shape":"InvalidRequestException"} |
| 893 | + {"shape":"InvalidRequestException"}, |
| 894 | + {"shape":"ThrottlingException"}, |
| 895 | + {"shape":"InvalidStateException"} |
890 | 896 | ],
|
891 | 897 | "documentation":"<p>Updates an Amazon EKS cluster to the specified Kubernetes version. Your cluster continues to function during the update. The response output includes an update ID that you can use to track the status of your cluster update with the <a href=\"https://docs.aws.amazon.com/eks/latest/APIReference/API_DescribeUpdate.html\"> <code>DescribeUpdate</code> </a> API operation.</p> <p>Cluster updates are asynchronous, and they should finish within a few minutes. During an update, the cluster status moves to <code>UPDATING</code> (this status transition is eventually consistent). When the update is complete (either <code>Failed</code> or <code>Successful</code>), the cluster status moves to <code>Active</code>.</p> <p>If your cluster has managed node groups attached to it, all of your node groups' Kubernetes versions must match the cluster's Kubernetes version in order to update the cluster to a new Kubernetes version.</p>"
|
892 | 898 | },
|
|
3807 | 3813 | "error":{"httpStatusCode":400},
|
3808 | 3814 | "exception":true
|
3809 | 3815 | },
|
| 3816 | + "InvalidStateException":{ |
| 3817 | + "type":"structure", |
| 3818 | + "members":{ |
| 3819 | + "clusterName":{ |
| 3820 | + "shape":"String", |
| 3821 | + "documentation":"<p>The Amazon EKS cluster associated with the exception.</p>" |
| 3822 | + }, |
| 3823 | + "message":{"shape":"String"} |
| 3824 | + }, |
| 3825 | + "documentation":"<p>Amazon EKS detected upgrade readiness issues. Call the <a href=\"https://docs.aws.amazon.com/eks/latest/APIReference/API_ListInsights.html\"> <code>ListInsights</code> </a> API to view detected upgrade blocking issues. Pass the <a href=\"https://docs.aws.amazon.com/eks/latest/APIReference/API_UpdateClusterVersion.html#API_UpdateClusterVersion_RequestBody\"> <code>force</code> </a> flag when updating to override upgrade readiness errors.</p>", |
| 3826 | + "error":{"httpStatusCode":400}, |
| 3827 | + "exception":true |
| 3828 | + }, |
3810 | 3829 | "IpFamily":{
|
3811 | 3830 | "type":"string",
|
3812 | 3831 | "enum":[
|
|
5391 | 5410 | "PREFER_NO_SCHEDULE"
|
5392 | 5411 | ]
|
5393 | 5412 | },
|
| 5413 | + "ThrottlingException":{ |
| 5414 | + "type":"structure", |
| 5415 | + "members":{ |
| 5416 | + "clusterName":{ |
| 5417 | + "shape":"String", |
| 5418 | + "documentation":"<p>The Amazon EKS cluster associated with the exception.</p>" |
| 5419 | + }, |
| 5420 | + "message":{"shape":"String"} |
| 5421 | + }, |
| 5422 | + "documentation":"<p>The request or operation couldn't be performed because a service is throttling requests.</p>", |
| 5423 | + "error":{"httpStatusCode":429}, |
| 5424 | + "exception":true |
| 5425 | + }, |
5394 | 5426 | "Timestamp":{"type":"timestamp"},
|
5395 | 5427 | "UnsupportedAvailabilityZoneException":{
|
5396 | 5428 | "type":"structure",
|
|
5647 | 5679 | "shape":"String",
|
5648 | 5680 | "documentation":"<p>A unique, case-sensitive identifier that you provide to ensure the idempotency of the request.</p>",
|
5649 | 5681 | "idempotencyToken":true
|
| 5682 | + }, |
| 5683 | + "force":{ |
| 5684 | + "shape":"Boolean", |
| 5685 | + "documentation":"<p>Set this value to <code>true</code> to override upgrade-blocking readiness checks when updating a cluster.</p>" |
5650 | 5686 | }
|
5651 | 5687 | }
|
5652 | 5688 | },
|
|
0 commit comments