Jobs using GitLab's AWS Docker Image are failing

Summary

(Summarize the bug encountered concisely) Jobs using GitLab's AWS Docker Image are failing with the following error:

aws: not found

Steps to reproduce

Basically, follow the steps and guidelines described here: https://docs.gitlab.com/ee/ci/cloud_deployment/

  1. Create a repository in GitLab
  2. Add AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env variables in CI/CD settings section of the repo
  3. Add a .gitlab-ci-yml file to that repo
  4. Add the following job to that gitlab-ci.yml file:
test-aws:
    image: registry.gitlab.com/gitlab-org/cloud-deploy:latest
    script:
      - aws s3 ls

Example Project

https://gitlab.com/mauricio.quiroga/gitlab-aws-docker-image-bug

What is the current bug behavior?

The job fails with the following message:

/bin/sh: eval: line 96: aws: not found

ERROR: Job failed: exit code 127

What is the expected correct behavior?

The job should succed and execute the specified commands Job succeded

Relevant logs and/or screenshots

 Running with gitlab-runner 12.7.1 (003fe500)
   on docker-auto-scale 0277ea0f
Using Docker executor with image registry.gitlab.com/gitlab-org/cloud-deploy:latest ...
00:20
 Authenticating with credentials from job payload (GitLab Registry)
 Pulling docker image registry.gitlab.com/gitlab-org/cloud-deploy:latest ...
 Using docker image sha256:a4fcb867dfdc1b0bafc8b6faf605f0d59775c0e16b8e63365e2656b53feb28f1 for registry.gitlab.com/gitlab-org/cloud-deploy:latest ...
Running on runner-0277ea0f-project-16915506-concurrent-0 via runner-0277ea0f-srm-1581710384-cf445603...
00:04
$ eval "$CI_PRE_CLONE_SCRIPT"
00:01
 Fetching changes with git depth set to 50...
 Initialized empty Git repository in /builds/mauricio.quiroga/gitlab-aws-docker-image-bug/.git/
 Created fresh repository.
 From https://gitlab.com/mauricio.quiroga/gitlab-aws-docker-image-bug
  * [new ref]         refs/pipelines/118060861 -> refs/pipelines/118060861
  * [new branch]      master                   -> origin/master
 Checking out aa45395c as master...
 Skipping Git submodules setup
Authenticating with credentials from job payload (GitLab Registry)
00:02
 $ aws s3 ls
 /bin/sh: eval: line 88: aws: not found
 ERROR: Job failed: exit code 127

Output of checks

This bug happens on GitLab.com

Edited by Mauricio Quiroga