Hourly usage also makes sense if you are actively determining the minimum system size you’ll need, or testing a solution out. Previously, you had to allocate them to a specific zone in a region to match your instances. Secondly, although zone based reserved instances may still have some small benefits, you can now use region based reserved instances.
This is a big relief, because creating the autoscale groups has become a bit more difficult, and even before were prone to creating problems if the an instance was stopped, resized, etc. You no longer need to add an instance to an autoscale group in order to use your reserved instances. This can be perfect for short-term usage or where your usage may fluctuate frequently.
When you spin up any new AWS based VM you will by default be using an hourly instance. This can shave 30% or more off your AWS instance charges. We’ll discuss how you can use a one or three year reserved instance for your FileMaker Cloud instance.
0 kommentar(er)
