Is there a way to avoid aws-iam-authenticator from using keys available as environment variables

[nishan...@appdynamics.com]

Is there a way to avoid aws-iam-authenticator from using keys available as environment variables and use either the profile defined in .kube/config or use role associated to the ec2 instance? 

for e.g. 

even if I use 

- name: test
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      command: aws-iam-authenticator
      args:
      - token
      - -i
      - eks-build
      env:
      - name: AWS_PROFILE
        value: ec2-role

since my env has some aws keys available aws-iam-authenticator tries to use those and not the profile associated in .kube/config. The goal here is to force the aws-iam-authenticator to use role associated to ec2 instance with or without defining 'env' in the .kube/config. Any suggestions will be appreciated.