<h3>Issue 1</h3>
<p>The question says it all. I can't find the EKS cluster which was created by kops in the AWS console. I can, however, interact with it as the IAM user (<code>kops-user</code>) which I used to launch the cluster, using <code>kops</code> and <code>kubectl</code> commands. The following policies are directly attached to <code>kops-user</code>:</p>
<pre><code>AmazonEC2FullAccess
AmazonRoute53FullAccess
AmazonS3FullAccess
IAMFullAccess
AmazonVPCFullAccess
</code></pre>
<p>Here was the command I used to launch the cluster:</p>
<pre><code>kops create cluster \
  --cloud aws \
  --vpc ${VPC_ID} \
  --subnets ${SUBNET1_ID},${SUBNET2_ID},${SUBNET3_ID} \
  --zones ap-southeast-1a,ap-southeast-1b,ap-southeast-1c \
  --networking calico \
  --master-size t3.medium --master-count 1 \
  --node-size t3.medium --node-count 1 \
  --dns-zone dev.mgamer.io \
  ${CLUSTER_NAME}
</code></pre>
<p>The Kubernetes cluster itself is working fine.</p>
<p>Why can't the <code>root</code> user see the cluster in the AWS console? How can this be fixed?</p>
<h3>Issue 2</h3>
<p>The other issue that I can't figure out is that, why does my user, <code>kops-user</code>, who already has all those powerful policies attached to it, is still unable to run <code>aws eks list-clusters</code>?</p>
<pre><code>lester:hello lester$ aws sts get-caller-identity
Account: '459567475699'
Arn: arn:aws:iam::459567475699:user/kops-user
UserId: SGLJI8490SG9D3IGLSK
lester:hello lester$ aws eks list-clusters
clusters: []
lester:hello-mgamer lester$
</code></pre>
<p>What other permission does it need?</p>
<p>I even tried adding a custom policy and attached it to the <code>kops-user</code>, with no luck:</p>
<pre><code>{
    &quot;Version&quot;: &quot;2012-10-17&quot;,
    &quot;Statement&quot;: [
        {
            &quot;Sid&quot;: &quot;VisualEditor0&quot;,
            &quot;Effect&quot;: &quot;Allow&quot;,
            &quot;Action&quot;: &quot;eks:*&quot;,
            &quot;Resource&quot;: &quot;*&quot;
        }
    ]
}
</code></pre>
<p>Thanks a lot in advance.</p>

<p><strong>Issue 1</strong>:</p>
<ul>
<li>The Kubernetes Cluster that kops creates is with EC2 instances, not with EKS.</li>
</ul>
<p><strong>Issue 2</strong></p>
<ul>
<li>Is the same answer from issue 1, it's not listing any EKS clusters because kops doesn't create one.</li>
</ul>
