Context root redirect for AWS Application Load Balancer using terraform

See also questions close to this topic

• (Terraform) Error 400: Invalid request: instance name (pg_instance)., invalid

  On GCP, I'm trying to create a Cloud SQL instance with this Terraform code below:

  resource "google_sql_database_instance" "postgres" {
      name                = "pg_instance"
      database_version    = "POSTGRES_13"
      region              = "asia-northeast1"
      deletion_protection = false
  
      settings {
          tier      = "db-f1-micro"
          disk_size = 10
      }
  }
  
  resource "google_sql_user" "users" {
      name     = "postgres"
      instance = google_sql_database_instance.postgres.name
      password = "admin"
  }
  

  But I got this error:

  Error: Error, failed to create instance pg_instance: googleapi: Error 400: Invalid request: instance name (pg_instance)., invalid

  Are there any mistakes for my Terraform code?
• How does Kubernetes and Terraform work seamlessly together and what role do they each undertake?

  I am a bit confused about the individual roles of Kubernetes and Terraform when using them both on a project.

  Until very recently, I had a very clear understanding of both their purposes and everything made sense to me. But, then I heard in one of Nana's videos on Terraform, that Terraform was also very advanced in orchestration and I got confused.

  Here's my current understanding of both these tools:

  • Kubernetes: Orchestration software that controls many docker containers working together seamlessly. Kubernetes makes sure that new containers are deployed based on the desired infrastructure defined in configuration files (written with the help of a tool like Terraform, as IaC).

  • Terraform: Tool for provisioning, configuring, and managing infrastructure as IaC.

  So, when we say that Terraform is a good tool for orchestration, do we mean that it's a good tool for orchestrating infrastructure states or docker containers as well?

  I hope someone can clear that out for me!
