Skip to main content

Security and access in Aiven for Valkey™

Control access and secure connections to your Aiven for Valkey™ service.

Two independent layers of control​

Securing an Aiven for Valkey™ service involves two layers that don't affect each other. Transport security, SSL, encrypts the connection between a client and the service. Authorization, through access control lists (ACLs), determines what an already-connected user can do, down to individual commands, key patterns, and pub/sub channels. Turning SSL off doesn't loosen a user's ACLs, and tightening ACLs doesn't encrypt an otherwise plain-text connection.

Things to know​

  • Every service starts with a default administrative user that has full access. Create separate service users with restricted ACLs for applications and integrations instead of sharing that user's credentials.
  • Direct ACL and CONFIG commands are restricted on the server. Configure ACLs and SSL settings through the Aiven Console, Aiven CLI, Aiven API, or Terraform instead.
  • When you set ACL categories, commands, or keys for a user through the CLI, API, or Terraform, specify all three together. Pub/sub channel rules can be set on their own.

Related pages