resourcedetection/eks instructions are unclear

[jakeforge]

Component(s)

processor/resourcedetection

Describe the issue you're reporting

The documentation says

Note: The kubernetes cluster name is only available when running on EC2 instances, and requires permission to run the EC2:DescribeInstances action

However, it is unclear what exactly a user needs to do in order to grant this permission to the resource detector. The same issue exists for other parts of the aws related resourcedetection components.

[github-actions]

Pinging code owners:

• processor/resourcedetection: @Aneurysm9 @dashpole

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[crobert-1]

Hello @jakeforge, the permissions are inherited from the user deploying the collector, I believe. So whichever permissions you have in your AWS environment, the collector (and this processor) would have as well.

In my own testing, I was using kubectl to set context to the EKS cluster, and then running kubectl apply to deploy the collector. kubectl uses kubeconfig files to list valid contexts, an example of which would be your EKS cluster. In my case, I setup a context for the EKS cluster, and included the role for my user in the args list of the execconfig. This included role was an IAM role with the permission required.

I don't have a lot of AWS experience though, so others may be able to share more information here.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• processor/resourcedetection: @Aneurysm9 @dashpole

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.