Resolved: Adding MX Record(s) in AWS

 Recently, I was migrating MX records from WIX to AWS. I was using GSuite and I was unable to do the same. Then after a little bit of research, I found this stackoverflow link , which helped me resolve the problem. Here is how you should be adding the records in AWS. Record Name: @ Record Type: MX Value: <Priority> <Route Traffic to> example: 10 aspx.alt1.google.com And if you have multiple records, simply add the records in the same text area in the new line and no commas. This will resolve your problem. :)

Understanding FaaS, Functions as a Service

There is a lot of buzz about the cloud. There are numerous options to host your applications or using pre-built softwares for your business needs.
So, there are different kinds of services available in the cloud.


  1. IaaS (Infrastructure as a Service) - In this you need to manage the servers yourself including the patches, updates, security and application hosting.
  2. PaaS (Platform as a Service) - So, you get the manged infrastructure by the cloud provider and you can focus on your application development
  3. SaaS (Software as a Service) - There are hundreds of thousands softwares available in the market that may fit to your needs directly and can be available in the cloud as well, be that a CMS like Wordpress, DotNetNuke, Joomla etc or an ecommerce solution like Prestashop, Opencart, Woocommerce, magento, NopCommerce or in softwares belonging to under domains and industries.
  4. But what if you need to create a custom application and still want the cost to be the least and infrastructure to be managed by someone else. You don't want to bother about fault tolerence and scalability, is there a solution available?
Yes, FaaS (Functions as a Service) which means you can create applications based on serverless architecture.

Is it really Serverless?
Not really. It simply means, that you don't need to worry about the infrastructure at all. It is a compute service that runs your code on demand based on various events.
In Microsoft Azure, it is called Azure Functions.
In Google Cloud, it is called Google Cloud Functions.
In AWS, you call it Lambda Functions.
You can also have your own FaaS using OpenFaaS

Okay! I get it. So what are the different use cases?
Well, there can be many:
  1. You may want to resize/process your images on your server.
  2. Need a payment service 
  3. Sending bulk emails
  4. sms
  5. Push Notifications
Infact, you can take a look at this document

Nowthat we have a very basic understanding of what serverless architecture and functions as a service means, we'll play with Azure Functions in the next article.