Skip to main content

Setting up Email Address in AWS - Workmail

Hi all,

Today I came up with a situation to create email address in AWS and landed in AWS Workmail.

Prerequisites: Domain Registrar login details for updating the NS or Dns records. If your registrar is not providing dns management then use the AWS Route53 service for managing the dns records.

In this service we need to setup this as below:

1) Create an Organization. The Web application url  will have a tail end like .awsapps.com/mail . If your organization is abc then the workmail web application url will be like https://abc.awsapps.com/mail



2) After creating the organization you need to click on it and now create the Domain for email address.



3) Once you create the domain , it should be verified by adding the TXT dns records and the remaining MX, CNAME and SPF records in the dns management (Route53)

        > Verify domain ownership (required)
        > Finalize mail setup (required)
        > Increase security (recommended)

It will take 5 to 10 Minutes for the dns entries to be get verified. So after adding the entries please wait for some time before clicking on the refresh button.

4) Once the domain is verified you can create the user, which is email addresses.



5) Finally configure the email id in your thunderbird.


6) Please see the dns entries as below:


In thunderbird select SSL/TLS with Normal Password. That is all. Happy mailing.

Comments

Popular posts from this blog

K8s External Secrets integration between AWS EKS and Secrets Manager(SM) using IAM Role.

What is K8s External Secrets and how it will make your life easier? Before explaning about External Secrets we will first look into the k8s secrets and how it will work. In k8s secrets we will create key value pairs of the secrets and set this as either pod env variables or mount them as volumes to pods. For more details about k8s secrets you can check my blog http://jinojoseph.blogspot.com/2020/08/k8s-secrets-explained.html   So in this case if developers wants to change the ENV variables , then we have to edit the k8s manifest yaml file, then we have to apply the new files to the deployment. This is a tiresome process and also chances of applying to the wrong context is high if you have multiple k8s clusters for dev / stage and Prod deployments. So in-order to make this easy , we can add all the secrets that is needed in the deployment, in the AWS Secret Manager and with the help of External secrets we can fetch and create those secrets in the k8s cluster. So what is K8s external...

ELK Stack with Filebeat using Docker Containers

ubuntu@master:~$ git clone https://github.com/deviantony/docker-elk.git ubuntu@master:~$ cd docker-elk ubuntu@master:~/docker-elk$ sudo docker-compose up -d Creating dockerelk_elasticsearch_1 ... done WARNING: Image for service kibana was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`. Creating dockerelk_elasticsearch_1 ... Creating dockerelk_logstash_1      ... done Creating dockerelk_kibana_1        ... done ubuntu@master:~/docker-elk$ sudo docker-compose ps           Name                         Command               State                                   Ports                      ...

K8s Secrets Explained.

 What is Secrets in K8s? Secrets are used to store sensitive information like Authentication Token, Passwords, SSH Keys and  Certificates. It is stored in etcd, datastore of k8s. The main advantage of the secret is that it can be updated dynamically , so if we want to change the username or password or ssh key of any of the containers inside the pod, then just changing the secret will dynamically update the existing and newely created POD's env values and ssh-key (mount as volume) . jinojosep@cloudshell:~ (boreal-physics-256910)$ kubectl create secret generic secret-demo --from-literal=username=jinouname --from-literal=password=jinomypassword secret/secret-demo created ################################ jinojosep@cloudshell:~ (boreal-physics-256910)$ kg secret NAME                  TYPE                                  DATA   AGE default-tok...