Skip to content

Commit 2c7400c

Browse files
authored
[DOCS] Minor grammatical fixes (#13271)
EAR doc fixes.
1 parent d193c30 commit 2c7400c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

architecture/design/docdb-encryption-at-rest.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -117,16 +117,16 @@ While we will eventually support option 1, we currently don't have a mechanism t
117117
# Key Management Service (KMS) Integration
118118

119119
KMS integration would initially be facilitated via the Enterprise Platform solution, where the user would maintain the credentials to their KMS system of choice, and at the universe creation time
120-
we would make appropriate API calls to create a new Universe Key and use that key to provision a new universe with At Rest Encryption enabled. In this section we details the approach we plan on
120+
we would make appropriate API calls to create a new Universe Key and use that key to provision a new universe with At Rest Encryption enabled. In this section, we detail the approach we plan on
121121
taking with some of the KMS system that we would support via Platform.
122122

123123
## Equinix [SmartKey](https://www.equinix.com/services/edge-services/smartkey/). Integration
124-
SmartKey is KMS a offering from Equinix, they provide SDK and API to manage the keys in their platform, Yugabyte platform would integrate with SmartKey via the REST API route and authenticate
124+
SmartKey is a KMS offering from Equinix, they provide SDK and API to manage the keys in their platform, Yugabyte platform would integrate with SmartKey via the REST API route and authenticate
125125
using their API key in order to manage the Keys. We would use the name attribute on the Key to link the universe that the key is generated for. Once the key is generated we would make appropriate RPC
126126
calls to YugabyteDB to enable encryption. We would call their rekey api when the user wants to rekey the universe and update the YugabyteDB nodes in a rolling fashion.
127127

128128
## AWS [Key Management Service](https://docs.aws.amazon.com/kms/latest/developerguide/overview.html)
129-
Amazon offers their KMS solution, we will your their KMS api to manage the keys, And they have the concept of aliases which we would use that to build a relationship between the key and universe.
129+
Amazon offers their KMS solution, we will use their KMS API to manage the keys. And they have the concept of aliases which we would use to build a relationship between the key and universe.
130130
When the key needs to be rotated we would create a new key and update the alias accordingly. And do the update on YugabyteDB nodes in a rolling fashion.
131131

132132
# Implementation Internals

0 commit comments

Comments
 (0)