[docs] Transferring Nautilus docs from github repo to Sui docs #22180
Conversation
…ion to relevant data access content
Co-authored-by: ronny-mysten <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
github-actions
bot
added
the
Type: Documentation
abhinavg6
temporarily deployed
to
sui-typescript-aws-kms-test-env
GitHub Actions
Inactive
ronny-mysten
temporarily deployed
to
sui-typescript-aws-kms-test-env
GitHub Actions
Inactive
ronny-mysten
temporarily deployed
to
sui-typescript-aws-kms-test-env
GitHub Actions
Inactive
ronny-mysten
temporarily deployed
to
sui-typescript-aws-kms-test-env
GitHub Actions
Inactive
| }, | ||
| items: [ | ||
| 'concepts/cryptography/nautilus/nautilus-design', | ||
| 'concepts/cryptography/nautilus/using-nautilus', |
There was a problem hiding this comment.
Are we married to this setup? I think the nautilus design and overview page should be combined and the using nautilus page should go in the Guides section. There should then be a Related links level 2 heading at the end of each topic that points to each other...and other links that might be valuable.
I can do this to see if you like or no. Let me know.
There was a problem hiding this comment.
Hmm.. I get you, but would be great if we could leave it as is for now, to allow the builders who've seen the Github docs find the same format (that's how we structured it there).. Basically we're just looking to migrate for mainnet launch right now.. We could then do your suggested optimization a couple of months later as an improvement once we've a few more things to add (like TEE network partners that we would've by then)..
|
|
||
| ## FAQs | ||
|
|
||
| 1. There are many TEE providers available. Why did Sui choose AWS Nitro Enclaves initially? |
There was a problem hiding this comment.
This was answered on another page. Would be better to create a snippet that can be used in both places using {@include}. Would also suggest not using FAQ and just making these their own section.
There was a problem hiding this comment.
This is also something i can update.
There was a problem hiding this comment.
Yeah makes sense to me. Thanks for offering to update - would appreciate it :)
There was a problem hiding this comment.
Wasn't as clean as I assumed. Kept relatively as is but now have the questions appear on right nav for better discoverability.
| - Configures required HTTP domains so the enclave can access external APIs via the parent EC2 instance (as the enclave itself has no internet access). | ||
| - Exposes three endpoints to allow client-side communication with the enclave. | ||
|
|
||
| When the enclave starts, it generates a fresh enclave key pair and exposes the following three endpoints: |
There was a problem hiding this comment.
I changed this to read three instead of two. Correct?
There was a problem hiding this comment.
oh right, sorry and thanks.. these were originally two, but then we added the third later, but didn't update that number :)
ronny-mysten
temporarily deployed
to
sui-typescript-aws-kms-test-env
GitHub Actions
Inactive
| $ ENCLAVE_OBJECT_ID=0xe0e70df5347560a1b43e5954267cadd1386a562095cb4285f2581bf2974c838d | ||
| ``` | ||
|
|
||
| You can view an example of an enclave config object containing PCRs [on SuiScan](https://testnet.suivision.xyz/object/0x58a6a284aaea8c8e71151e4ae0de2350ae877f0bd94adc2b2d0266cf23b6b41d). You can also view an [example of an enclave object](https://testnet.suivision.xyz/object/0xe0e70df5347560a1b43e5954267cadd1386a562095cb4285f2581bf2974c838d) containing the enclave public key. |
There was a problem hiding this comment.
I forgot to point out that we don't want to provide links to testnet data as there's no guarantee this info won't get wiped. We can address later but something to keep in mind on future writings.
There was a problem hiding this comment.
That's a good point, especially with the discussions on a potential testnet wipe. cc @joyqvq
|
Thanks for the changes, @ronny-mysten. We'll merge this next week once the changes go to mainnet. |
Description
Moving the Nautilus docs from github repo to the main Sui docs for mainnet release.
Test plan
NA
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.