aws / aws-nitro-enclaves-cli

Tooling for Nitro Enclave Management

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Unable to open /dev/nitro_enclaves on latest amazon emi enclave

last61474 opened this issue · comments

Hi, I spawned a new ec2 instance and the nitro-cli enclave run is unable to start the enclave. Same eif and dockerfile works on an older enclave.

Can I check if you have any idea on what can be the possible issue:

  Action: Run Enclave
  Subactions:
    Failed to execute command `Run`
    Failed to trigger enclave run
    Failed to construct EnclaveManager with given arguments
    Failed to create enclave handle
    Failed to open device file: Os { code: 2, kind: NotFound, message: "No such file or directory" }
  Root error file: src/enclave_proc/resource_manager.rs
  Root error line: 521
  Version: 1.2.2
  Action: Run Enclave
  Subactions:
    Failed to handle all enclave process replies
    Failed to connect to 1 enclave processes
  Root error file: src/enclave_proc_comm.rs
  Root error line: 358
  Version: 1.2.2
[ E19 ] File operation failure. Such error appears when the system fails to perform the requested file operations, such as opening the EIF file when launching an enclave, or seeking to a specific offset in the EIF file, or writing to the log file.
File: '/dev/nitro_enclaves', failing operation: 'Open'.

For more details, please visit https://docs.aws.amazon.com/enclaves/latest/user/cli-errors.html#E19

If you open a support ticket, please provide the error log found at "/var/log/nitro_enclaves/err2023-07-27T23:54:30.234475648+00:00.log"
Failed connections: 1
[ E39 ] Enclave process connection failure. Such error appears when the enclave manager fails to connect to at least one enclave process for retrieving the description information.

For more details, please visit https://docs.aws.amazon.com/enclaves/latest/user/cli-errors.html#E39

If you open a support ticket, please provide the error log found at "/var/log/nitro_enclaves/err2023-07-27T23:54:30.234651195+00:00.log"

Check if the enclaves option was enabled to true on the ec2 at launch.