• terraform for loop list for target_groups with a combine variable

  Is there a way to use the below list in a for loop and add in the target_groups ? I am trying to use the prefix with target_groups variable in a for-loop. I have tested also for_each. The target_groups expects the list format but the for_each does not give that expected result.

  variable "prefix" {
    description = "NLB Prefix"
    type        = any
    default = "test-target"
  }
  
  variable "target_groups" {
    description = "NLB"
    type        = any
    default = {
      tg1 = {
        name_prefix          = "test"
        backend_protocol     = "TCP"
        backend_port         = 443
        target_type          = "ip"
        deregistration_delay = 10
        preserve_client_ip   = true
        stickiness = {
          enabled = true
          type    = "source_ip"
        }
        targets = {
          appl1 = {
            target_id = "191.11.11.11"
            port      = 443
          }
        }
      },
      }
    }
  }
  

  I tried the list below for_each

  module "g-appl_nlb" {
    source = "../../modules/compute/lb"
  
    name               = format("%s-g-appl-nlb", var.name_prefix)
    load_balancer_type = "network"
    vpc_id             = data.aws_vpc.target_vpc.id
    ...
  
    target_groups = [
  
      for_each = var.target_groups 
        name_previs          = var.prefix
        backend_protocol     = each.value["backend_protocol"]
        backend_port         = each.value["backend_port"]
        target_type          = each.value["target_type"]
        deregistration_delay = each.value["deregistration_delay"]
        preserve_client_ip   = each.value["preserve_client_ip"]
        stickiness           = each.value["stickiness"]
    ]
  ....
  
  
• Terraform is throwing InvalidArgumentException Duplicate ProcessorParameter passed to ProcessingConfiguration on Kinesis Firehose dynamic partitioning

  I'm trying to create a Kinesis Firehose using terraform with dynamic partitioning using two partition queries from the JSON I'm recieving, my processing configuration looks like this

  processing_configuration {
    enabled = true
    processors {
      type = "RecordDeAggregation"
      parameters {
        parameter_name  = "SubRecordType"
        parameter_value = "JSON"
      }
    }
    processors {
      type = "MetadataExtraction"
      parameters {
        parameter_name  = "JsonParsingEngine"
        parameter_value = "JQ-1.6"
      }
      parameters {
        parameter_name  = "MetadataExtractionQuery"
        parameter_value = "{transaction_id:.transaction_id}"
      }
      parameters {
        parameter_name  = "MetadataExtractionQuery"
        parameter_value = "{stage:.stage}"
      }
    }
  }
  

  But when I execute this part of the code it returns a duplication error for the processing configuration.

  I also tried to create an appart processor for the new ExtractionQuery, it looks like this

  processing_configuration {
    enabled = true
    processors {
      type = "RecordDeAggregation"
      parameters {
        parameter_name  = "SubRecordType"
        parameter_value = "JSON"
      }
    }
    processors {
      type = "MetadataExtraction"
      parameters {
        parameter_name  = "JsonParsingEngine"
        parameter_value = "JQ-1.6"
      }
      parameters {
        parameter_name  = "MetadataExtractionQuery"
        parameter_value = "{transaction_id:.transaction_id}"
      }
    }
    processors {
      type = "MetadataExtraction"
      parameters {
        parameter_name  = "JsonParsingEngine"
        parameter_value = "JQ-1.6"
      }
      parameters {
        parameter_name  = "MetadataExtractionQuery"
        parameter_value = "{stage:.stage}"
      }
    }
  }
  

  But it fails with an error that says only one MetadataExtraction processor is allowed.
• setting up Application load balancer with Global accelerator with Nginx target group upstream to IIS

  I have set up an application Load balancer with Global accelerator and Nginx Proxy pass to different IIS upstream based upon hostname. The website works well and can access the websites globally. some times customers had issues accessing websites with 500 error codes. we have an error logger configured with our app we can see double IP addresses in ROMOTE_ADDR for some of the request

  For requests with double ip addresses, it throws a 500 Internal server error. and other request with single IP address are good

  nginx.conf

  proxy_set_header        Host $host;
    proxy_set_header        Connection "";
    proxy_set_header        X-Real-IP $http_x_forwarded_for;
    proxy_set_header        remote_addr $http_x_forwarded_for;
    proxy_set_header        X-Forwarded-For $http_x_forwarded_for;
    proxy_hide_header        Server;
    proxy_hide_header        X-Powered-By;
    proxy_hide_header        X-AspNet-Version;
    proxy_headers_hash_bucket_size 64;
  
    real_ip_header   X-Forwarded-For;
    set_real_ip_from 10.15.0.0/16;
    real_ip_recursive on;
  
  enter code here
  

  virtual host

  proxy_pass            http://www-servers;
      proxy_read_timeout    90;
      proxy_connect_timeout 90;
      proxy_http_version    1.1;
      proxy_set_header      Host $host;
      proxy_set_header      Connection "";
      proxy_set_header      X-Real-IP $http_x_forwarded_for;
      proxy_set_header      remote_addr $http_x_forwarded_for;
      proxy_set_header      X-Forwarded-For $http_x_forwarded_for;
      proxy_hide_header      Server;
      proxy_hide_header      X-Powered-By;
      proxy_hide_header      X-AspNet-Version;
  
  
  
  
  
  double ip address   -  Double IP Address: 72.194.29.174, 104.129.198.101
  

  sometimes there are three IP addresses

  Double IP Address: 73.223.72.109, 172.18.0.3, 64.62.158.119
  

  what header we can set to get the correct IP address and prevent some connection to log double ip's
• KeyCloak Mixed Configuration Issue with AWS ECS and ALB

  I am struggeling with a "smalL" problem during my ECS configuration.

  I have the following Infrastructure

  ECS Fargate (Serverless)

  1. Service which deploys 2 container (Application and KeyCloak)
  2. ALB with SSL enabled.

  When I open keyclauk.domain.de I am able to access keycloak. (I have attached an AWS Cert) When I try to access keycloak internally from application container to keycloak container I get an Error Message (Mixed Content: The page at 'url' was loaded over HTTPS, but requested an insecure resource 'url/auth'. This request has been blocked; the content must be served over HTTPS.)

  I already configured Service Discovery and trying to communicate through this own dns zone task.service which seems to work but still get this issue.

  Does anyone similar problems or advices?

  Thanks!