Requested attribute Address does not exist in schema for AWS::MemoryDB::Cluster

0

I created a MemoryDB for Redis with cloudformation and I wanted to output the cluster endpoint, this is the code:

memoryDBCluster:
    Type: AWS::MemoryDB::Cluster
    DependsOn:
      - Lambda1
      - Lambda2
    Properties:
      ClusterName: !Sub 'cluster-${Environment}'
      Description: Redis cluster
      EngineVersion: "7.0"
      ACLName: open-access
      NodeType: !Ref NodeType
      NumReplicasPerShard: 1
      NumShards: 1
      SecurityGroupIds:
        - !Ref memoryDBClusterSG
      SubnetGroupName: !Ref memoryDBClusterSubnetGroup
      TLSEnabled: true

I tried to output the endpoint in two ways:

first with

Outputs:
  ClusterAddress:
    Description: "The cluster Address"
    Value: !GetAtt memoryDBCluster.Address

With this I got "Requested attribute Address does not exist in schema for AWS::MemoryDB::Cluster"

and:

Outputs:
  ClusterAddress:
    Description: "The cluster Address"
    Value: !GetAtt memoryDBCluster.Endpoint.Address

in this case the error was "Requested attribute Endpoint.Address does not exist in schema for AWS::MemoryDB::Cluster"

is this a bug? where can I report it?

1 Answer
0

Hello,

From your query, I understand that you are trying to create a MemoryDB cluster for Redis with CloudFormation and want to output the cluster endpoint but you are facing error’s.

In order to fix the issue, please try to use : "!GetAtt memoryDBClusterRedis.ClusterEndpoint.Address" in the Outputs value.

See the below snippet:

Outputs:
  ClusterAddress:
    Description: "The cluster Address"
    Value: !GetAtt memoryDBClusterRedis.ClusterEndpoint.Address

The above approach should be fixing the error and you should be able to create the Cluster and output cluster’s address.

Thank you for bringing this issue to our attention. We're always looking forward to make our services easier to use for our customers, therefore I’ll be submitting the feedback internally to modify the AWS Documentation accordingly.

If you face any further errors or issues, then I would suggest you to open a support case with AWS for further troubleshooting. You can use the following link for the same: https://support.console.aws.amazon.com/support/home#/case/create

AWS
SUPPORT ENGINEER
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions