Skip to content

NimTechnology

Trình bày các công nghệ CLOUD một cách dễ hiểu.

  • Kubernetes & Container
    • Docker
    • Kubernetes
      • Ingress
      • Pod
    • Helm Chart
    • OAuth2 Proxy
    • Isito-EnvoyFilter
    • Apache Kafka
      • Kafka
      • Kafka Connect
      • Lenses
    • Vault
    • Longhorn – Storage
    • VictoriaMetrics
    • MetalLB
    • Kong Gateway
  • CI/CD
    • ArgoCD
    • ArgoWorkflows
    • Argo Events
    • Spinnaker
    • Jenkins
    • Harbor
    • TeamCity
    • Git
      • Bitbucket
  • Coding
    • DevSecOps
    • Terraform
      • GCP – Google Cloud
      • AWS – Amazon Web Service
      • Azure Cloud
    • Golang
    • Laravel
    • Python
    • Jquery & JavaScript
    • Selenium
  • Log, Monitor & Tracing
    • DataDog
    • Prometheus
    • Grafana
    • ELK
      • Kibana
      • Logstash
  • BareMetal
    • NextCloud
  • Toggle search form

[AWS] Configure Ingress SSL and SSL Redirect on Load Balancer Controller

Posted on November 18, 2022 By nim No Comments on [AWS] Configure Ingress SSL and SSL Redirect on Load Balancer Controller

Chúng ta cũng đã biết cách tạo ingress trên eks là như thế nào.
Nhưng giờ chúng ta cần add thêm SSL vào trong ingress của Load Balancer Controller

Contents

Toggle
  • 1) Overview
  • 2) Demo
    • 2.1) Prepare system
      • 2.1.1) Install eks cluster
      • 2.1.2) Install Load Balancer Controller
  • 2.2) Install ACM Certificate by terraform

1) Overview

Bước 1: mua domain trên Route53 hoặc bất cứ đâu.
Bước 2 là tạo Certificate Manager.
Bước 3: Update ssl và ssl redirect on annotation của ingress
Đây là mô hình ssl và https redirect.
Để có ssl trong website thì chúng ta sẽ cần chú ý các mục trên ở phần ingress.

2) Demo

2.1) Prepare system

2.1.1) Install eks cluster

Đầu tiên bạn cần dựng được 1 eks cluster:
https://github.com/mrnim94/terraform-aws/tree/master/eks/AWS-EKS-Cluster-Basics
và đầu là 1 bài viết về dụng eks cluster bằng terraform.
https://nimtechnology.com/2022/08/21/aws-create-eks-node-groups-in-public-and-private-subnets/

2.1.2) Install Load Balancer Controller

Tiếp theo bạn cần cài đặt Load Balancer Controller
https://github.com/mrnim94/terraform-aws/tree/master/eks-ingress/EKS-with-LoadBalancer-Controller/lbc-install-terraform-manifests
Bạn có thể tham khảo bài này:
https://nimtechnology.com/2022/09/13/aws-aws-load-balancer-controller-and-ingress-are-installed-by-terraform-helm-provider-on-eks/

2.2) Install ACM Certificate by terraform

c11-acm-certificate.tf
>>>>

# Resource: ACM Certificate
resource "aws_acm_certificate" "acm_cert" {
  domain_name       = "*.nimtechnology.com"
  validation_method = "DNS"

  tags = {
    Environment = "dev"
  }

  lifecycle {
    create_before_destroy = true
   }
}

# Outputs
output "acm_certificate_id" {
  value = aws_acm_certificate.acm_cert.id 
}

output "acm_certificate_arn" {
  value = aws_acm_certificate.acm_cert.arn
}

output "acm_certificate_status" {
  value = aws_acm_certificate.acm_cert.status
}

https://github.com/mrnim94/terraform-aws/tree/master/ingress-ssl-terraform-manifests

Mình đã tạo được ACM
Giờ mình trở lại trang mà mình mua domain để add CNAME
ACM đã được verify
root@LP11-D7891:~# kubectl get all
NAME                                         READY   STATUS    RESTARTS   AGE
pod/app1-nginx-deployment-777cddb9b4-h6km5   1/1     Running   0          63s
pod/app2-nginx-deployment-577bf469f7-5nd2j   1/1     Running   0          63s
pod/app3-nginx-deployment-6988d859c5-8lwwx   1/1     Running   0          63s

