What if you want to assign static, private IP addresses to instances in an auto scaling group, and you do not want to use a load balancer? nor grant permissions to attach network interfaces in a startup script? Enter the network interface manager, which manages the assignment of a pool of network interfaces to instances!
The network interface manager, manages the assignment of a pool of network interfaces to instances. When the instance is stopped or terminated, the interface is removed. When a new instance is started, an interface from the pool is assigned to it.
The manager will listen to all EC2 instance state change notifications. When an instance with the tag
reaches the state running, it will assign a free network interface with the same tag and tag value in it’s subnet.
The manager also syncs the state every 5 minutes, to ensure that we are eventually consistent in the face of errors.
You can start using the network interface manager, in three simple steps:
To deploy the provider, type:
git clone https://github.com/binxio/ec2-network-interface-manager.git cd ec2-network-interface-manager aws cloudformation create-stack \ --capabilities CAPABILITY_IAM \ --stack-name network-interface-manager \ --template-body file://./cloudformation/network-interface-manager.yaml aws cloudformation wait stack-create-complete --stack-name network-interface-manager
Create a pool of network interfaces, and tag them with an
InterfaceAZ1: Type: AWS::EC2::NetworkInterface Properties: Tags: - Key: network-interface-manager-pool Value: bastion InterfaceAZ2: Type: AWS::EC2::NetworkInterface Properties: Tags: - Key: network-interface-manager-pool Value: bastion
Create an auto scaling group and apply the tag
network-interface-manager-pool to all the instances:
AutoScalingGroup: Type: AWS::AutoScaling::AutoScalingGroup Properties: ... Tags: - Key: network-interface-manager-pool Value: bastion PropagateAtLaunch: true
The manager will automatically associate network interfaces to instance tagged with
network-interface-manager-pool. It does
this by subscribing to EC2 state change events. It will not do anything on instances without the
network-interface-manager-pool. The network interface manager also syncs the state every 5 minutes, to ensure that we are eventually
consistent in the face of errors.
That is all. If you want to see it all in action, deploy the demo.
In order to deploy the demo, type:
read -p "vpc id: " VPC_ID read -p "three subnet ids: " SUBNET_IDS aws cloudformation create-stack \ --capabilities CAPABILITY_NAMED_IAM \ --stack-name network-interface-manager-demo \ --template-body file://./cloudformation/demo-stack.yaml \ --parameter Name=VPC,Value=$VPC_ID Name=Subnets,Value=$SUBNET_IDS aws cloudformation wait stack-create-complete --stack-name network-interface-manager-demo
As network interfaces are bound to an availability zone, the auto scaling group should also be tied to a single availability zone. Otherwise. instances can be rescheduled in another AZ leaving the network interfaces from the pool unattached.
There are two alternative solutions to achieve the same functionality:
In my use case, I did not want to spent money on keeping an NLB running nor give the instance all the permissions to attach network interfaces.
With the network interface manager, you can dynamically bind a range of static, private IP addresses to auto scaling group instances. If you are looking for binding Elastic IPs, you can use the EC2 elastic IP manager.