Amazon VPC Cloud where to start or what are the alternatives? How to calculate the cost?
Need to organise a system of two or three web servers with a load balancer, two database replicated to them and file storage all this must communicate on their internal network, the outside must look only gateway\balancer. The government wants the cloud, preferably Amazon. I absolutely idea how to do this in the form of iron servers, but Amazon as someone who is not given to me. I have created a test machine for linux, as it allows them a trial, but that's all, I can't figure out how to calculate the cost of their services, as I understand it from all the services I need only lightsail that would have been a regular VPS and the network between them. What will be the cost of the whole system? Only the cost of the VM? Or they take some kind of monthly fee for lightsail, for network traffic over a VPC? I can't find this info in control panel. Can someone suggest a more simple solution for this project?
marques_Rutherford answered on June 14th 19 at 20:02
lightsail, as you can guess from the name, this is a simplified(easy) interface on compute - Elastic Compute Cloud (EC2) services. And a little cheaper due to the fact that the control you are given is not enough. But he soon realizes some patterns and sets of services for a quick start. This is the way of startups.
Lightsail, as I recall, starts in the "default VPC" and managed by AWS, where all the servers live in a public subnet that is unsafe.
The scheme that you want, probably, is implemented lightsail-Ohm, but for more control still it is recommended to organize your VPC (Virtual Private Cloud) - network of AWS services.
In your case you will need something like(for valuation) :
1. Balancer :
- ALB\ELB service (separate pricing). HA service provides AWS
- two instances you need a load balancer (Nginx, HAProxy, and others). HA and others provide you.
2. N backend of the appropriate type (see the value of a particular instance meets your needs)
3. replicated database :
- you can take 2 instance need the power(pay for instance) and configure everything yourself
- to take the RDS (separate service, different pricing) need database HA and where service will deal with AWS for you, giving you endpoint to connect with servers.
4. File storage. This is better
If you have Windows : you will need two instances for fault tolerance and HA
If you have *nix : you can do the same with WIndows or take the EFS (individual service where you pay for the place) which is highly available and can be connected to different *nix instances at the same time.
5. Inside VPC
VPC is available as well as any network in the iron equivalent.
Subnet - private, public
Configuring for routing public subnet to private subnet through the NAT instance\service
NAT instance or service
VPN instance or Bastion (to access instances in private subnets)
Here you can already calculate how much it would cost for about hold only instances and services.
How many will you have unexpected expenses on data etc. - you will be able to see only the results of the billing for the first month.
This is my personal opinion on how I should have done in your case.
It may be that you have not mastered (each with its own speed of development) is fast enough and faster implement a different scheme - the choice is yours