big-angle-30002
01/12/2024, 2:59 PM"command": "aws",
"args": [
"eks",
"get-token",
"--cluster-name",
cluster.name,
"--region",
region,
"--output",
"json"
],
"env": [
{
"name": "AWS_ACCESS_KEY_ID",
"value": "XXXXXXX"
},
{
"name": "AWS_SECRET_ACCESS_KEY",
"value": "XXXXXXXXX"
}
]
Instead of using the aws keys I want to use a role
"args": [
"eks",
"get-token",
"--cluster-name",
cluster.name,
"--region",
region,
"--role",
role_arn,
"--output",
"json"
],
but an error occurs, I emphasize that I have given the role administrative privileges for these tests
[PULUMI LOG] error: configured Kubernetes cluster is unreachable: unable to load schema information from the API server: Get "https://EB5CF32E90F564339E329B6399F46E53.gr7.us-east-1.eks.amazonaws.com/openapi/v2?timeout=32s": getting credentials: exec: executable aws failed with exit code 252
I don't quite understand how authentication with a role account should be in these casesNo matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.
Powered by