Amazon WorkMail Reviews

Within our organization, we handle procurement and keep customers updated through email. Most customers use our procurement application, which goes through different stages. When a customer submits a request on our website, we send them a message via Amazon WorkMail to confirm that their request has been received and is under review. We regularly update them on the status of their procurement through email.

For instance, if a customer is procuring items from China and shipping them to Africa, we inform them at each stage. From the initial procurement process in China to the transfer of goods to West Africa, such as Nigeria, we keep the customer informed at every step.

The most valuable feature of the Amazon WorkMail for me is the SMC server. It makes my work much easier, especially since I often work with Spring Boot. There are many built-in APIs in Spring Boot that help with messaging. What I appreciate about it is that it simplifies the process. I don't need to write much code; I define the credentials in my properties or environment variables. The Java Message API, an internal API from Spring Boot, does most of the work. I set up the properties and connected them to the SMC server, and I can send emails. 

We use it to send emails, basically. Plus, whenever you send or receive an email, WorkMail gives you a trigger point. It's very much integrated with other AWS services. For example, one use case we had was with our UAT servers. They were costing us a lot because we had to pay for them every month, even when no one was using them for a few months.

So, we set it up so that whenever a client sends us an email saying "please turn on the UAT server," the UAT server automatically turns on using WorkMail. We get a trigger that the client wants the server on, so we turn it on. After four or five days, it automatically turns off, which saves us money. That's one use case we are using it for.

The integrations. WorkMail has great integrations with Lambda functions, relationships with SNS, and other AWS services. The integration capabilities are very simple, easy, and powerful.

With more integrations, you can create more workflows. If you have limitations, you cannot create those integrations.

I use Amazon WorkMail to create email accounts and integrate them with Gmail and Microsoft Outlook. I've launched a website and migrated it to AWS infrastructure, and WorkMail is part of this integration.

Amazon WorkMail integrates with Route 53 and other AWS services, providing a seamless experience when using AWS infrastructure.

We used the product to send email notifications to our customers, end users, or our internal team. If we are hosting any applications, the customer must know it.

The product is very user-friendly. It enables us to send emails to end users.

Our primary use case is to send emails to any person using an identity.

The best feature is that Amazon SES provides verified email messages. There are many software and email services, but SES provides verified accounts for an organization. With SES, you can also handle any bounces or complaints we receive from emails.

Three main things that I like about it are:

• It comes out of the box as an Amazon service.
• It is completely a managed solution.
• It is highly scalable.

Because it is completely managed, I don't need to worry about availability and resiliency. These are the things that we typically require from any email service. We previously had a lot of problems with the on-premise environment.

It is highly available and scalable. It is also highly reliable. I don't lose any of the messages or emails. If there is an issue where the email sent operation failed, Amazon as a platform ensures that the send operation is retried, and the email reaches its destination. This way, it is highly reliable. 

Email service is definitely a requirement from an enterprise standpoint. Many organizations have their own on-premise email services, which take a lot of memory, backup, and other resources. If we can have a completely managed backup solution where we have a tiered backup or a tiered archival to be able to retrieve emails, it would be great. I would like to be able to retrieve emails in real-time (hot retrieval), over the 90-days period (warm retrieval), and over the one-year period (cold retrieval). It would be useful to have tiered backup and retrieval. It would help us in managing emails better and have a better backup solution. So, backup is something that we require. 

We would also like to have cross-regional support. Tomorrow, my enterprise might be functioning across multiple geographies or globally, and if we can have a sustainable and reliable synchronization solution to replicate emails across multiple geographies so that everybody can access them—if not in real-time, then at least in a suitable amount of time—it would be helpful. It would be a really good feature to add.

We use Amazon SES to send emails and notifications to our customers.

Amazon SES is very easy to configure. If I have an email ID in Gmail, I would have to learn the Gmail API to send an email programmatically. The advantage of Amazon SES is that I don't have to learn the API of the email service provider. I can just add my email on Amazon SES, do some verification, and send the email content directly to Amazon SES, which will then go through my email. So I don't have to learn the API of the email service provider. If tomorrow we start using a Yahoo account, I'll have to learn the API of the Yahoo email service. So, in this case, we can add both accounts to Amazon SES, and we only have to learn the API of Amazon SES.

We primarily use the solution for:

1. Transactional emails. Applications can use SES to send emails related to specific user actions, such as password resets or account confirmations.
   
2. Marketing emails. SES can be used to send newsletters, promotional emails, and other marketing communications to large email lists.
   
3. Notification emails. SES can be used to send notifications or alerts to users or administrators, such as order confirmation emails or system status updates.
   
4. Custom emails. SES can be used to build custom email solutions, such as automated email responses or personalized email campaigns.

Overall, SES is designed to make it easy for businesses to send a high volume of emails quickly and reliably, with features like automatic retries and email-sending history tracking.

The solution has improved our organization by offering:

1. Scalability. Amazon SES can handle a high volume of emails, making it suitable for organizations with large email lists or that need to send a large number of emails on a regular basis.
   
2. Deliverability. SES uses machine learning and other techniques to help improve the deliverability of emails, increasing the likelihood that emails will be delivered to their intended recipients.
   
3. Reliability. SES has a 99.9% availability rate and automatically retries failed deliveries, helping to ensure that emails are delivered successfully.
   
4. Integration. SES can be easily integrated with other AWS services and third-party applications, allowing organizations to build custom email solutions or integrate email communication into their existing systems.