openresty / openresty/lua-resty-redis
Unable to connect to redis instance AWS elastic cache - In-Transit Encryption (TLS) enabled
Open
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 2k
- Forks
- 447
- Avg merge
- 2h 24m
- Merged PRs (30d)
- 3
Description
function M.connect_to_redis ()
local redis = require "resty.redis"
local red = redis:new()
red:set_timeout(10000)
local vcap_services = cjson.decode(os.getenv("ENV"))
local redis_service_name = os.getenv("REDIS")
local redis_credentials = vcap_services[redis_service_name][1].credentials;
local redis_host = redis_credentials.host
local redis_port = redis_credentials.port
local redis_password = redis_credentials.password
local ok, err = red:connect(redis_host, redis_port)
local res, err = red:auth(redis_password)
return red
end
I tried enable ssl=true by passing it as params
local options = {
ssl = true
}
local ok, err = red:connect(redis_host, redis_port, options)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at M.connect_to_redis and the red:connect(redis_host, redis_port, options) call, then reproduce the failure against an AWS ElastiCache Redis instance with in-transit encryption enabled. Verify the supported TLS connection options and authentication flow; done means the client establishes a secure connection and authenticates successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, lua, redis
- Domain
- databases, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100