Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

12
  • 3
    Alternatively, you can also save the configuration, and launch the new environment using the configuration. Commented Jul 26, 2013 at 12:58
  • 1
    Yep, I'd say that's the best option. I just keep forgetting it and launch new environments willy-nilly. :) Commented Jul 26, 2013 at 13:08
  • 1
    @dingdong: yep, and in particular you can access them in your application. E.g. in Rails ENV["CUSTOM_ENV"] would return "something-something". Commented Jun 13, 2014 at 11:25
  • 3
    If I add new properties, or change a property value, are they immediately available, do they require anything to be restarted etc? I recently changed the size of an autoscaling group and AWS terminated nearly all 40 of our instances and spun up 45 new ones. I don't want that to happen if I add a new property to an existing environment. Any ideas? Commented Feb 25, 2015 at 16:27
  • 6
    Beware of the recent changes. As per this answer, they are not passed as environment variables. They are only passed as system properties Commented May 26, 2016 at 23:07