Has anyone successfully provisioned IoT in this Amazon AWS Region/Endpoint: iot.ap-northeast-1.amazonaws.com ?

[johnwest]

Hello,

It looks like a possible policy issue - but I was wondering if anyone here has  successfully provisioned IoT in this Amazon AWS Region/Endpoint: iot.ap-northeast-1.amazonaws.com ?

Thanks,
johnwest

[SwRa]

Hi,

I have not tried this, but it looks like it shouldn't be a problem. Kindly check this. Just make sure that the IoT core instance where the devices are created is in the correct region. Try checking your region. 

If you are using the developer console, there should be a dropdown menu in the upper right corner where you can change the region.

Regards,

Swathy

[SwRa]

Also, you could try referring to this guide.

Regards,

Swathy

[johnwest]

Hello Swathy,

Yep - did that - and that's why I'm posting here.  It appears to be a policy issue.  No matter what I do - the IoT ARN always lands in us-east-1.

Maybe you can try what you've suggested and verify it works.

The issue is the policy JSON - no matter what I try there - it always lands in us-east-1.

My JSON-foo isn't great (obviously) - since it's an infinite open bag as to what the correct syntax is for forcing the ARN to land in a certain Region/Endpoint.

Go ahead and do what you've suggested and show (prove) you can control where the Region/Endpoint lands.

I'll look for your post and steps and JSON syntax.

Thanks,
johnwest

[SwRa]

Hi John,

I see that you have your problem solved in this other ticket. Kindly continue your conversation there. I am closing this ticket.

Thank you,

Swathy