Skip to content

Unable to Create IoT Rule with HTTPS Endpoint Containing _ or -

0

We're encountering an issue when attempting to create an AWS IoT Rule with an HTTPS action endpoint. If the URL contains an underscore (_) or a hyphen (-), the validation fails with the error:

The HTTPS endpoint must be a valid URL.

Endpoint Used: https://mangoe.duckdns.org/api/device_mgmt_service/devices/centralizeErrorLogs

Error Message: The HTTPS endpoint must be a valid URL.

Expected Behavior: URLs with underscores or hyphens (like /device_mgmt_service/) were previously accepted and used successfully.

Current Behavior: Creation fails with validation error, even though the URL is valid and accessible.

asked a year ago146 views

1 Answer
0
Accepted Answer

We're encountering an issue when attempting to create an AWS IoT Rule with an HTTPS action endpoint. If the URL contains an underscore (_) or a hyphen (-), the validation fails with the error: The HTTPS endpoint must be a valid URL. Expected Behavior: URLs with underscores or hyphens (like /device_mgmt_service/) were previously accepted and used successfully. Current Behavior: Creation fails with validation error, even though the URL is valid and accessible.

Replicated the issue and were able to create AWS IoT Rule with an HTTPS action endpoint via below CLI as well as on Console.

aws iot create-topic-rule-destination --destination-configuration httpUrlConfiguration={confirmationUrl=https://mangoe.duckdns.org/api/device_mgmt_service/devices/centralizeErrorLogs}

  1. [https://docs.aws.amazon.com/cli/latest/reference/iot/create-topic-rule-destination.html]
  2. [https://docs.aws.amazon.com/cli/latest/reference/iot/create-topic-rule.html]
  3. [https://docs.aws.amazon.com/iot/latest/developerguide/rule-destination-http-managing.html]

Also, the investigation was carried out in cooperation with the department in charge of the service, the cause of this incident was identified, and corrections were made to the UI and the bug has been fixed. So, I kindly request you to try on your end and if you still face the issue, please raise the Support case with AWS.

AWS

answered a year ago

EXPERT

reviewed 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.