I'm not sure how much control this project has over this, but it seems like the architecture you're choosing does result in a large number of public IPs being created.
I think every availability zone gets its own public IP, so that's multiple EIPs per Redis cache? we definitely filled up our expanded quota of 10 really quickly. with multiple services having their own Redis cache each, and all of them being duplicated as prod and staging, there's just a lot of networking.
Would you recommend a different setup? Just having one elastic cache per AWS account and working with different Redis databases? Or is there maybe a way to reduce the amount of public IPs used? Any feedback appreciated. thanks for the great work you've put into this project, we make good use of it in our small team.
I'm not sure how much control this project has over this, but it seems like the architecture you're choosing does result in a large number of public IPs being created.
I think every availability zone gets its own public IP, so that's multiple EIPs per Redis cache? we definitely filled up our expanded quota of 10 really quickly. with multiple services having their own Redis cache each, and all of them being duplicated as prod and staging, there's just a lot of networking.
Would you recommend a different setup? Just having one elastic cache per AWS account and working with different Redis databases? Or is there maybe a way to reduce the amount of public IPs used? Any feedback appreciated. thanks for the great work you've put into this project, we make good use of it in our small team.