CloudFormation是否公开Redis ElastiCache复制组的读取器端点？ [英] Does CloudFormation expose the Reader Endpoint of a Redis ElastiCache Replication Group?

问题描述

我需要公开我的Redis ReplicationGroup的Reader端点，以便供依赖的CloudFormation堆栈使用。

I need to expose the Reader Endpoint of my Redis ReplicationGroup so it can be used by dependent CloudFormation stacks.

我以前使用了主要端点，即可以作为CloudFormation返回值使用，但我现在需要使用于2019年6月推出的Reader Endpoint [ https://aws.amazon.com/about-aws/whats-new/2019/06/amazon-elasticache-launches- 。

I've previously used the primary endpoint, which is available as a CloudFormation return value, but I now need to use the Reader Endpoint, introduced in June 2019 [https://aws.amazon.com/about-aws/whats-new/2019/06/amazon-elasticache-launches-reader-endpoint-for-redis/].

但是，Reader端点未出现在CloudFormation文档[ https://docs.aws.amazon.com/AWSCloudFormation/最新/UserGuide/aws-resource-elasticache-replicationgroup.html]

However the Reader Endpoint does not appear in the Return Values in the CloudFormation documentation [https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-elasticache-replicationgroup.html]

我的堆栈输出定义为：

MyReplicationGroup.PrimaryEndPoint.Address
MyReplicationGroup.PrimaryEndPoint.Port

阅读器端点是否可用，但尚未记录？

Is the Reader Endpoint available, but not yet documented? Perhaps the following is all I need?

MyReplicationGroup.ReaderEndPoint.Address
MyReplicationGroup.ReaderEndPoint.Port

我宁愿不使用ReadEndPoint.Addresses和ReadEndPoint.Ports，因为它们是副本列表，因此我需要以编程方式选择要连接的对象-Reader Endpoint将为我完成所有工作（这就是它的全部内容）。

I'd rather not use the ReadEndPoint.Addresses and ReadEndPoint.Ports as these are lists of replicas, and I then need to programmatically choose which to connect to - the Reader Endpoint will do all that for me (that is the whole point of it).

推荐答案

读者端点地址当前未公开。

Reader Endpoint Address is not currently exposed.

但是主要端点和可以使用的阅读器
端点。

假设您有一个主要端点 one.two.three.com 。

然后，读者端点将是 one-ro.two.three.com 。

Suppose you have a primary endpoint one.two.three.com.
Then reader endpoint would be one-ro.two.three.com.

通过这种方式，您可以在相应的主要Endpoi的帮助下为Reader Endpoint生成地址。

In this way, you can generate the address for a Reader Endpoint with the help of a corresponding Primary Endpoint.

注意：我知道这不是永久性的解决方案，但目前作为
解决方法是，我们可以在主要
端点的帮助下推断出读者端点。

Note: I know this is not the permanent solution but for now as a workaround we can deduce the Reader Endpoint with the help of the Primary Endpoint.

这篇关于CloudFormation是否公开Redis ElastiCache复制组的读取器端点？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！