Enhanced networking with the Elastic Network Adapter (ENA)

[felipe-vvoosh]

Please, can you make your AMIs compatible with ENA?

All the new instance types enforce this now...

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html

[tboyko]

Second this. In fact, some EC2 instance types like c5 and m5 require that ENA support is available. Following these directions to add ENA support to the Graylog AMI image we started with does not work. The EC2 instance fails to boot after enabling ENA and starting on an instance type that uses ENA.

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking-ena.html#enhanced-networking-ena-ubuntu

[malcyon]

Hello,

I am just looking through old tickets. I see in the documentation linked above, it says:

The latest AMIs for Red Hat Enterprise Linux, SUSE Linux Enterprise Server, and CentOS include the module required for enhanced networking with ENA and have ENA support enabled.

Since we're on Ubuntu 18.04.5 LTS now, I wondered if the status on ENA has changed. I launched an EC2 instance using the latest AMI. I made sure that the instance I launched was a c5 instance.

My c5 instance did boot up successfuly. After I logged into it, I ran through the "Test whether enhanced networking is enabled" section of the above documentation. I can see that the kernel module is enabled:

ubuntu@graylog:~$ modinfo ena
filename:       /lib/modules/5.4.0-1037-aws/kernel/drivers/net/ethernet/amazon/ena/ena.ko
license:        GPL
description:    Elastic Network Adapter (ENA)
author:         Amazon.com, Inc. or its affiliates
srcversion:     3E413E910958805060F698C
alias:          pci:v00001D0Fd0000EC21sv*sd*bc*sc*i*
alias:          pci:v00001D0Fd0000EC20sv*sd*bc*sc*i*
alias:          pci:v00001D0Fd00001EC2sv*sd*bc*sc*i*
alias:          pci:v00001D0Fd00000EC2sv*sd*bc*sc*i*
alias:          pci:v00001D0Fd00000051sv*sd*bc*sc*i*
depends:        
retpoline:      Y
intree:         Y
name:           ena
vermagic:       5.4.0-1037-aws SMP mod_unload 
signat:         PKCS#7
signer:         
sig_key:        
sig_hashalgo:   md4
parm:           debug:Debug level (0=none,...,16=all) (int)

And the enaSupport attribute is set on the EC2 instance:

donald@laptop:~$ aws ec2 describe-instances --instance-ids i-0452ef5afadb06a6c --query "Reservations[].Instances[].EnaSupport"
[
    true
]

However, the network interface driver is not set correctly:

ubuntu@graylog:~$ ethtool -i eth0
driver: vif
version: 
firmware-version: 
expansion-rom-version: 
bus-info: vif-0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

I have not read through all the documentation. These are just my notes from poking around.