Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add configurable debug-mode option into AWS EC2 enclave operator startup #1151

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sunnywu
Copy link
Contributor

@sunnywu sunnywu commented Nov 12, 2024

  1. Added a debug_mode config in secrets manager for aws ec2 start.sh to decide if we need to add --debug-mode param for nitro-cli command

  2. When running --debug-mode param, also add --attach-console param Tested enabling it and on Core Service dashboard can see the attestation request with "AAAAAAAA...." enclave id to confirm it is running in enclave mode

…h to decide if we need to add --debug-mode param for nitro-cli command

2. When running --debug-mode param, also add --attach-console param
Tested enabling it and on Core Service dashboard can see the attestation request with "AAAAAAAA...." enclave id to confirm it is running in enclave mode
echo "starting enclave..."
nitro-cli run-enclave --eif-path $EIF_PATH --memory $MEMORY_MB --cpu-count $CPU_COUNT --enclave-cid $CID --enclave-name uid2operator
if [ "$DEBUG_MODE" == "true" ]; then
echo "starting enclave... --eif-path $EIF_PATH --memory $MEMORY_MB --cpu-count $CPU_COUNT --enclave-cid $CID --enclave-name uid2operator --debug-mode --attach-console"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: starting enclave in debug mode ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants