AWS Chatbot commands not working yet? Could not connect to the endpoint URL

[jusdino]

AWS Chatbot commands not working yet? Could not connect to the endpoint URL

[tim-finnigan]

Thanks for letting us know — the AWS Health Dashboard should highlight any ongoing issues affecting service health. As mentioned the Chatbot team has updated their documentation to note the supported regions, and still has a few other places in their documentation to update. I think we can close this as their are no action items on our end, but for any other issues related to this you can let us know and we can escalate those to the Chatbot team.

[jusdino]

I just found a region that works:

$ export AWS_DEFAULT_REGION=us-east-2
$ aws chatbot describe-slack-channel-configurations
{
    "SlackChannelConfigurations": []
}

Is this some sort of mismatch because chatbot is a 'global' service, but you can't call other regional endpoints?

[tim-finnigan]

Thanks for reporting this issue, the service team is aware and currently in the process of updating their documentation.

This page has since been added which highlights the supported regions: https://docs.aws.amazon.com/chatbot/latest/APIReference/Welcome.html

As noted there:

AWS Chatbot APIs are currently available in the following Regions:

• US East (Ohio)
• US West (N. California)
• US West (Oregon)
• Asia Pacific (Singapore)

So in terms of region codes currently supported that is: us-east-2, us-west-1, us-west-2, ap-southeast-1.

There are still a handful of incomplete/inconsistent areas in the Chatbot documentation which they are aware of, and should be addressing in the near future. To send feedback on the documentation please use the Provide feedback at the bottom of the API documentation pages.

[jusdino]

That's interesting, since us-east-1 and us-west-1 were the two regions I was trying when I opened the ticket in the first place. For what it's worth, those regional hostnames had no A records when I did a DNS lookup when I opened it, but now they work for me. It's almost like there was an unreported chatbot outage or something.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.