diff --git a/README.md b/README.md
index 569aeb2..1c787a8 100644
--- a/README.md
+++ b/README.md
@@ -52,6 +52,7 @@ terraform apply --auto-approve
 
 ## Connect to and verify the cluster
 ```
+# Make sure to use --region if the cluster is deployed in non-default region and --profile if the cluster is deployed in a non-default AWS account
 aws eks update-kubeconfig --name [eks_cluster_name]
 kubectl get nodes
 kubectl get pods -A
@@ -79,4 +80,4 @@ terraform output
 * Prior to `terraform destroy`, infrastructure resources created by pods/controllers and may not be visible to Terraform need to be deleted, e.g., nginx-ingress's NLB. A good practice is to always begin by running `helmfile destroy`.
 * If Karpenter is used for node provisioning, ensure the nodes created by it are not lingering around before running `terraform destroy`. 
 * Due to [known issues](https://github.com/kubernetes-sigs/aws-ebs-csi-driver/issues/1507), the aws-ebs-csi-driver retains EBS volumes during cluster destruction. These volumes should be manually deleted if no longer needed.
-  
\ No newline at end of file
+