The aws monitoring of checkmk differentiates between global and local services.
For global services, and for getting an access token via sts service, checkmk
assumed that the global region "us-east-1" can be used.
This assumption is wrong. When hosting aws services in the following regions,
you have to use said regions to access the global services:
The error message visible in the debug output of the aws special agent was:
An error occurred (InvalidClientTokenId) when calling the GetCallerIdentity operation: The security token included in the request is invalid.
The global service region can now be configured.
To the list of all Werks