NAME                                  TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE
service/app1-nginx-nodeport-service   NodePort    172.20.108.228   <none>        80:30031/TCP   55s
service/app2-nginx-nodeport-service   NodePort    172.20.124.205   <none>        80:31908/TCP   55s
service/app3-nginx-nodeport-service   NodePort    172.20.239.172   <none>        80:31545/TCP   55s
service/kubernetes                    ClusterIP   172.20.0.1       <none>        443/TCP        120m

NAME                                    READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/app1-nginx-deployment   1/1     1            1           68s
deployment.apps/app2-nginx-deployment   1/1     1            1           68s
deployment.apps/app3-nginx-deployment   1/1     1            1           68s

NAME                                               DESIRED   CURRENT   READY   AGE
replicaset.apps/app1-nginx-deployment-777cddb9b4   1         1         1       69s
replicaset.apps/app2-nginx-deployment-577bf469f7   1         1         1       69s
replicaset.apps/app3-nginx-deployment-6988d859c5   1         1         1       69s
root@LP11-D7891:~# kubectl get ingress
NAME               CLASS                  HOSTS   ADDRESS                                                  PORTS   AGE
ingress-ssl-demo   my-aws-ingress-class   *       ingress-ssl-demo-236734605.us-east-1.elb.amazonaws.com   80      74s
Nếu bạn lấy ingress trong domain để vào thì sẽ thấy đỏ đỏ như hình
Vì cert chúng ta đã ký với *.nimtechnology.com
Tạo domain mới và CNAME vào ingress
OK. tất cả OK
AWS - Amazon Web Service

Post navigation

Previous Post: [AWS] Creating AWS Certificate Manager (ACM)
Next Post: [AWS] Creat Persistent Volume on EKS via EBS.

More Related Articles

[EKS] Adjusting things to migrate EKS legacy to new versions. AWS - Amazon Web Service
[Terraform] – Terraform Beginner – Lesson 8: Terraform Functions and Conditional Expressions AWS - Amazon Web Service
[EFS/EKS] Warning: config file does not have retry_nfs_mount_command item in section mount… AWS - Amazon Web Service
[ElastiCache] Provisioning Redis on AWS so quickly by terraform AWS - Amazon Web Service
[AWS] Setup Schedule Action for Auto Scaling Group – Saving Cost is based on ASG AWS - Amazon Web Service
[Demo] Instructing configure AssumeRole – IAM on AWS AWS - Amazon Web Service

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Tham Gia Group DevOps nhé!
Để Nim có nhiều động lực ra nhiều bài viết.
Để nhận được những thông báo mới nhất.

Recent Posts

  • [Azure] The subscription is not registered to use namespace ‘Microsoft.ContainerService’ May 8, 2025
  • [Azure] Insufficient regional vcpu quota left May 8, 2025
  • [WordPress] How to add a Dynamic watermark on WordPress. May 6, 2025
  • [vnet/Azure] VNet provisioning via Terraform. April 28, 2025
  • [tracetcp] How to perform a tracert command using a specific port. April 3, 2025

Archives

  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021

Categories

  • BareMetal
    • NextCloud
  • CI/CD
    • Argo Events
    • ArgoCD
    • ArgoWorkflows
    • Git
      • Bitbucket
    • Harbor
    • Jenkins
    • Spinnaker
    • TeamCity
  • Coding
    • DevSecOps
    • Golang
    • Jquery & JavaScript
    • Laravel
    • NextJS 14 & ReactJS & Type Script
    • Python
    • Selenium
    • Terraform
      • AWS – Amazon Web Service
      • Azure Cloud
      • GCP – Google Cloud
  • Kubernetes & Container
    • Apache Kafka
      • Kafka
      • Kafka Connect
      • Lenses
    • Docker
    • Helm Chart
    • Isito-EnvoyFilter
    • Kong Gateway
    • Kubernetes
      • Ingress
      • Pod
    • Longhorn – Storage
    • MetalLB
    • OAuth2 Proxy
    • Vault
    • VictoriaMetrics
  • Log, Monitor & Tracing
    • DataDog
    • ELK
      • Kibana
      • Logstash
    • Fluent
    • Grafana
    • Prometheus
  • Uncategorized
  • Admin

Copyright © 2025 NimTechnology.