Videos
I would like to have someone set up an Email Server on AWS Free Tier, is it possible?
I have 4 domains and need one email address for each domain that will serve as a catch-all address. I would like POP / SMTP and Webmail.
What should I expect to pay someone to set it up?
I'm confident in my abilities to set up and maintain web servers, and create websites, but email is something I've never hosted myself, so please forgive the lack of proper terminology.
I'm in the process of moving all my sites from GoDaddy to AWS, and that's all fine except for the email accounts. I don't really understand the difference between a "mail server", an mx record, a relay, and all of that. I just set up accounts in GoDaddy, and plug in the relevant details to my/my client's email applications. Like I say I'm fairly comfortable on a Linux terminal, and I can find my way around a tutorial/man page, so long as I know what man page I should be reading.
So what are my options?
SES - I don't really understand the whole part about being Sandboxed - does this mean I can't send emails to anyone until Amazon approves my account? How do I get approved? And once I am, does that mean I have to nitpick my client's email habits, and whether any of their messages are unsolicited? And does SES handle incoming messages? Basically, I don't even really understand what SES is.
Setting up all necessary servers on my EC2 instance(s) - I'm perfectly willing to learn how to install, configure and maintain my own email servers, so long as I know what I'm actually supposed to learn. I also understand there's some wrinkle with AWS and needing permission before being able to send mail in and out.
Paying some third party - can I just buy email services from some company like Godaddy and bind it to domains that I'm hosting on my EC2s? Is this a good idea?
Essentially, I'm kinda just lost.
I host over 350 email accounts on 100+ domains on one of my AWS Instances. If you're willing to spend up to a week configuring your email server, working with Amazon to get your EIP off the black lists and setting up your reverse DNS. IT CAN BE DONE. ARS Technica published a very good guide. http://arstechnica.com/information-technology/2014/02/how-to-run-your-own-e-mail-server-with-your-own-domain-part-1/ It's not specific to AWS, but covers Linux based server configuration. It will get you off to a good start. Although some of the SPAM restrictions are a bit on the strict side.
Good Luck, A word of advice spend some time studying every configuration they recommend. Make sure you understand what it's doing. This will make it easier for you to diagnose problems when your users complain that they aren't getting email from their buddy.
AWS IP addresses are on the block lists used by most ISP's so hosting a mail server there is not good. You can hack postfix to use SES as an outbound transport but it's a pain in the ass to do - it's a lot easier to use google apps for email. - You can bind your domains to google apps.
I'm looking to create a personal website, hosted on a domain I buy. Additionally, I want to have an email associated with the site. The email would be used as a personal email, so I would need to both receive and send emails.
Is AWS hosting the best option for email hosting?
So you have purchased a new domain
abc.comand have already set it up inRoute53. Good. Now you want to point this domain to your other websitexyz.com. So, you will go to Route53 console, and will create aCNAMErecord to point abc.com to xyz.com. What this CNAME record will do is create an alias for xyz.com. The Route53 console is self explanatory. If you will feel confused, just ping me here and ask specific doubts.To set up your email server with your own domain e.g.
[email protected], you have to think what product you want to choose. There is Amazon workmail, Gmail for business, Office 365, etc. Each of these service will charge you. E.g. Amazon workmail charges you $4 per month, per user. Similarly gmail charges you $5. They will also give you additional benefits such as calendars, chat applications, etc. Once you have set this up, you can send and receive emails normally like you do in gmail.
If you would like to send bulk emails using an API, that is where Amazon SES comes in. This service will allow your already created email address to send thousands of email to your customers. It also serves other purposes such as creating a filter list of users, bouncing back messages that are not delivered, scanning for viruses, etc.
Q1 is simple enough. But the problem is, if you built your website by Weebly, as they don't allow FTP access, you can't get your website file out of Weebly. Then you can't put your website on S3. So the answer is, you can either stay with Weebly, or you have to build a new website without using online website building services like Weebly.
Be noticed that you can only host a static website on S3, which means no database, PHP etc is allowed.
For Q2, you misunderstood Amazon Web Services. They provide email sending service called SES (for companies which send 100,000 emails per day with cheap price), but they don't provide any email inbox. This fact bothered me and finally I solve the mailbox problem by setting up email forwarding on Godaddy, so that all incoming email of my domains could be forwarded to my personal email account. But if you registered your domain by Weebly, they provide email inbox service didn't they?