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.

Sign up for GitHub

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

vsock_proxy: set log level to warn #592

Merged
merged 2 commits into from
Mar 20, 2024
Merged

vsock_proxy: set log level to warn #592

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f63710c
vsock_proxy: set log level to warn
meerd Mar 12, 2024
9590845
Merge branch 'main' into vsp_enable_logging
meerd Mar 20, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions vsock_proxy/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,3 +100,10 @@ systemctl enable nitro-enclaves-vsock-proxy.service
The service files can be found in `service` directory. The proxy is ran using the default configuration
from `/etc/nitro_enclaves/vsock-proxy.yaml`, on local port 8000 and the AWS KMS endpoint corresponding to
the region of the instance.

You can use the following command to check the vsock proxy logs to diagnose connectivity issues.
```
journalctl -eu nitro-enclaves-vsock-proxy.service
```
To enable more detailed logging output, set the `RUST_LOG` environment variable to the `trace` log level in
the service file (e.g.`/usr/lib/systemd/system/nitro-enclaves-vsock-proxy.service`).
4 changes: 2 additions & 2 deletions vsock_proxy/service/nitro-enclaves-vsock-proxy.service
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,11 +8,11 @@ Type=simple
StandardOutput=journal
StandardError=journal
SyslogIdentifier=vsock-proxy
# Use RUST_LOG=trace for more verbose logging
ExecStart=/bin/bash -ce "TOKEN=$(curl --silent -X PUT \"http://169.254.169.254/latest/api/token\" -H \"X-aws-ec2-metadata-token-ttl-seconds: 21600\") ; \
REGION=$(curl --silent -H \"X-aws-ec2-metadata-token: $TOKEN\" http://169.254.169.254/latest/dynamic/instance-identity/document | jq -r .region) ; \
[ -z \"$REGION\" ] && REGION=$(curl --silent http://169.254.169.254/latest/dynamic/instance-identity/document | jq -r .region) ; \
exec /usr/bin/vsock-proxy 8000 kms.$${REGION}.amazonaws.com 443 \
--config /etc/nitro_enclaves/vsock-proxy.yaml"
RUST_LOG=warn exec /usr/bin/vsock-proxy 8000 kms.$${REGION}.amazonaws.com 443 --config /etc/nitro_enclaves/vsock-proxy.yaml"
Restart=always
TimeoutSec=0

Expand Down