<p>With cloud solutions like AWS, this is not so straightforward to figure out like with "classic", always-on servers that wholly belong to you, and where you are paying fixed monthly prices for power, network, backup and rack-space, with maybe a little bonus on-top if you exceed some bandwidth limits.</p>

<p>So, in your case, have a good look at what "sizes" of VMs AWS has to offer. According to Wikipedia, in 2016, prices on AWS ranged from $0.0065/hour to $6.82/hour, depending on performance and other factors, with similar ranges for storage, and then further complicated by other factors of your plan (i.e., 3-years prepaid or whatever).</p>

<p>Secondly, you have to factor in when and how long you actually need your application to be available. If none of your users are working before 7am or after 9pm, then you can have the application running only in this time, not paying anything in the "off" time.</p>

<p>Thirdly, there are even more options. For example, maybe you can use lambdas for some functionality of your application (even more finegrained control over costs) and so on.</p>

<p>Lastly, there are things like spot prices, where you bid for unused resources at drastically lower prices. You might become creative here and run your background batch processes on such instances, for example.</p>

<p>More variations are mentioned in the comments.</p>

<p>So, you see, we cannot really predict what your application will cost. It would certainly be possible to give you a ballpark figure in the case that you would run your application 24/7 just like a classic VM, but that would be rather useless.</p>

<p>You need to sit down, read some more about the AWS pricing structure (they do have an online calculator where you can plop a few values in). As you are not doing a play or for-fun project, it would also be more than worthwhile to actually experiment, get an AWS account, develop a small prototype and do some performance tests so you see what you actually do need.</p>

<p>Check out their calculator at <a href="https://aws.amazon.com/tco-calculator/" rel="nofollow noreferrer">https://aws.amazon.com/tco-calculator/</a> if you didn't already, but be prepared that their breakdown of on-premise costs is, in my opinion, not very useful (you'd better figure that out yourself, if on-premise is at all an option for you).</p>

CC BY-SA 3.0
2018-01-30T15:22:52.120Z
AWS prices vary with the region used also. I wonder if giving the calculator link in the answer would help the OP or not :/
Tensibai
CC BY-SA 3.0
2018-01-30T17:17:05.167Z
@Tensibai, I've added a link. Not a big fan of it (their on-premise cost comparison are, IMO, ludicrously overcalculated).
AnoE
CC BY-SA 3.0
2018-01-30T17:44:25.117Z
@AnoE Reserved instances can also play a factor. If you are going to have the VM persist for the foreseeable future, they can be a huge cost saver.
Preston Martin
CC BY-SA 3.0
2018-01-30T20:01:44.020Z
@anoe I was more thinking about the cost estimator, tco are always highly opinionated, but one or the other, without insight of what OP wish to do that doesn't add much IMO.
Tensibai
CC BY-SA 3.0
2018-01-30T15:09:30.980Z
2018-01-30T18:12:10.810Z
2018-01-30T18:12:10.810Z
AnoE
<p>I am developing an inventory management application i want to use AWS EC2 . which will have 10-15 users and storage about 2GB  .as a newbie i could not understand the pricing can somebody help me how much it will <strong>cost me per month</strong></p>

CC BY-SA 3.0
2018-01-30T13:26:16.640Z
What do you not understand ? please try to give some details about you read and are not understanding... We can't guess what you did read and didn't understood.
Tensibai
CC BY-SA 3.0
2018-01-30T13:51:33.297Z
how much it will cost
salih
CC BY-SA 3.0
2018-01-30T13:54:45.060Z
It will cost you per month the hour price of the instance type chosen by 28*24 in february, 24*31 in March and 24*30 in april...
Tensibai
<amazon-web-services><amazon-ec2><cloud>
How much it will cost for AWS for deploying a inventory management application
salih
# How much it will cost for AWS for deploying a inventory management application

(Asked by: username_0 on 2018-01-30)

I am developing an inventory management application i want to use AWS EC2 . which will have 10-15 users and storage about 2GB .as a newbie i could not understand the pricing can somebody help me how much it will **cost me per month**

**Tags:** amazon-web-services, amazon-ec2, cloud

> **Comments:**
> **username_1**: What do you not understand ? please try to give some details about you read and are not understanding... We can't guess what you did read and didn't understood.  
> **username_0**: how much it will cost  
> **username_1**: It will cost you per month the hour price of the instance type chosen by 28*24 in february, 24*31 in March and 24*30 in april...  

---

## 1 answers

### Answer by username_2 on 2018-01-30. Score: 1 | Accepted answer

With cloud solutions like AWS, this is not so straightforward to figure out like with "classic", always-on servers that wholly belong to you, and where you are paying fixed monthly prices for power, network, backup and rack-space, with maybe a little bonus on-top if you exceed some bandwidth limits.

So, in your case, have a good look at what "sizes" of VMs AWS has to offer. According to Wikipedia, in 2016, prices on AWS ranged from $0.0065/hour to $6.82/hour, depending on performance and other factors, with similar ranges for storage, and then further complicated by other factors of your plan (i.e., 3-years prepaid or whatever).

Secondly, you have to factor in when and how long you actually need your application to be available. If none of your users are working before 7am or after 9pm, then you can have the application running only in this time, not paying anything in the "off" time.

Thirdly, there are even more options. For example, maybe you can use lambdas for some functionality of your application (even more finegrained control over costs) and so on.

Lastly, there are things like spot prices, where you bid for unused resources at drastically lower prices. You might become creative here and run your background batch processes on such instances, for example.

More variations are mentioned in the comments.

So, you see, we cannot really predict what your application will cost. It would certainly be possible to give you a ballpark figure in the case that you would run your application 24/7 just like a classic VM, but that would be rather useless.

You need to sit down, read some more about the AWS pricing structure (they do have an online calculator where you can plop a few values in). As you are not doing a play or for-fun project, it would also be more than worthwhile to actually experiment, get an AWS account, develop a small prototype and do some performance tests so you see what you actually do need.

Check out their calculator at <https://aws.amazon.com/tco-calculator/> if you didn't already, but be prepared that their breakdown of on-premise costs is, in my opinion, not very useful (you'd better figure that out yourself, if on-premise is at all an option for you).

> **Comments:**
> **username_1**: AWS prices vary with the region used also. I wonder if giving the calculator link in the answer would help the OP or not :/  
> **username_2**: @username_1, I've added a link. Not a big fan of it (their on-premise cost comparison are, IMO, ludicrously overcalculated).  
> **username_3**: @username_2 Reserved instances can also play a factor. If you are going to have the VM persist for the foreseeable future, they can be a huge cost saver.  
> **username_1**: @anoe I was more thinking about the cost estimator, tco are always highly opinionated, but one or the other, without insight of what OP wish to do that doesn't add much IMO.  

---

