Environment forever stuck in abort

Hi There,

We accidentally deleted a Custom AMI prior to a transitioning the environment to a new Custom AMI, and now the environment is forever stuck in an abort. Is there anyone who can assist? In trying to update the AMI via the CLI, we receive this error:

command: aws elasticbeanstalk update-environment --environment-name {env-name} --option-settings Namespace=aws:autoscaling:launchconfiguration,OptionName=ImageId,Value={new-ami-id} --region {region}

An error occurred (InvalidParameterValue) when calling the UpdateEnvironment operation: Environment named {env-name} is in an invalid state for this operation. Must be Ready.

Thanks!

Edited by: bwn on Jan 11, 2019 1:59 PM