Example: Manage IGMP configurations using Amazon VPC Transit Gateways
This example shows at least one host that uses the IGMP protocol for multicast traffic.
AWS automatically creates the multicast group when it receives an IGMP JOIN
message from an instance, and then adds the instance as a member in this group. You can also
statically add non-IGMP hosts as members to a group using the AWS CLI. Any instances that are in
subnets associated with the multicast domain can send traffic, and the group members receive the
multicast traffic.
Use the following steps to complete the configuration:
-
Create a VPC. For more information about creating VPCs, see Creating a VPC in the Amazon VPC User Guide.
-
Create a subnet in the VPC. For more information about creating subnets, see Creating a subnet in your VPC in the Amazon VPC User Guide.
-
Create a transit gateway configured for multicast traffic. For more information, see Create a transit gateway using Amazon VPC Transit Gateways.
-
Create a VPC attachment. For more information, see Create a VPC attachment using Amazon VPC Transit Gateways.
-
Create a multicast domain configured for IGMP support. For more information, see Create an IGMP multicast domain using Amazon VPC Transit Gateways.
Use the following settings:
-
Enable IGMPv2 support.
-
Disable Static sources support.
-
-
Create an association between subnets in the transit gateway VPC attachment and the multicast domain. For more information see Associating VPC attachments and subnets with a multicast domain using Amazon VPC Transit Gateways.
-
The default IGMP version for EC2 is IGMPv3. You need to change the version for all IGMP group members. You can run the following command:
sudo sysctl net.ipv4.conf.eth0.force_igmp_version=2 -
Add the members that do not use the IGMP protocol to the multicast group. For more information, see Register members with a multicast group using Amazon VPC Transit Gateways.
