- 최신
- 최다 투표
- 가장 많은 댓글
Although Amazon VPC supports multicast via AWS Transit Gateway, AWS Lambda does not directly support sending or receiving multicast messages. When you connect a Lambda function to a VPC, it receives an Elastic Network Interface (ENI) with a private IP address, allowing it to communicate with other VPC resources.
Lambda functions, on the other hand, are designed to be stateless, event-driven compute services that do not support multicast messaging patterns such as group communication or network broadcasting. Multicast is typically used in scenarios requiring one-to-many or many-to-many communication, whereas Lambda functions are typically triggered by specific events or API calls.
If your application requires multicast communication, you may need to consider an alternative solution, such as running your code on Amazon EC2 instances within your VPC. This way, you can take full advantage of AWS Transit Gateway's multicast support.
So, the ENI recieved by the AWS Lambda does not allow the multicast messages to arrive?
No, because Lambda is event-driven, not packet-driven. It doesn't support setting up a network listener - that is, opening up a port and listening for inbound connections.