Provide better UX when user specifies incorrect AWS KMS endpoint

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, when a user specifies an invalid AWS KMS endpoint (for example, with the https:// scheme in front), they currently get the vague error "SocketError: nodename nor servname provided, or not known." It would be a better experience if the user received a message specifying that there is probably an issue with the KMS endpoint.

            Assignee:
            Oleg Pudeyev (Inactive)
            Reporter:
            Emily Giurleo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: