patternMinor
Should I shut down the staging environment when the deployment test ends?
Viewed 0 times
shutthedeploymentenvironmentstagingendsdowntestshouldwhen
Problem
I have a small application deployed on an EC2 instance.
I need a staging environment so I've thought of two choices:
-
Deploy the same app again on the same instance, and that would be a staging environment. But I would really like to separate things and NOT put the two environments into the same instance.
-
Or use another instance especially for staging, but it will be expensive. So, is it good to start the staging instance right before deployment and shut it down when the tests end?
Thank you.
I need a staging environment so I've thought of two choices:
-
Deploy the same app again on the same instance, and that would be a staging environment. But I would really like to separate things and NOT put the two environments into the same instance.
-
Or use another instance especially for staging, but it will be expensive. So, is it good to start the staging instance right before deployment and shut it down when the tests end?
Thank you.
Solution
You can approach this case with multiple ways.
I commented on paths that you can follow, so you should choose one that brings you greater benefit and agility both in creating your environments and in testing them.
Regards
- For example you can set an auto-shutdown for 20:00 pm and auto-start for 8:00 am.
- Use Terraform to create your environment and, after deployment/testings, you can easily destroy it, saving your costs.
- And many other ways.
I commented on paths that you can follow, so you should choose one that brings you greater benefit and agility both in creating your environments and in testing them.
Regards
Context
StackExchange DevOps Q#14394, answer score: 2
Revisions (0)
No revisions yet.