AWS eks: Documentation typo fixes and terminology consistency updates
Summary
Corrected minor typos, standardized terminology (e.g., 'Id' to 'ID', 'Arn' to 'ARN'), and improved punctuation.
Security assessment
Changes involve non-security grammatical improvements and capitalization consistency (e.g., 'ARN' instead of 'Arn'). No security vulnerabilities, configurations, or best practices are addressed.
Evidence
+KMS_KEY_DISABLED | The AWS KMS Key associated with your cluster is disabled. Re-enable the key to recover your cluster. | The KMS Key ARN | Yes
Diff
diff --git a/eks/latest/userguide/troubleshooting.md b/eks/latest/userguide/troubleshooting.md index ae89aa06d..7c9db9e72 100644 --- a//eks/latest/userguide/troubleshooting.md +++ b//eks/latest/userguide/troubleshooting.md @@ -350 +350 @@ The diagnostic information is collected and stored at: -To retrieve log bundle for Bottlerocket nodes, please refer to [Bottlerocket Log](https://github.com/bottlerocket-os/bottlerocket?tab=readme-ov-file#logs) for more details. +To retrieve the log bundle for Bottlerocket nodes, please refer to [Bottlerocket Logs](https://github.com/bottlerocket-os/bottlerocket?tab=readme-ov-file#logs) for more details. @@ -559 +559 @@ To access the health of your cluster in the Amazon EKS console, look for a table -You will get increased visibility into the health of your Amazon EKS cluster, quickly diagnose and fix any issues, without needing to spend time debugging or opening AWS support cases. For example: you accidentally deleted a subnet for the Amazon EKS cluster, Amazon EKS won’t be able to create cross account network interfaces and Kubernetes AWS CLI commands such as `kubectl` exec or `kubectl` logs. These will fail with the error: `Error from server: error dialing backend: remote error: tls: internal error.` Now you will see an Amazon EKS health issue that says: `subnet-da60e280 was deleted: could not create network interface`. +You will get increased visibility into the health of your Amazon EKS cluster, quickly diagnose and fix any issues, without needing to spend time debugging or opening AWS support cases. For example: you accidentally deleted a subnet for the Amazon EKS cluster, Amazon EKS won’t be able to create cross-account network interfaces and Kubernetes AWS CLI commands such as `kubectl` exec or `kubectl` logs. These will fail with the error: `Error from server: error dialing backend: remote error: tls: internal error.` Now you will see an Amazon EKS health issue that says: `subnet-da60e280 was deleted: could not create network interface`. @@ -590,4 +590,4 @@ Code | Message | ResourceIds | Cluster Recoverable? -SUBNET_NOT_FOUND | We couldn’t find one or more subnets currently associated with your cluster. Call Amazon EKS update-cluster-config API to update subnets. | Subnet Ids | Yes -SECURITY_GROUP_NOT_FOUND | We couldn’t find one or more security groups currently associated with your cluster. Call Amazon EKS update-cluster-config API to update security groups | Security group Ids | Yes -IP_NOT_AVAILABLE | One or more of the subnets associated with your cluster does not have enough available IP addresses for Amazon EKS to perform cluster management operations. Free up addresses in the subnet(s), or associate different subnets to your cluster using the Amazon EKS update-cluster-config API. | Subnet Ids | Yes -VPC_NOT_FOUND | We couldn’t find the VPC associated with your cluster. You must delete and recreate your cluster. | VPC id | No +SUBNET_NOT_FOUND | We couldn’t find one or more subnets currently associated with your cluster. Call Amazon EKS update-cluster-config API to update subnets. | Subnet IDs | Yes +SECURITY_GROUP_NOT_FOUND | We couldn’t find one or more security groups currently associated with your cluster. Call Amazon EKS update-cluster-config API to update security groups. | Security group IDs | Yes +IP_NOT_AVAILABLE | One or more of the subnets associated with your cluster does not have enough available IP addresses for Amazon EKS to perform cluster management operations. Free up addresses in the subnet(s), or associate different subnets to your cluster using the Amazon EKS update-cluster-config API. | Subnet IDs | Yes +VPC_NOT_FOUND | We couldn’t find the VPC associated with your cluster. You must delete and recreate your cluster. | VPC ID | No @@ -600 +600 @@ STS_REGIONAL_ENDPOINT_DISABLED | The STS regional endpoint is disabled. Enable -KMS_KEY_DISABLED | The AWS KMS Key associated with your cluster is disabled. Re-enable the key to recover your cluster. | The KMS Key Arn | Yes +KMS_KEY_DISABLED | The AWS KMS Key associated with your cluster is disabled. Re-enable the key to recover your cluster. | The KMS Key ARN | Yes @@ -602 +602 @@ KMS_KEY_NOT_FOUND | We couldn’t find the AWS KMS key associated with your clu -KMS_GRANT_REVOKED | Grants for the AWS KMS Key associated with your cluster are revoked. You must delete and recreate the cluster. | The KMS Key Arn | No +KMS_GRANT_REVOKED | Grants for the AWS KMS Key associated with your cluster are revoked. You must delete and recreate the cluster. | The KMS Key ARN | No