Yes and yes. The docs aren't really clear on those either. I spent so much time reading up on the instances and what they were good for, but when I got into select one there were new options that said "better". Why were they better? Back to researching. I guess that's just the way it goes though. And, there are so many settings in the aws calculator that I have no clue what they do. It's like you have to be an expert going into this to understand it.
One thing that really gets me every time is cost. They're not clear on what changes will incur costs, and what those respective costs will be. They just say "may increase your monthly bill" -- the budget tool is no help in this area as well. I've set up alerts and that's all well and good, but that's basically a live version. I want to know what if I add 20GBs to my instance, what will that do?
I spent most of the day trying to get a multi site setup on my ec2 instance. Granted, this was probably mostly lack of apache2 knowledge but still took a while.
I don't know, maybe I'm just in a big rant fest right now about having to research each and every little thing I encounter or want to do?
It's not just you, AWS is something you have to get used to. If you really plan to get into it I recommend trying a course on udemy to learn about all the different service available.
Back to your specific case:
The way machines in AWS work (and EC2 specifically) is they have an intended purpose category (t for general purpose, r for memory optimized, c for compute), they have the generation (3, 4, 5) and they have the size (large, xlarge, 24xlarge).
All of these factors affect the pricing, for example for a machine used in our MemSQL cluster I'd choose a memory optimized one (cause MemSQL sits in the RAM), but for a "utils" server used to manage some service I'd take a general purpose one. If I'd take a compute machine for Mem, I'd have to pay for a huge one to get to the amounts of memory I need.
In general it's advised to use the latest generation available in the region you picked, it's usually cheaper.
My rule of thumb is this: pick the smallest machine I can get away in the latest generation. The beauty about cloud computing is that you can upgrade or downgrade your machines as you go, you don't have to commit to a single size or type from the beginning (hence the name Elastic Compute Cloud)
I don't really use the budget tool, I find it unintuitive. I use the pricing page for each service I use and try to estimate the costs. I'm lucky that I work in a relatively large company with people that work in cost optimization and can help me understand it better if there's an issue.
If you have any specific issues or questions you can send me a PM and I'll try to help as best as I can (:
Thank you for your response. It cleared some things up for me. What I personally got out of that was "general purpose" is probably the way to go. lol! I appreciate your willingness to help!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yes and yes. The docs aren't really clear on those either. I spent so much time reading up on the instances and what they were good for, but when I got into select one there were new options that said "better". Why were they better? Back to researching. I guess that's just the way it goes though. And, there are so many settings in the aws calculator that I have no clue what they do. It's like you have to be an expert going into this to understand it.
One thing that really gets me every time is cost. They're not clear on what changes will incur costs, and what those respective costs will be. They just say "may increase your monthly bill" -- the budget tool is no help in this area as well. I've set up alerts and that's all well and good, but that's basically a live version. I want to know what if I add 20GBs to my instance, what will that do?
I spent most of the day trying to get a multi site setup on my ec2 instance. Granted, this was probably mostly lack of apache2 knowledge but still took a while.
I don't know, maybe I'm just in a big rant fest right now about having to research each and every little thing I encounter or want to do?
It's not just you, AWS is something you have to get used to. If you really plan to get into it I recommend trying a course on udemy to learn about all the different service available.
Back to your specific case:
The way machines in AWS work (and EC2 specifically) is they have an intended purpose category (t for general purpose, r for memory optimized, c for compute), they have the generation (3, 4, 5) and they have the size (large, xlarge, 24xlarge).
All of these factors affect the pricing, for example for a machine used in our MemSQL cluster I'd choose a memory optimized one (cause MemSQL sits in the RAM), but for a "utils" server used to manage some service I'd take a general purpose one. If I'd take a compute machine for Mem, I'd have to pay for a huge one to get to the amounts of memory I need.
In general it's advised to use the latest generation available in the region you picked, it's usually cheaper.
My rule of thumb is this: pick the smallest machine I can get away in the latest generation. The beauty about cloud computing is that you can upgrade or downgrade your machines as you go, you don't have to commit to a single size or type from the beginning (hence the name Elastic Compute Cloud)
I don't really use the budget tool, I find it unintuitive. I use the pricing page for each service I use and try to estimate the costs. I'm lucky that I work in a relatively large company with people that work in cost optimization and can help me understand it better if there's an issue.
If you have any specific issues or questions you can send me a PM and I'll try to help as best as I can (:
Thank you for your response. It cleared some things up for me. What I personally got out of that was "general purpose" is probably the way to go. lol! I appreciate your willingness to help!