Feat: enable multi-region deployments and fix FluentBit configuration support

[novekm]

What does this PR do?

This PR enables multi-region performance workloads by upgrading to AWS Provider v6 and adding native multi-region support. It includes three key enhancements:

1. AWS Provider v6 Upgrade - Enables enhanced multi-region resource management
2. Multi-Region Deployment Support - Adds region variable for cross-region deployments
3. FluentBit Configuration Fix - Adds missing configuration_values parameter support

These changes specifically target performance-critical workloads like Unreal Cloud DDC and Perforce that require multi-region deployments for performance optimization (not just disaster recovery), but also provides benefits in general.

Motivation

Business Need: Organizations deploying performance-critical workloads need multi-region EKS clusters for:

• 🎮 Unreal Cloud DDC: Game developers require DDC clusters in multiple regions for faster Unreal Engine workflows through cached derived data
• 🔧 Perforce: Development teams need Perforce edge servers across regions for code sync performance
• 🏗️ Global Development Teams: Engineering teams across regions need local build clusters for faster compilation and testing

Current Limitations:

• Single-region deployment assumption in current module
• AWS Provider v5 constraints make multi-region resource management cumbersome
• FluentBit configuration_values parameter ignored, forcing manual helm commands

Real-World Testing: Successfully tested in production environment with multi-region Unreal DDC deployment using terraform init -upgrade - no compatibility issues encountered.

Technical Changes

🌍 Multi-Region Support

• New: region variable for explicit region override
• Benefit: Deploy EKS addons to different regions within same Terraform state
• Usage:

  # US East cluster
  module "addons_us_east" {
    source = "aws-ia/eks-blueprints-addons/aws"
    region = "us-east-1"
    cluster_name = "ddc-us-east"
  }
  
  # EU West cluster  
  module "addons_eu_west" {
    source = "aws-ia/eks-blueprints-addons/aws"
    region = "eu-west-1" 
    cluster_name = "ddc-eu-west"
  }

🔧 AWS Provider v6 Upgrade

• Files: versions.tf, tests/complete/versions.tf, README.md
• Benefit: Better multi-region networking, IAM, and resource dependencies
• Impact: Enables complex multi-region architectures in single Terraform state

🐛 FluentBit Configuration Fix

• Problem: Custom configuration_values ignored, forcing manual helm commands
• Solution: Merge configuration_values with existing values parameter
• Usage:

  aws_for_fluentbit = {
    configuration_values = jsonencode({
      cloudWatchLogs = {
        logGroupName = "/aws/eks/cluster/application/custom"
      }
    })
  }

📦 Provider Updates

• Helm: >= 2.16.0, < 3.0.0 (compatible with child modules)
• Kubernetes: >= 2.33.0 (improved multi-cluster management)

Breaking Changes

⚠️ AWS Provider v6 Required - This is a major version bump

Migration Benefits:

• Multi-region capabilities for performance workloads
• Better resource management across regions
• Future-proofing for AWS service evolution
• Enhanced security and stability

Migration Path:

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = ">= 6.0"
    }
  }
}

More

• Yes, I have tested the PR using my local account setup (Successfully deployed multi-region Unreal DDC infrastructure with terraform init -upgrade - no compatibility issues)
• Yes, I ran pre-commit run -a with this PR

Additional Notes

Test Evidence:

• Deployed to production environment with multi-region EKS clusters
• Validated FluentBit configuration_values functionality with custom log group configuration
• Confirmed compatibility with existing child modules (aws-ia/eks-blueprints-addon/aws v1.1.1)
• No version conflicts encountered during provider upgrades

For Moderators

• E2E Test successfully complete before merge?

Additional Notes