Based on the research, here's what you need to do to enable AWS PrivateLink with Prefect Cloud:
1.
Prerequisites:
- You must have a Prefect Cloud Enterprise plan that includes PrivateLink support
- You'll need your AWS Account Number
- You'll need the AWS VPC IDs where your EKS clusters are running
- You'll need to know the source region for each VPC
2.
Setup Process:
1. Contact Prefect's sales or support team to initiate the PrivateLink setup process
2. They will provide you with the necessary service endpoint details for your configuration
3. You'll need to provide them with:
- Your AWS Account Number
- VPC IDs
- Source regions for each VPC
- VPC Endpoint ID (once created)
4. After creating the endpoint, you'll need to enable 'Modify Private DNS' to complete the setup
3.
Post-Setup:
- Once the connection is accepted and configured by the Prefect team, all traffic between your EKS workers and Prefect Cloud will be routed through PrivateLink
- This ensures that all communication is encrypted and stays within the AWS network, never touching the public internet
For detailed documentation and the most up-to-date information, you can refer to the
Prefect documentation on PrivateLink.
Since this is an Enterprise feature, I recommend reaching out to your Prefect account representative or support team to begin the process. They will be able to provide you with specific endpoint details and guide you through the setup process for your particular environment.
Would you like me to provide more specific details about any part of this process?