How do I get Elastic Beanstalk config changes to persist?

My workflow is like this:

1. Create environment via eb create (i.e. the command line tools)
2. Notice that something is broken
3. Maybe change an environment variable in the AWS EB dashboard
4. Terminate environment via eb terminate
5. Maybe edit code locally and commit
6. Repeat from step 1.

And my problem is the intersection of these factors:

• I would like to use Saved Configurations so that eb create --cfg LiveConfig will work, and so that we can have one configuration for live, one for staging, etc.
• The dashboard only lets me edit the environment for running environments - so, even if I know I am lacking a key environment variable for the current code, I still need to spin up that instance to be able to edit it in the Dashboard, which wastes time.
• The dashboard will let me overwrite the current running environment (which is typically useless as the program has probably already read all its config data), but does not commit this change to the Saved Configuration that I used to launch this environment.
• The dashboard does not allow me to overwrite an existing Saved Configuration, meaning that instead of being able to edit LiveConfig and immediately relaunch with that, I end up having to assign a new name each time, leaving me with LiveConfig2, LiveConfig3, LiveConfig4, .. LiveConfig37, etc etc.

Is there a better way?