- Más nuevo
- Más votos
- Más comentarios
TL;DR: Contact your local AWS Solutions Architect for an in-depth discussion of alternative solutions.
Tricky question because there's no easy way to solve this.
In an ideal world you'd just put a NLB in front of the ElastiCache cluster; point PrivateLink at it and away you go. But it isn't that easy.
One way to solve this would be to deploy Lambda functions to each account; and have them independently call the clusters. Probably raises more problems than it solves: Lambda deployment; cross-account access; sync/async calls; all sorts of things.
In the end, you may find the solution that you've linked to is the way to go; but it also (as you know) has drawbacks.
Definitely an opportunity to chat to your local AWS team and find a "good" way of doing this.
Contenido relevante
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 5 meses