Security

Arctickey is built with security-first design. Your data is protected in transit and at rest.

TLS Encryption#

All connections use TLS 1.3 encryption. Unencrypted connections are not supported.

Connection String#

Always use rediss:// (with double 's') for TLS:

TEXT

rediss://:YOUR_PASSWORD@YOUR_INSTANCE.eu.arctickey.com:6379

Certificate Verification#

We use valid certificates from Let's Encrypt. Most clients verify automatically:

TypeScript

// ioredis - works out of the box
const redis = new Redis('rediss://:PASSWORD@YOUR_INSTANCE.eu.arctickey.com:6379');

// If you need to customize TLS options
const redis = new Redis({
  host: 'YOUR_INSTANCE.eu.arctickey.com',
  port: 6379,
  password: 'YOUR_PASSWORD',
  tls: {
    // Standard verification (recommended)
    rejectUnauthorized: true,
  },
});

Password Authentication#

Every instance has a unique, randomly-generated password:

32+ characters
Alphanumeric with special characters
Automatically generated on creation

Password Location#

Find your password in the dashboard:

Click on your instance
Click Connect
Copy the password

Best Practices#

Never commit passwords to git
Use environment variables
Rotate passwords periodically

Terminal

# .env (never commit this file)
REDIS_URL=rediss://:YOUR_PASSWORD@YOUR_INSTANCE.eu.arctickey.com:6379

IP Whitelisting#

Restrict access to specific IP addresses for additional security.

Setting Up IP Whitelist#

Go to your instance dashboard
Click Security tab
Add IP addresses or CIDR ranges

Whitelist Formats#

TEXT

# Single IP
192.168.1.100

# CIDR range
10.0.0.0/8

# IPv6
2001:db8::1

Common Scenarios#

Office Network:

TEXT

203.0.113.50  # Office public IP

Cloud Providers:

TEXT

# Vercel (check their docs for current IPs)
# Heroku (use their outbound IPs)
# AWS (your NAT gateway or Elastic IP)

Testing Access#

Terminal

# From allowed IP
redis-cli --tls -h YOUR_INSTANCE.eu.arctickey.com -p 6379 -a YOUR_PASSWORD PING
# PONG

# From blocked IP
# Connection refused or timeout