How does one optimise their infrastructure in AWS you may ask, well… I have made a little ‘Techdox Rules for AWS” it’s all pretty basic, but when someone new see’s all this processing power sometimes they can’t contain themselves. (GUILTY!)
- Sit down and think of exactly your infrastructure is going to need in terms of CPU power, Storage space, redundancy and security.
- If multiple people are going to be using AWS make them accounts, do not use your ‘GOD’ account for daily use. The more restrictions of your staff the less chance of them building up charges to your account.
- Set a monthly budget to track your spending, for example I put a budget of $10.00 and I checked it the next week and my forecast spending was $120.00… the budget can show you what is going to be charging you so much in the future and allows you to change something before it stings your bank, this leads us to my next rule.
- Set alarms! if your budget has not been monitored you have a fallback which is an alarm, lets say you have not tracked your budget and you have an alarm to set off after you have gone over budget e.g. and email or SMS is sent out, that gives you a good chance to get it sorted.
- Only use what you need. When you are building your infrastructure e.g. EC2 machines, make sure you are only creating what you need. Do you really need 5 machines located all around the would on a load balancer for a website about dinosaurs? I did not think so.
Optimisation is all about making your service run at an optimal level with the cost to run at an affordable level as well. Cloud providers like AWS offer you an IaaS (Infrastructure as a Service) all you need to do is add your service on top of it.
Cloud storage is like a credit card, it can be a really useful service or it can land you in a pit of crippling debt. – Techdox 2017