I'm new to AWS and I'm looking to migrate from a leased dedicated server at a data center. Unfortunately, my initial experience with AWS sales was disappointing as I received generic advice that wasn't useful. I'm hoping to get some knowledgeable insights from this community regarding a suitable AWS instance that would match my current server configuration:
- CPU: E3-1230 V2 @ 3.30GHz
- Memory: 16 GB
- Hard Drive 1: 500 GB Samsung SSD
- Hard Drive 2: 2TB Samsung
- OS: Windows 2016
- Usable IPs: 5 (using 2 for website and email)
- Bandwidth: 10Tb @ 30mbp
My server runs an IIS webserver, MDaemon email server, ColdFusion, server antivirus, and MySQL. I typically see a CPU utilization of 2-10% and memory usage around 40-55%. Having full control over the Windows environment is crucial, including the ability to restart as needed.
Given that I have surplus capacity in my current setup, I'd greatly appreciate your suggestions and advice on what AWS instances might work best for me.
5 Answers
Honestly, AWS might complicate things for what you're trying to do. If you’re running your own email server, it's worth reconsidering your tech stack. Pricing is public, so you can test out instances to see if it fits your needs, but it might be time for a tech upgrade anyway.
If your goal is just to set up a Windows server on AWS alongside MySQL and IIS, you might not get the full benefits of the cloud. I suggest looking into containerizing your applications, which could simplify management and improve resilience. Plus, if you go with something like RDS for MySQL, you can easily scale as your needs grow. Ultimately, setting up the right configuration from the onset will save headaches down the line.
Consider reaching out to AWS directly or finding a partner who can help you architect your migration properly. If you're not comfortable managing AWS's complexities, a two-tier architecture (possibly even three tiers with load balancing) might suit you better than trying to set everything up alone.
You might want to start by spinning up an instance to test how it handles your workload. AWS allows for easy scaling, so once you set it up, you can monitor its performance and adjust the instance type if needed. Just keep in mind that migrating a live website and email system is a significant task, so it's important to plan carefully to avoid unexpected costs or downtime.
For sorting out EC2 instance types based on capability and pricing, I recommend using third-party websites that consolidate this info better than AWS does. Check out instances.vantage.sh for a clearer comparison. Keep in mind that running an email server on EC2 is tricky because port 25 is blocked, which could lead to issues with spamming and reputation management.
Thanks for the link! It sounds like hosting the email separately could be a smart move. The compliance aspect can really complicate things, so balancing that with the flexibility of the cloud could definitely work in your favor.
Exactly! And if your expectations for cost are off, it can lead to bigger issues down the line. If you're not finding resources to help with AWS instance comparisons, I totally understand your frustration. It's tough making these decisions without good information.