DEV Community

Cover image for Part-68: Global External Load balancer with HTTPS Self-signed certificate in GCP Cloud
Latchu@DevOps
Latchu@DevOps

Posted on

Part-68: Global External Load balancer with HTTPS Self-signed certificate in GCP Cloud

#googlecloud #devops #cloud #learning

Google Cloud - Global Application Load Balancer HTTPS

l0

Step-01: Introduction

Pre-requisite-1: Create Instance Templates, Create Managed Instance Groups as part of below demo

https://dev.to/latchudevops/part-67-mastering-google-cloud-global-load-balancers-regional-mig-global-http-demo-n98
Enter fullscreen mode Exit fullscreen mode

Pre-requisite-2: Create Self-Signed SSL Certificates
Create Global Application Load Balancer - HTTPS with Self-Signed SSL Certificates

Step-02: Pre-requisite-2: Create Self-Signed Certificates

# Create and Change Directory
mkdir  SSL-SelfSigned-Certs
cd SSL-SelfSigned-Certs

# Create your app1 key:
openssl genrsa -out app1.key 2048

# Create your app1 certificate signing request:
openssl req -new -key app1.key -out app1.csr -subj "/CN=app1.latchudevops.com"

# Create your app1 certificate:
openssl x509 -req -days 7300 -in app1.csr -signkey app1.key -out app1.crt
Enter fullscreen mode Exit fullscreen mode

l1

Step-03: Create Global HTTPS Load Balancer

  • Go to Network Services -> Load Balancing -> CREATE LOAD BALANCER
  • Select Application Load Balancer (HTTP/S): START CONFIGURATION
  • Internet facing or internal only: From Internet to my VMs or serverless services
  • Global or Regional: Global external Application Load Balancer
  • Load Balancer name: global-lb-external-https-selfsignedssl

l2

Frontend Configuration

  • Click on ADD FRONTEND IP AND PORT
  • Name: frontend-https-selfsignedssl
  • Description: frontend-https-selfsignedssl
  • Protocol: HTTPS
  • IP Version: IPv4
  • IP Address: global-lb-ip2 CREATE NEW EXTERNAL STATCI IP
  • Port: 443

l3

UPLOAD SELF-SIGNED CERTIFICATE

l4

  • Click on CREATE A NEW CERTIFICATE
  • NAME: app1-ssl-self-signed
  • Description: app1-ssl-self-signed
  • Click on CREATE
  • Enable HTTP to HTTPS Redirect: enabled
  • Click on DONE

l5

l6

Backend Configuration

l7

  • CLick on CREATE A BACKEND SERVICE
  • Name: mybackend-svc1
  • Description: mybackend-svc1
  • Backend type: Instance Group
  • Protocol: HTTP
  • Named Port: webserver80 (AUTO-POPULATED WHEN BACKEND IS SELECTED AS mig1-lbdemo)
  • Timeout: 30
  • BACKENDS 
Instance Group: mig1-us-central1
Port Numbers: 80
REST ALL LEAVE TO DEFAULTS
Click on DONE
Instance Group: mig1-us-east1
Port Numbers: 80
REST ALL LEAVE TO DEFAULTS
Click on DONE
Enter fullscreen mode Exit fullscreen mode
  • Disable Cloud CDN
  • Health Check: http-health-check
  • Security: 
Cloud Armor backend security policy: NONE
Enter fullscreen mode Exit fullscreen mode
  • Click on CREATE

Routing Rules

  • Mode: Simple host and path rule
  • REST ALL LEAVE TO DEFAULTS

Review and Finalize

  • Review all settings
  • Click on CREATE

Step-04: Verify Load Balancer

l18

  • Go to Network Services -> Load Balancing -> global-lb-external-https selfsigned

l19

  • Review the Tabs 
LOAD BALANCERS
BACKENDS
FRONTENDS
Enter fullscreen mode Exit fullscreen mode

l20

Step-05: Verify SSL Certificate in Certificate Manager

Goto Security -> Certificate Manager -> Data Protection
Click on CLASSIC CERTIFICATES -> app1-ssl-self-signed

l21

Step-06: Access Application using LB IP on browser

Important Note: WAIT FOR 3 to 5 Minutes before Load Balancer is fully operational

# Access Application - HTTP
http://LB-IP
Observation: Should redirect to HTTPS URL

# Access Application - HTTPS
https://LB-IP
Enter fullscreen mode Exit fullscreen mode

l22

Step-07: Delete Load Balancer

Delete the Load balancer created as part of this demo and dont delete the Backend services

l23

🌟 Thanks for reading! If this post added value, a like ❤️, follow, or share would encourage me to keep creating more content.

— Latchu | Senior DevOps & Cloud Engineer

☁️ AWS | GCP | ☸️ Kubernetes | 🔐 Security | ⚡ Automation
📌 Sharing hands-on guides, best practices & real-world cloud solutions

Top comments (0)