MissingServiceIdError - The model being used for the service elasticbeanstalk is missing the serviceId metadata property, which is required.

Description

When installing awsebcli besides awscli the following error is shown on eb init (and other eb-commands):

# eb init
ERROR: MissingServiceIdError - The model being used for the service elasticbeanstalk is missing the serviceId metadata property, which is required.

# pip freeze
awscli==1.19.4
awsebcli==3.14.4
blessed==1.17.12
botocore==1.20.4
cached-property==1.5.2
cement==2.8.2
colorama==0.3.9
docker==3.7.3
docker-compose==1.21.2
docker-pycreds==0.4.0
dockerpty==0.4.1
docopt==0.6.2
docutils==0.15.2
jmespath==0.10.0
jsonschema==2.6.0
pathspec==0.5.5
pyasn1==0.4.8
python-dateutil==2.8.1
PyYAML==3.13
requests==2.15.1
rsa==4.5
s3transfer==0.3.4
semantic-version==2.5.0
six==1.11.0
tabulate==0.7.5
termcolor==1.1.0
texttable==0.9.1
urllib3==1.26.3
wcwidth==0.2.5
websocket-client==0.57.0

Steps to reproduce

Have a docker with

FROM python:3.7-alpine3.12
ENV PATH "$PATH:/root/.local/bin"
RUN pip install --upgrade --user awscli awsebcli

Run eb init

Observed result

See description

Expected result

Being able to use both together.

Additional environment details (Ex: Windows, Mac, Amazon Linux etc)

See above

[Palakpatel67]

We’ve updated botocore version for EB CLI. this should be fixed in awsebcli version 3.19.4

[LeszekBlazewski]

The problem still exists, It occurs when installing both aws cli and eb cli, probably because of the botocore dependency issue. You can check this simple example:

FROM python:3.9-slim-buster

RUN apt-get update -y && apt-get install -y \
  jq \
  zip \
  git

RUN pip install --no-cache-dir --upgrade awsebcli awscli ec2instanceconnectcli

When building the docker image you can see that version 3.14.3 is being installed not the latest one which is 3.19.3. When trying to manually install the 3.19.3 version, error is thrown that there will be a compability issue between botocore versions.

Successfully installed PyYAML-3.13 awscli-1.19.8 awsebcli-3.14.4

Then authorize yourself and use correct aws profile within container or mount host aws credential files and try to issue for example the eb init --verbose command. Bascially the commands will fail with the error provided already above.

It would be nice if eb cli would also support the more recent botocore version as stated in this bug report https://github.com/boto/botocore/issues/2288 manually installing and pinnig botocore version in dockerfile fixes the issue so this adjustmend must be made in my example to make it work

RUN pip install --no-cache-dir --upgrade awsebcli awscli ec2instanceconnectcli botocore==1.19.63

Best regards,