Data protection in Amazon OpenSearch Memory
The AWS shared
responsibility model
For data protection purposes, we recommend that you protect AWS account credentials and set up individual users with AWS IAM Identity Center or AWS Identity and Access Management (IAM). That way, each user is given only the permissions necessary to fulfill their job duties. We also recommend that you secure your data in the following ways:
-
Use multi-factor authentication (MFA) with each account.
-
Use SSL/TLS to communicate with AWS resources. We require TLS 1.2 and recommend TLS 1.3.
-
Set up API and user activity logging with AWS CloudTrail. For more information, see Logging Amazon OpenSearch Memory API calls with AWS CloudTrail.
-
Use AWS encryption solutions, along with all default security controls within AWS services.
-
Use advanced managed security services such as Amazon Macie, which assists in discovering and securing sensitive data that is stored in Amazon S3.
We strongly recommend that you never put confidential or sensitive information, such as your customers' email addresses, into tags or free-form text fields such as a Name field. This includes when you work with OpenSearch Memory or other AWS services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into tags or free-form text fields used for names may be used for billing or diagnostic logs. For OpenSearch Memory, this applies to space names, strategy names and descriptions, actor and session IDs, and metadata keys and values. The content of events and memories is customer data and is protected as described in this topic.
Encryption at rest
OpenSearch Memory encrypts the events and memories in every space at rest. By default, it uses an AWS owned key. AWS owned keys are not stored in your account. You can't view, manage, or audit their use, and there is no charge for them.
If you want to control the key, choose a customer managed key in AWS Key Management Service (AWS KMS) when you create the space. You own the key, set its policy, can audit its use in CloudTrail, and can revoke OpenSearch Memory's access to it. You pay AWS KMS charges for a customer managed key.
Key management
To use a customer managed key, specify its ARN in
encryptionConfiguration.kmsKeyArn when you create the space. The key
must be a symmetric encryption key that is enabled and in the same AWS Region as the
space. You can't change a space's key after you create it.
Topics
Permissions required for a customer managed key
OpenSearch Memory uses your key with the permissions of the principal that makes the request. A principal that calls an OpenSearch Memory operation on a space with a customer managed key therefore needs permission to use the key, in addition to permission for the OpenSearch Memory action. The following table lists the AWS KMS actions that each operation requires.
| Operation | AWS KMS actions |
|---|---|
| CreateSpace | kms:CreateGrant |
| CreateEvent, CreateMemory | kms:Decrypt, kms:GenerateDataKey,
kms:GenerateDataKeyWithoutPlaintext,
kms:ReEncryptFrom,
kms:ReEncryptTo |
| UpdateMemory | kms:Decrypt, kms:GenerateDataKey |
| GetEvent, BatchGetEvent, ListEvents, SearchEvents, DeleteEvent, GetMemory, ListMemories, SearchMemories, DeleteMemory | kms:Decrypt |
You can grant these permissions in the key policy, in an IAM policy, or both. The following example key policy statement lets one role use the key for all OpenSearch Memory operations, and only through OpenSearch Memory.
{ "Sid": "Allow use of the key through OpenSearch Memory", "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::111122223333:role/my-memory-app-role" }, "Action": [ "kms:CreateGrant", "kms:Decrypt", "kms:GenerateDataKey", "kms:GenerateDataKeyWithoutPlaintext", "kms:ReEncryptFrom", "kms:ReEncryptTo" ], "Resource": "*", "Condition": { "StringEquals": { "kms:ViaService": "osm.us-east-1.amazonaws.com" } } }
Replace 111122223333 with your account ID,
my-memory-app-role with the role that calls OpenSearch Memory, and
us-east-1 with the Region of the space. The
kms:ViaService condition means the role can use the key only from
OpenSearch Memory, not directly.
If a principal can access a space but can't use its key, the principal's requests
fail with AccessDeniedException.
How OpenSearch Memory uses grants
Extraction, consolidation, and retention run after your request returns, so OpenSearch Memory needs to use your key when no request from you is in progress. When you create a space with a customer managed key, OpenSearch Memory creates grants on the key with your permissions. The grants allow OpenSearch Memory to encrypt and decrypt the space's data for this background work. You can see the grants with the AWS KMS ListGrants operation. OpenSearch Memory retires them when you delete the space.
You can limit the grants that OpenSearch Memory can create with the
kms:GrantIsForAWSResource and kms:GrantOperations
condition keys on the kms:CreateGrant permission.
If the key becomes unavailable
If you disable the key, schedule it for deletion, revoke the grants, or remove a principal's access to it, OpenSearch Memory can no longer read or write the space's data:
-
Requests from a principal that can't use the key fail with
AccessDeniedException. -
Requests on a space whose key is disabled, pending deletion, or deleted fail with
ValidationException. -
Extraction and consolidation for the space stop until the key is available again.
Re-enable the key or cancel its deletion to restore access. If AWS KMS throttles
OpenSearch Memory's use of the key, requests fail with
ThrottlingException; retry with backoff or request a higher AWS KMS
quota.
Encryption in transit
All requests to OpenSearch Memory use Transport Layer Security (TLS). OpenSearch Memory requires TLS 1.2 and supports TLS 1.3.
Data location
Your spaces, and the events and memories stored in them, stay in the AWS Region where you created the space.
To extract memories, OpenSearch Memory calls a foundation model. Model calls may be processed in another AWS Region within the same geography as your space, for example within the United States for a space in US East (N. Virginia). The data sent to the model is used only to produce the memories and is not stored outside the space's Region. For the Regions in each geography, see Geographic cross-Region inference in the Amazon Bedrock User Guide.
Deleting data
The following operations delete data from a space:
-
DeleteEvent – Deletes the event. It doesn't delete memories already extracted from the event. To delete those, use
DeleteMemory. -
DeleteMemory – Permanently deletes the memory. You can't restore a deleted memory.
-
DeleteSpace – Deletes the space and all of its memories. The space's events are removed when they reach the end of their retention period.
Expired events and memories are removed automatically according to the space's retention settings. For more information, see Configuring retention.
A deleted event or memory can appear in search results for a short time after the delete call returns.