# Get Permanent Token When Accessing External Clusters You can quickly integrate an external cluster into cluster management using kubeconfig. To ensure the stability of the integration, it is recommended to use a long-lasting token (preferably a permanent token) in the kubeconfig. However, different cluster service providers, such as AWS EKS and GKE, have different methods for getting a permanent token, typically only providing tokens with a validity of 24 hours. !!! note For specific product operation interface reference: [Integrate Cluster](../user-guide/clusters/integrate-cluster.md) ## Create a ServiceAccount with Cluster Administrator Permissions To address the above issue, you can create a ServiceAccount with cluster administrator permissions and use the kubeconfig of this ServiceAccount to access the cluster. !!! warning When executing the following steps, ensure that you have configured the AWS or GCP CLI and have permissions to access the cluster, otherwise an error will occur. 1. Create the YAML configuration for the ServiceAccount and ClusterRoleBinding: ```bash cat >eks-admin-service-account.yaml <