I see this forum post on the things network. The answer there notes:
I solved this issue. The documentation for the nam1 cluster is outdated. There is no tenant ID and it is not “.industries” it is “nam1.cloud.thethings.network” for your cluster addres[s]
I am not an expert in the service but that above forum post may be related to your issue. I recommend reaching out to The Things Stack for their deployment issues. However, in general, when using a CloudFormation's custom resource, the resource provider should be sending back a PhysicalResourceId.
This value should be an identifier unique to the custom resource vendor, and can be up to 1 KB in size. The value must be a non-empty string and must be identical for all responses for the same resource.
Hi. Since you mentioned eu1, I take it you're using Things Stack Community Edition? (https://eu1.cloud.thethings.network is the EU cluster of the Community Edition.) If so, please ensure that you have selected Community when deploying the template. I think the user in the forum post that Taka_M has linked, probably picked Cloud when it should have been Community. Regardless, you need to pick the right deployment type to match your Things Stack account/deployment.
Relevant questions
Cloudformation doesn't properly return non-ascii characters
asked 8 months agoCan I SSH into my container running on AppRunner?
asked 4 months agoHow to integrate Amazon S3 into Microsoft Access
asked 5 months agoRunning aws cli command in Cloudformation fails
Accepted Answerasked 17 days agoCloudFormation Invalid PhysicalResourceID - how to fix?
asked 20 days agoHow to troubleshoot Cloudformation "Invalid request provided: AWS::ElasticLoadBalancingV2::ListenerRule Validation exception"?
asked 5 months agoHow to deploy an operator on exiting EKS using CloudFormation?
asked 17 days agoCloudFormation stack stuck in UPDATE_COMPLETE_CLEANUP_IN_PROGRESS
Accepted Answerasked 8 months agoThe Things Network republish into another topic
asked 4 months agoHave a service running in an ECS cluster dynamically create a new service in the same cluster
asked 2 months ago