我们想使用 NAT 在本地连接到 ElasticCache 配置端点(如:http://docs.aws.amazon.com/AmazonElastiCache/latest/UserGuide/Access.Outside.html 中所述)。但是找不到IP地址，NAT不能使用DNS。
我们确实设法使用 NAT 映射每个节点的 IP 地址，但我们想立即连接到整个集群。
我在 Ask Ubuntu 中发现了另一个相关问题，但也没有 awserws: https://askubuntu.com/questions/779961/use-endpoint-instead-of-ip-in-iptables
最佳答案
我建议为开发或单元测试设置一个本地 Redis 服务器。
为测试、暂存和生产环境创建单独的 elasticache 集群。
原因是，要让它从本地机器连接起来工作量太大，其次，根据AWS documents，在任何情况下都不建议将所有这些工作用于生产环境。本身:
Limitations
This approach should be used for testing and development purposes only. It is not recommended for production use due to the following limitations:
The NAT instance is acting as a proxy between clients and multiple clusters. The addition of a proxy impacts the performance of the cache cluster. The impact increases with number of cache clusters you are accessing through the NAT instance. The traffic from clients to the NAT instance is unencrypted. Therefore, you should avoid sending sensitive data via the NAT instance. The NAT instance adds the overhead of maintaining another instance. The NAT instance serves as a single point of failure. For information about how to set up high availability NAT on VPC, see High Availability for Amazon VPC NAT Instances: An Example.
关于amazon-web-services - 找不到 AWS ElasticCache 配置端点 IP 地址，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/44007257/