How to use AWS CLI with Elastic Beanstalk?

Question

In the documentation it states that the EB CLI is replaced by AWS CLI but all of the documentation is still talking about EB CLI.

I have created an application in Elastic Beanstalk console and now I'm ready to start developing. I have all the tools installed on Ubuntu and I've already tested it locally. Now I want to deploy it to Elastic Beanstalk. How do I do this with AWS CLI?

Have you gone through this? docs.aws.amazon.com/cli/latest/reference/elasticbeanstalk/… — Shibashis
– Shibashis, Commented Jun 5, 2016 at 17:52
After you install aws cli, you will have to execute commands using aws cli elasticbeanstalk check-dns-availability <options> — Shibashis
– Shibashis, Commented Jun 5, 2016 at 17:54
Also check this docs.aws.amazon.com/elasticbeanstalk/latest/dg/… — Piyush Patil
– Piyush Patil, Commented Jun 5, 2016 at 17:54
Where in the documentation did you read about AWS CLI replacing EB CLI? I couldn't find that anywhere. — ERIK_SON
– ERIK_SON, Commented Jul 15, 2016 at 8:48

qqbenq · Accepted Answer · 2017-01-23 11:27:53Z

43

You have to create a source bundle from your application, see details here: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/applications-sourcebundle.html (Or alternatively you can use AWS CodeCommit or AWS CodeBuild as source for your application.)

Then you can use the AWS CLI to create a new version from your application and deploy it to one application environment. (See the CLI documentation for EBS here.)

Create a source bundle:

zip MyCodeBundle.zip <source files>

Upload that to S3:

aws s3 cp MyCodeBundle.zip s3://a-bucket-where-you-store-your-source-bundles/

Create a new application version using the source bundle you just uploaded:

aws elasticbeanstalk create-application-version --application-name YourEBSAppName --version-label YourVersionLabel --source-bundle S3Bucket="a-bucket-where-you-store-your-source-bundles",S3Key="MyCodeBundle.zip"

And finally you update one of your environments to use that version (this is deploy even though that verb is completely missing from the new AWS CLI for EBS - this was a little confusing for me):

aws elasticbeanstalk update-environment --application-name YourEBSAppName --environment-name YourEBSEnvironmentName --version-label YourVersionLabel

answered Jan 23, 2017 at 11:27

qqbenq

10.5k5 gold badges43 silver badges47 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

Laurence Gonsalves Over a year ago

Thanks! I was looking for a way to deploy to EB without the weird git integration stuff Amazon provides. This is a bit longer than I hoped, but it works.

alext Over a year ago

If you are trying to run this through Github actions, you need to add region flag. "--region us-east-1"

krishna422 Over a year ago

Can you pls help me with this - How would I know if the environment deployment is completed? since even after aws elasticbeanstalk update-environment is success- deployment is still being processed in aws

JRichardsz Over a year ago

I got this error with create-application-version command

An error occurred (InvalidParameterValue) when calling the CreateApplicationVersion operation: No Application named 'hello-world' found.

JRichardsz Over a year ago

Also, currently create-application-version don't create the environment

Marcin · Accepted Answer · 2020-05-01 08:39:53Z

2

To complement @qqbenq answer, here is an example of AWS CLI deployment to beanstalk with a given deployment policy:

aws elasticbeanstalk update-environment \
    --environment-name <eb-env-name> \
    --version-label <verion-label-to-deploy> \
    --option-settings \
        Namespace=aws:elasticbeanstalk:command,OptionName=DeploymentPolicy,Value=Rolling \
        Namespace=aws:elasticbeanstalk:command,OptionName=BatchSizeType,Value=Fixed \
        Namespace=aws:elasticbeanstalk:command,OptionName=BatchSize,Value=1

answered May 1, 2020 at 8:39

Marcin

241k16 gold badges315 silver badges368 bronze badges

2 Comments

mdabdullah Over a year ago

This really saved my day, all I was looking for was to update one custom value inside configuration. This was my final command:

aws elasticbeanstalk update-environment --environment-name myenvname --option-settings Namespace=aws:elasticbeanstalk:application:environment,OptionName=CONFIGURATION_NUMBER,Value=1.2.003

Marcin Over a year ago

@mdabdullah Glad the answer was useful:-)

Collectives™ on Stack Overflow

How to use AWS CLI with Elastic Beanstalk?

2 Answers 2

5 Comments

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

5 Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related