Hello

Im trying to complete the implementation course in the Gitlab PSE pathway.

I already did all the setup of the enviroment, configuring the necessary files, im at the step of Running a Toolkit (GET) Docker Container.

After positioning myself at the appropiate folder :

cd /gitlab-environment-toolkit/terraform/environments/3k

I can run terraform init

and it runs succesfully

terraforminit730×321 11 KB

but after running

terraform plan -out 3k.aws_ec2.tfplan

it gives me an error

errorterraform1298×202 9.41 KB

My main.tf looks like this

terraform {
required_providers {
aws = {
source = “hashicorp/aws”
}
}
}

Configure the AWS Provider

provider “aws” {
region = var.region
}

And i already set the enviroment variables on the linux instance

And running the command :

docker run -it
-v /home/ec2-user/gitlab-environment-toolkit/keys:/gitlab-environment-toolkit/keys
-v /home/ec2-user/gitlab-environment-toolkit/ansible/environments/3k:/gitlab-environment-toolkit/ansible/environments/3k
-v /home/ec2-user/gitlab-environment-toolkit/ansible/ansible.cfg:/gitlab-environment-toolkit/ansible/ansible.cfg
-v /home/ec2-user/gitlab-environment-toolkit/terraform/environments/3k:/gitlab-environment-toolkit/terraform/environments/3k
-e AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID
-e AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY
-e GITLAB_PASSWORD=$GITLAB_PASSWORD
registry.gitlab.com/gitlab-org/gitlab-environment-toolkit:latest

I pass the values to those variables and use them in the Docker image, but it gives me the error shown above.

I want to make sure that im using the correct keys from AWS, im using them from this screen :

keysaws779×434 14 KB

i heard that you could use them from here as well but i don’t have access :

alternawskeys1301×411 36.3 KB

Can anyone help me? after running terraform i only need to run the ansible scripts and would complete the workshop, im so close but can’t figure out the terraform error, any help would be greatly appreciated.

Thanks in advance.

Hi

The problem was indeed on the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY , AWS is very nitpicky about security, so we had to make some changes to policies and roles in order to make it work, it was a hassle but we managed to continue after that, thanks.