Add ApiGateway Support for EKS as AWS_PROXY Integration

I apologize, but there seems to be a misunderstanding in your request. Currently, Amazon API Gateway does not offer direct integration with Amazon EKS (Elastic Kubernetes Service) as an AWS_PROXY integration.

API Gateway's AWS service integrations are typically used for AWS services that have REST APIs, like DynamoDB or Lambda. EKS, on the other hand, uses the Kubernetes API, which is not directly compatible with API Gateway's integration model.

To expose EKS cluster metadata to external systems securely, you would need to use alternative approaches:

1. Use AWS Lambda: You can create a Lambda function that interacts with the EKS API using the AWS SDK. This Lambda function can then be integrated with API Gateway.

2. Use EC2 instances or EKS nodes: You can set up a proxy server on EC2 or within your EKS cluster that can handle the API requests and forward them to the EKS API.

3. Direct access: For secure direct access, you would typically use the kubectl command-line tool or the Kubernetes API directly, with proper authentication and authorization set up.

4. AWS CLI or SDK: For programmatic access to EKS cluster metadata, you can use the AWS CLI or SDKs, which handle the signed requests to the EKS API.

These methods would allow you to perform actions like ListClusters and DescribeCluster securely. While they may introduce some overhead, they ensure proper authentication and authorization when accessing EKS resources.

It's worth noting that exposing cluster metadata directly to external systems should be done cautiously and with proper security measures in place, regardless of the method used.
Sources
Control network access to cluster API server endpoint - Amazon EKS
Create and manage Amazon EKS clusters with Step Functions - AWS Step Functions