-
Notifications
You must be signed in to change notification settings - Fork 54
docs: update state of clouds #1732
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
Conversation
✅ Deploy Preview for constellation-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
docs/docs/overview/clouds.md
Outdated
|
||
AWS currently doesn't offer CVMs. AWS proprietary Nitro Enclaves offer some related features but [are explicitly not designed to keep AWS itself out](https://aws.amazon.com/blogs/security/confidential-computing-an-aws-perspective/). Besides, they aren't suitable for running entire Kubernetes nodes inside them. Therefore, Constellation uses regular EC2 instances on AWS [Nitro](https://aws.amazon.com/ec2/nitro/) without runtime encryption. Attestation is based on the [NitroTPM](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nitrotpm.html), which is a vTPM managed by the Nitro hypervisor. Hence, the hypervisor is currently part of Constellation's TCB. | ||
## Amazon Web Services (AWS) | ||
Amazon EC2 [supports AMD SEV-SNP](https://aws.amazon.com/de/about-aws/whats-new/2023/04/amazon-ec2-amd-sev-snp/). Regarding (3), AWS provides direct access to remote-attestation statements. However, regarding (4), the CVMs still include closed-source firmware running in VM Privilege Level (VMPL) 0. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
re CVMs still include closed-source firmware
: I did not check yet if we can independently recreate the measurement we get from the sev-guest device. But, AWS says the initial firmware inside the CVM is based on OVMF. So it may not be closed-source. On the other hand, there is no information yet what exactly is put into the CVM.
Co-authored-by: Thomas Tendyck <51411342+thomasten@users.noreply.github.com>
Proposed change(s)
Checklist