Sage 100

Urgent sales question - we have a prospect who is interested in running on AWS. He will start with a 10 user Sage100 license ... and possibly grow to 15-20 at some point. Could use some help if anyone knows what ""level"" or spec of AWS to get. One server (with Standard) or two (with Advanced)... Thanks - trying to get an order and they are asking, and the requirements document really doesn't address this.... Thanks in advance

Hi Jeff - we have a client on Azure - do you think if i get the specs that they are using it will help the cause?

That would be great - thanks Douglas ... not sure they are open for Azure, but that is better than nothing ! still hoping for someone doing AWS

Gotcha - let me reach out to the client and like you said, it will be better than nothing, in case you do not get someone with AWS

Jeff, you can spec out the AWS servers pretty much the way you would spec an on-premise server. The nice thing is that you should expect slightly better performance from AWS for the same specs. In general, AWS instance types (T3 medium, T3 large, M2 small, etc. etc) will tell you the number of virtual CPUs and the amount of RAM. Each instance type is tuned for specific workloads. As you know, Sage 100 tends to be IO heavy so pick an instance type which is tuned that way. I am not the one to say which types are best, since that's out of my area, but you know how you would spec a physical server, so you should be able to pick the right one in AWS. FWIW, I really like dealing with the AWS environment.

Thanks Phil - knowing which types are appropriate, based on someone who has done this, is exactly what I am looking for...

The instance types are described here: https://aws.amazon.com/ec2/instance-types/. As I implied earlier, any advice that *I* might give regarding hardware should be given all the weight that you would typically give an electrician advising you on how to frame a house. However, I think Sage 100 is best served by a general purpose instance with fast storage IO. I use T3 and T2 types only, but for a production Sage 100 instance I'd be inclined to think about an M5 or M5a instance because those offer dedicated SSD storage, which is really nice. The price is also higher. One of the lovely things about AWS is that resizing an instance is very easy, and even changing an instance type is doable, and you don't have leftover hardware to worry about. I have started with a T2 Small instance before and was able to move to a T3 Large with almost no effort. I had to shut down the server for a little while, but that was it.

Hi Jeff - i just spoke to the IT person and about Azure (and she also works with AWS) and she said there are so many options it would be better to have a phone call (with her, not me). If needed, shoot me an email at douglas@aciconsulting.com and i will share her info to you.

Okay - having no idea of what I speak, but trusting my IT guys totally, here's what they say: For a single server (standard) i'd get a C4.2xlarge (8cores 15GB RAM) That is for an EC2 instance. They could get away with a C4.xlarge now and grow into a C4.2xlarge if needed later on. With Advanced i'd want to do 2x C4.2xlarge since most of the processing is done on the server instance but the RDS server will still need to have 15-20 users running on it.

MyHostedDSD does uses AWS solely, and have extensive experience in hosting Sage on that platform. You can contact @RobertEppele to get any questions answered. Also, just a heads up re @PhilipWhirley comment: Please be careful when using the dedicated SSD Storage. These are ""Instance Stores"" and do not persist across stops/terminations/hardware failures. These would be a horrible choice for Sage data. Please always use EBS Volumes, and add provisioned IOPS if the added throughput is needed. You can look here for further information on this: https://help.acloud.guru/hc/en-us/articles/115003534253-AWS-EC2-Instance-Store-vs-EBS