Elastic Beanstalk Deployment Error: "S3 client configured for “eu-west-2” but the bucket “elasticbeanstalk-eu-west-2-364597724349” is in “eu-west-2”"

Deployment
3

I cannot really say how I fixed it, because I archived the repo that was causing the error and then created a new one. And now it is working in the new one. The .travis.yml files:

Working / New Repo

deploy:
  - skip_cleanup: true
    provider: elasticbeanstalk
    access_key_id: "$ACCESSKEYID"
    secret_access_key: "$SECRETACCESSKEY"
    region: "eu-west-2"
    app: "kodular-auth"
    env: "auth-dev"
    bucket_name: "..."
    zip_file: ".elasticbeanstalk/ebdeploy.zip"
    on:
      branch: master

Not Working / Old Repo

deploy:
  - provider: elasticbeanstalk
    skip_cleanup: true
    access_key_id: 
      secure: "..."
    secret_access_key:
      secure: "..."
    region: "eu-west-2"  
    app: "kodular-auth"
    env: "master"
    bucket_name: "..."
    zip_file: "ebdeploy.sh"
    on:
      repo: Kodular/Kodular-Auth
      branch: master

Note that ... was removed to not expose it. You should change those ... to the literal values.

Maybe the error was been caused because of using the secure way in the acess keys. It’s the only difference I can find. Try using environment variables and passing them with $ACCESSKEYID.

1 Like