# AWS MemoryDB temporary access

[Temporary access overview](/docs/concepts/temporary-access) covers target setup, connection methods, and credential handling.

MemoryDB targets create password-authenticated users and add them to an existing
ACL. Configure an ACL already associated with the intended cluster:

```json
{
  "provider": "memorydb", "executor": "in_do", "region": "us-east-1",
  "aclName": "app-readers", "accessString": "on ~app:* -@all +get +mget",
  "maxTtlSeconds": 3600
}
```

Encrypt the AWS management credential JSON (`accessKeyId`, `secretAccessKey`,
optional `sessionToken`) when adding the target. The IAM principal needs
`memorydb:CreateUser`, `memorydb:DescribeUsers`, `memorydb:UpdateACL`, and
`memorydb:DeleteUser`. Management session credentials must remain valid for
cleanup. Passwords and passwordless ACL directives cannot be supplied in the
access string; Seekrit generates a fresh password for each lease.

The returned username and password connect to your cluster's existing TLS
endpoint. ACL propagation can delay usability. Users have no native TTL:
Seekrit deletes the user at expiry, and AWS removes it from every ACL. Cleanup
retries until AWS confirms absence, including after a manual revoke reports
pending deletion. Propagation and existing connections can outlast the lease.

See the [MemoryDB CreateUser](https://docs.aws.amazon.com/memorydb/latest/APIReference/API_CreateUser.html)
and [DeleteUser](https://docs.aws.amazon.com/memorydb/latest/APIReference/API_DeleteUser.html) references.

See the [CLI reference](/docs/reference/cli) and [API reference](/docs/reference/api) for commands and endpoints.
