# Bauen Sie eine Sandbox, um Änderungen zu testen, bevor Sie sie live schalten

**URL:** <https://meta.discourse.org/t/build-a-sandbox-to-test-changes-before-making-them-live/58298>\
**Category:** Sysadmins\
**Tags:** how-to\
**Created:** [3. März 2017 um 13:34 UTC](https://meta.discourse.org/t/build-a-sandbox-to-test-changes-before-making-them-live/58298 "2017-03-03T13:34:07Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mikechristopher](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mikechristopher/32/89135_2.png) [@mikechristopher](https://meta.discourse.org/u/mikechristopher)\
**Post date:** [3. März 2017 um 15:18 UTC](https://meta.discourse.org/t/build-a-sandbox-to-test-changes-before-making-them-live/58298/2 "2017-03-03T15:18:48Z")

</div>

Quick question on this as pretty new to AWS

- when setting the domain what did you use (if you dont have a domain) - I was able to use the public dns / IP to start but once you stop the server the IP address changes unless you use elastic IPs.  
I am now able to access it on the new IP - however will this not cause me issues with the IP changing constantly everytime I stop / start it when I need it.?

---

_[View the full topic](https://meta.discourse.org/t/build-a-sandbox-to-test-changes-before-making-them-live/58298)._