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 enclave support for peer pods to aws provider #2182

Open
gaussye opened this issue Dec 4, 2024 · 3 comments
Open

Add enclave support for peer pods to aws provider #2182

gaussye opened this issue Dec 4, 2024 · 3 comments
Labels
provider/aws Issues related to AWS CAA provider

Comments

@gaussye
Copy link

gaussye commented Dec 4, 2024

Can we include enclave option for aws provider when create ec2 instances for peed pod? The option can only be configured when launch a new instance.

aws cli:
aws ec2 run-instances --image-id ami- --count 1 --instance-type c5.2xlarge --key-name dev_nitro.pem --region us-east-1 --enclave-options 'Enabled=true' --subnet-id

@bpradipt
Copy link
Member

bpradipt commented Dec 6, 2024

Can we include enclave option for aws provider when create ec2 instances for peed pod? The option can only be configured when launch a new instance.

aws cli: aws ec2 run-instances --image-id ami- --count 1 --instance-type c5.2xlarge --key-name dev_nitro.pem --region us-east-1 --enclave-options 'Enabled=true' --subnet-id

@gaussye how do you plan to use nitro enclave with peer-pods ?

@gaussye
Copy link
Author

gaussye commented Dec 12, 2024

@bpradipt We are still in the POC phase. If everything goes well, we may start the testing on enclave instance in Jan 2025.

@mkulke mkulke added the provider/aws Issues related to AWS CAA provider label Dec 16, 2024
@bpradipt
Copy link
Member

@gaussye once you have something ready, may be we can discuss in our community call on the best way to integrate it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
provider/aws Issues related to AWS CAA provider
Projects
None yet
Development

No branches or pull requests

3 participants