Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Elastic Beanstalk CLI commands eb push or git aws.push (in EB CLI 2.6 or lower version) #50

Open
hingston opened this issue Aug 19, 2017 · 0 comments

Comments

@hingston
Copy link

This will stop working on Aug 23, 2017. Details:

You’re receiving this because you have used Elastic Beanstalk CLI commands eb push or git aws.push (in EB CLI 2.6 or lower version) to upload incremental code commits in your AWS Account during the last 6 months. The support for eb push and git aws.push will be retired on Aug 23, 2017. To continue performing incremental uploads, you need to migrate to AWS CodeCommit[1] to manage your code repositories. AWS CodeCommit is a fully-managed source control service that makes it easy for you to host secure and highly scalable private Git repositories. AWS CodeCommit is supported in Elastic Beanstalk EB CLI version 3.8 or higher.

Why is this happening?
AWS Elastic Beanstalk deprecated the EB CLI 2.6 on 12-12-2014[2], and it has stopped receiving bug fixes, security updates and performance improvements. After Aug 23 2017, you can no longer use three commands in EB CLI 2.6, such as eb push, git aws.push or eb branch. We recommend moving onto a version with long-term support (LTS) by AWS Elastic Beanstalk today (EB CLI 3.10).

What are the differences between EB CLI version 3 and version 2.6?
In the LTS EB CLI, you will get full access to AWS CodeCommit and existing new features you don’t have access to now. To see the differences from version 3 of the EB CLI, please visit this page: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli.html#eb-cli2-differences

What do I need to do?
In order to use the functionality provided by eb push or git aws.push, you need to migrate your Elastic Beanstalk repositories to CodeCommit before Aug 23rd, 2017. You can find step-by-step instructions on the following page:
[http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli.html#eb-cli2-migrating]

Is there any cost to use CodeCommit?
Anyone with an AWS account can get started with AWS CodeCommit for free. Your account gets 5 active users per month for free (within limits), after which you pay $1 per additional active user per month. You can find AWS CodeCommit pricing details at: https://aws.amazon.com/codecommit/pricing/

To help you migrate to CodeCommit, we’re offering $50 AWS credit to cover your AWS CodeCommit costs once you migrate.

Where can I get more information?
To learn more about EB CLI Version 3, please see “The EB CLI” section of our documentation in Elastic Beanstalk Developer Guide (http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli3.html). To learn more about how to use the EB CLI with AWS CodeCommit, please visit http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli-codecommit.html
If you run into any issues or need help during the migration, open a support case or email [email protected].

[1]: CodeCommit introduction page: https://aws.amazon.com/codecommit/
[2]: AWS Elastic Beanstalk EB CLI change log: https://aws.amazon.com/releasenotes/2598419100316126

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant