allow eks_public_access_cidrs to be optionally set in nebari-config.yaml

[dcmcand]

Reference Issues or PRs

closes #2881

What does this implement/fix?

adds ability to specify aws.eks_public_access_cidr in your nebari-config.yaml

Put a x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features not to work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

• Did you test the pull request locally?
• Did you add new tests?

How to test this PR?

Deploy to AWS

Go to the EKS console and under the networking tab, check that Public access source allowlist says "0.0.0.0/0"

add eks_public_access_cidrs: ["{YOUR_PUBLIC_IP}/32"] to your config under the AWS object

ex:

amazon_web_services:
  kubernetes_version: '1.31'
  region: us-east-2
  eks_public_access_cidrs: ["12.345.678.910/32"]
  node_groups:
    general:
      instance: m5.2xlarge
      min_nodes: 1
      max_nodes: 1
      gpu: false
      single_subnet: false
      permissions_boundary:
    user:
      instance: m5.xlarge
      min_nodes: 0
      max_nodes: 5
      gpu: false
      single_subnet: false
      permissions_boundary:
    worker:
      instance: m5.xlarge
      min_nodes: 0
      max_nodes: 5
      gpu: false
      single_subnet: false
      permissions_boundary:

Redeploy

Go to the EKS console and check that Public access source allowlist now reflects your configured range

Any other comments?

This is also feature parity for Azure and GCP