As a builder in cloud, you might feel confused about which resources cost mostly in your account.
In AWS, you can quickly find out which services even functionality cost a lot via AWS Billing or AWS Cost Explorer. However sometimes it sucks on finding out which functions cost mostly if you have hundreds of Lambda …
Though you're administrator of your AWS account, you probably see below warnings when viewing your cluster in EKS console.
Your current user or role does not have access to Kubernetes objects on this EKS cluster.