CloudFormation是否暴露Redis ElastiCache复制组的Reader Endpoint？

Absolutely! Even though the CloudFormation documentation hasn’t been updated to explicitly list the ReaderEndPoint return values, you can use MyReplicationGroup.ReaderEndPoint.Address and MyReplicationGroup.ReaderEndPoint.Port just like you do with the Primary Endpoint.

Here’s how to implement it in your stack outputs: #

Outputs:
  RedisReaderEndpointAddress:
    Description: Address of the Redis Replication Group Reader Endpoint
    Value: !GetAtt MyReplicationGroup.ReaderEndPoint.Address
    Export:
      Name: RedisReaderEndpointAddress
  RedisReaderEndpointPort:
    Description: Port of the Redis Replication Group Reader Endpoint
    Value: !GetAtt MyReplicationGroup.ReaderEndPoint.Port
    Export:
      Name: RedisReaderEndpointPort

Key Details to Keep in Mind: #

• The Reader Endpoint launched in June 2019, and CloudFormation has supported referencing it via these attributes since then—documentation simply lagged behind the feature rollout.
• This aligns perfectly with the Reader Endpoint’s core purpose: it automatically distributes read traffic across your replica nodes, so you avoid the overhead of programmatically managing the list of individual replica endpoints (ReadEndPoint.Addresses/ReadEndPoint.Ports).
• Ensure your replication group has at least one replica node deployed— the Reader Endpoint won’t exist if you only have a primary instance.
• You can confirm the endpoint exists by checking your replication group in the ElastiCache console, or running the aws elasticache describe-replication-groups --replication-group-id <your-group-id> CLI command (look for the ReaderEndpoint field in the response).

If you hit any snags, double-check that your Redis version supports the Reader Endpoint feature, and that your replication group is configured with read replicas. In most cases, though, the attribute references will work seamlessly.

内容的提问来源于stack exchange，提问作者JimSpriggs