Lorawan-stack: Cloud Formation stack lambda function errors

Hi,

I think this is a bug, but please correct me if I'm wrong!

Summary

After installing and configuring the AWS IoT integration for The Things Stack in our AWS account with the cluster address au1.cloud.thethings.network, I created a thing in AWS IoT Core. The CreateThingFunction returned an error: Failed to dial Identity Server at "ttn-v3-is:///ttn.au1.cloud.thethings.network": connection error: desc = "transport: error while dialing: dial tcp: lookup ttn.au1.cloud.thethings.network on 169.254.78.1:53: no such host" The documentation says that while the cluster address can be in au1, Identity Server API requests to any cluster other than eu1 will fail.

I changed the stack so that the cluster address was eu1.cloud.thethings.industries and it seemed to work in that things were created on ttn console au1.cloud.thethings.network, but the lambda function is still reporting failure. The logs show

2021/02/23 02:13:20 Created on Identity Server
2021/02/23 02:13:21 Failed to dial Join Server at "ttn-v3-js:///eu1.cloud.thethings.network": context deadline exceeded
2021/02/23 02:13:21 Rollback create on Identity Server failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded

Steps to Reproduce

1. create an organisation and application on au1.cloud.thethings.network using the au1 community network
2. install the AWS IoT Integration 1.0.4 for The Things Stack, using an au1 cluster address (no tenant ID)
3. create a thing in AWS

What do you see now?

The cluster address given in the documentation doesn't seem to work, or isn't applicable for community network. It appears eu1 has to be used instead. The lambda function reports an error result in cloudwatch, but creates things in the TTN console.

What do you want to see instead?

The lambda function shouldn't report an error. The documentation here should have a sample cluster address for the community network.

Environment

I don't think the hardware or gateways are relevant here.

How do you propose to implement this?

Documentation updates and lambda function updates.

How do you propose to test this?

Could easily be tested by using the reproduce steps above so long as eu1 is not used as the test network.

Can you do this yourself and submit a Pull Request?

Unfortunately not if the lambda functions are written in Go!

Thanks