Skip to main content

Generating SSL Certificate with Namecheap and ELB assigning using ACM

First Generate a Private Key for SSL: This I am doing from the web server.

# openssl genrsa -out gateway_key.pem 2048

Now generate a csr with using the above key:

# root@ip-10-0-3-90:~# openssl req -new -sha256 -key gateway_key.pem -out gateway_key.csr
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [AU]:JP
State or Province Name (full name) [Some-State]:XXXX
Locality Name (eg, city) []:XXXX
Organization Name (eg, company) [Internet Widgits Pty Ltd]:XXXX Co Ltd
Organizational Unit Name (eg, section) []:XXXX
Common Name (e.g. server FQDN or YOUR name) []:gateway.X-XXXX.net
Email Address []:admin@X-XXXX.net

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:
An optional company name []:
root@ip-10-0-3-90:~#

Now Login to namecheap and Click on the SSLCertificate "Activation" link.

There you have to paste the gateway_key.csr content. Click Next.

Give the email id admin@X-XXXX.net for sending the activation email. Click Next.

This will send an activation email to admin@X-XXXX.net and click on that activation link and copy past the validation code in the activation url.

Now namecheap will send you the SSL certificate to the email id admin@X-XXXX.net

Now login to your AWS and take the ACM service and click on Import ssl certificate.

Here give the certificate and gateway_key.pem content.

Now click on review and import button. This will review and save the ssl certificate in ACM.

Now go to ELB and click on "Listeners" . There click on edit and change the SSL certificate that we just now added for the ELB.

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...

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...

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                      ...