The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Bitbucket pipelines terraform provisioning EKS failing

vgautam
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 22, 2024

I am trying to run terraform plan from bitbucket pipelines. I have mapped the necessary rolearns to EKS. It works from my local but gives this error:

Has Anyone done this workflow:
Terraform to provision EKS in a separate AWS account from pipeline using OIDC


│ Error: Kubernetes cluster unreachable: Get "https://XXXXXXXXXXX.gr7.us-east-1.eks.amazonaws.com/version": getting credentials: exec: executable aws not found
It looks like you are trying to use a client-go credential plugin that is not installed.
To learn more about this feature, consult the documentation available at:
https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 24, 2024

Hi @vgautam and welcome to the community!

The output you shared here includes the following error:

executable aws not found

Is this the output of an AWS CLI command?

Pipelines builds that run on Atlassian's infrastructure use Docker containers. For every step of your build, a Docker container starts (the build container) using the image you have specified in your bitbucket-pipelines.yml file. Any tools you use in that step's script need to be preinstalled in the Docker image you use as a build container or (if they are not) you need to install them during the build by adding the necessary commands in the yml file's script.

If it is indeed the AWS CLI that is missing from your build, you can either use a different Docker image as a build container, one that has AWS CLI preinstalled, or you can install it during the build. You can find details here:

The instructions for Linux are relevant in this case and you don't need to use sudo as the build runs with root user.

Kind regards,
Theodora

DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events