eb terminate - AWS Elastic Beanstalk

eb terminate


Terminates the running environment so that you don't incur charges for unused AWS resources.

Using the --all option, deletes the application that the current directory was initialized to using eb init. The command terminates all environments in the application. It also terminates the application versions and saved configurations for the application, and then deletes the application.

If the root directory contains a platform.yaml file specifying a custom platform, this command terminates the running custom environment.


You can always launch a new environment using the same version later. If you have data from an environment that you want to preserve, set the database deletion policy to Retain before terminating the environment. This keeps the database operational outside of Elastic Beanstalk. After this, any Elastic Beanstalk environments must connect to it as an external database. If you want to back up the data without keeping the database operational, set the deletion policy to take a snapshot of the database before terminating the environment. For more information, see Database lifecycle in the Configuring environments chapter of this guide.


eb terminate

eb terminate environment-name





Terminates all environments in the application, the application's application versions, and its saved configurations, and then deletes the application.


Terminates the environment without prompting for confirmation.


Terminates the environment even if there are dependent environments with links to it. See Compose Environments.


The number of minutes before the command times out.


If successful, the command returns the status of the terminate operation.


The following example request terminates the environment tmp-dev.

$ eb terminate The environment "tmp-dev" and all associated instances will be terminated. To confirm, type the environment name: tmp-dev 2018-07-11 21:05:25 INFO: terminateEnvironment is starting. 2018-07-11 21:05:40 INFO: Deleted CloudWatch alarm named: awseb-e-2cpfjbra9a-stack-AWSEBCloudwatchAlarmHigh-16V08YOF2KQ7U 2018-07-11 21:05:41 INFO: Deleted CloudWatch alarm named: awseb-e-2cpfjbra9a-stack-AWSEBCloudwatchAlarmLow-6ZAWH9F20P7C 2018-07-11 21:06:42 INFO: Deleted Auto Scaling group policy named: arn:aws:autoscaling:us-east-2:11122223333:scalingPolicy:5d7d3e6b-d59b-47c5-b102-3e11fe3047be:autoScalingGroupName/awseb-e-2cpfjbra9a-stack-AWSEBAutoScalingGroup-7AXY7U13ZQ6E:policyName/awseb-e-2cpfjbra9a-stack-AWSEBAutoSca lingScaleUpPolicy-1876U27JEC34J 2018-07-11 21:06:43 INFO: Deleted Auto Scaling group policy named: arn:aws:autoscaling:us-east-2:11122223333:scalingPolicy:29c6e7c7-7ac8-46fc-91f5-cfabb65b985b:autoScalingGroupName/awseb-e-2cpfjbra9a-stack-AWSEBAutoScalingGroup-7AXY7U13ZQ6E:policyName/awseb-e-2cpfjbra9a-stack-AWSEBAutoSca lingScaleDownPolicy-SL4LHODMOMU 2018-07-11 21:06:48 INFO: Waiting for EC2 instances to terminate. This may take a few minutes. 2018-07-11 21:08:55 INFO: Deleted Auto Scaling group named: awseb-e-2cpfjbra9a-stack-AWSEBAutoScalingGroup-7AXY7U13ZQ6E 2018-07-11 21:09:10 INFO: Deleted security group named: awseb-e-2cpfjbra9a-stack-AWSEBSecurityGroup-XT4YYGFL7I99 2018-07-11 21:09:40 INFO: Deleted load balancer named: awseb-e-2-AWSEBLoa-AK6RRYFQVV3S 2018-07-11 21:09:42 INFO: Deleting SNS topic for environment tmp-dev. 2018-07-11 21:09:52 INFO: terminateEnvironment completed successfully.