Error running nitro enclave allocator

[blmalone]

Error message:

[ec2-user@ip-172-16-1-154 ~]$ sudo systemctl status nitro-enclaves-allocator.service
● nitro-enclaves-allocator.service - Nitro Enclaves Resource Allocator
   Loaded: loaded (/usr/lib/systemd/system/nitro-enclaves-allocator.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2021-04-16 17:26:37 UTC; 2s ago
  Process: 3569 ExecStart=/usr/bin/nitro-enclaves-allocator (code=exited, status=1/FAILURE)
 Main PID: 3569 (code=exited, status=1/FAILURE)

Apr 16 17:26:37 ip-172-16-1-154.ec2.internal systemd[1]: Starting Nitro Enclaves Resource Allocator...
Apr 16 17:26:37 ip-172-16-1-154.ec2.internal nitro-enclaves-allocator[3569]: /usr/bin/nitro-enclaves-allocator: line 130: /sys/module/nitro_enclaves/parameters/ne_cpus: No such file or directory
Apr 16 17:26:37 ip-172-16-1-154.ec2.internal nitro-enclaves-allocator[3569]: cat: .tmp_file: No such file or directory
Apr 16 17:26:37 ip-172-16-1-154.ec2.internal nitro-enclaves-allocator[3569]: rm: cannot remove '.tmp_file': No such file or directory
Apr 16 17:26:37 ip-172-16-1-154.ec2.internal nitro-enclaves-allocator[3569]: Error: The CPU pool file is missing. Please make sure the Nitro Enclaves driver is inserted.
Apr 16 17:26:37 ip-172-16-1-154.ec2.internal systemd[1]: nitro-enclaves-allocator.service: main process exited, code=exited, status=1/FAILURE
Apr 16 17:26:37 ip-172-16-1-154.ec2.internal systemd[1]: Failed to start Nitro Enclaves Resource Allocator.
Apr 16 17:26:37 ip-172-16-1-154.ec2.internal systemd[1]: Unit nitro-enclaves-allocator.service entered failed state.
Apr 16 17:26:37 ip-172-16-1-154.ec2.internal systemd[1]: nitro-enclaves-allocator.service failed.

Running on m5.xlarge Amazon Linux.

[blmalone]

Never mind, I had to click the 'Enable Enclave' option when launching a new EC2 instance. It's not available by default.