AWS PrivateLink provides private, low-latency connectivity between your Amazon VPC and supported AWS services without using the public internet. By leveraging VPC endpoints, you can enhance security, improve performance, and simplify network architecture.Documentation Index
Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt
Use this file to discover all available pages before exploring further.
AWS VPC Endpoint Types
AWS VPC endpoints come in two flavors:| Endpoint Type | Supported Services | Mechanism | Primary Use Case |
|---|---|---|---|
| Gateway Endpoint | Amazon S3, DynamoDB | Route tables | Private data access to S3/DynamoDB |
| Interface Endpoint | 100+ AWS services (Lambda, Kinesis, SNS, etc.) | Elastic Network Interfaces (ENIs) | Private API calls to AWS services |
Gateway endpoints are free of data processing charges, whereas interface endpoints incur hourly and per-GB data processing fees.
Gateway Endpoint: Accessing Amazon S3 Privately
To keep traffic between your VPC and Amazon S3 entirely on the AWS network, create a gateway endpoint:Gateway endpoints support only Amazon S3 and DynamoDB. For other services, use interface endpoints.
Interface Endpoint: Calling AWS Lambda Privately
When your applications need to invoke Lambda functions without leaving the AWS backbone, deploy an interface endpoint:
Links and References
- AWS PrivateLink Documentation
- VPC Endpoints Overview
- Amazon S3 User Guide
- AWS Lambda Developer Guide