cox-automotive / aws-ebcli Goto Github PK

If you're using eb ssh it won't work as SSH isn't included with the image. Can be fixed by adding openssh to the list of packages to be installed in the Dockerfile.

docker run -i -e AWS_ACCESS_KEY_ID=${AWS_ACCESS_KEY_ID} -e AWS_SECRET_ACCESS_KEY=${AWS_SECRET_ACCESS_KEY} -w /work -v $PWD:/work coxauto/aws-ebcli /bin/bash -c "${CMD}"

Throws:
ERROR: InvalidProfileError - The config profile (eb-cli) could not be found

why needs AWS_SESSION_TOKEN?

secret key and key id are enough.

Hi,
I try to deploy 2 different projects to 2 different AWS environments by 2 different AWS credentials,
I do it by passing "-e" argument,
It seems that it's cached, and in the second project, it tries to push it to the same AWS environment,
Would you please help me if I can try any other approach or somehow overwrite the credentials,
Thanks,
Sina

With Gitlab Runner CI/CD throws eb command not found

.gitlab-ci.yml

... // other stages and configs, then:
deploy:
  stage: deploy
  image: coxauto/aws-ebcli
  dependencies:
    - build
  script:
    - mkdir -p ~/.aws
    - touch ~/.aws/config
    - chmod 600 ~/.aws/config
    - echo "[profile eb-cli]" >> ~/.aws/config
    - echo "aws_access_key_id=${AWS_ACCESS_KEY_ID}" >> ~/.aws/config
    - echo "aws_secret_access_key=${AWS_SECRET_ACCESS_KEY}" >> ~/.aws/config
    - git checkout $CI_COMMIT_REF_NAME
    - git fetch --all
    - git pull
    - eb labs cleanup-versions --force
    - eb deploy
    - echo "DEPLOYMENT OF $CI_COMMIT_REF_NAME IS COMPLETE"
  environment:
    name: $CI_COMMIT_REF_NAME
  only:
    - master

Hello,

It seems that after the latest docker image update (3 days ago), eb deploy fails

Anyone is having the same issue here?