At the moment, the AWS-IoT callback type by default uses data.iot.[region].amazonaws.com as the endpoint to POST to. This is a public endpoint not associated with the developer's AWS account and for testing only (cf. https://docs.aws.amazon.com/cli/latest/reference/iot-data/index.html).
Custom AWS-IoT endpoints provisioned for an account look like this: [id].iot.[region].amazonaws.com.
Is there any way to configure/change the endpoint in the Sigfox backend? This would be a prerequisite for any production deployment.
Answer by AWS · Mar 20 at 05:54 AM
AWS and Sigfox are working closely together to enhance the AWS IoT connector provided today so first of all thank you for the feedback.
As mentioned by the link you provided, two different types of public endpoints exist today for AWS IoT, a default one and a custom endpoint.
As of today, AWS recommends strongly (Best Practice) to use the custom endpoint rather than the default one, but it is not mandatory.
AWS and Sigfox share a joint roadmap and this enhancement is already part of it. The customer experience will be the same as what is available today. No extra configuration will be needed from the user as this information can be retrieved automatically by using the AWS IoT API. In order to be able to call the method Describe Endpoint of the AWS IoT API on behalf of the customer, Sigfox plans to make a minor edit to the AWS CloudFormation script available today so it includes this additional permission.
We would be very interested to hear from you if you have any other feedback when using the connector.
We will update this post as soon as this enhancement is released.
The AWS & Sigfox Team
Answer by maku · Mar 20 at 11:09 AM
Setting up a custom callback using the endoint address provided on AWS results in the callback having status: "pending".
Is there a functioning tutorial put there?
Edit: I see I was too slow with the snipping tool and yet another err.600 was thrown.