The error is ListMetricsRequest failed: send request failed. followed by a proxy error driven by an incorrect URL because this is running in us-iso-east-1 and doesn't push the config to the metric checks. My logs show the iam/sts calls are working going to iam.us-iso-east-1.c2s.ic.gov and sts.us-iso-east-1.c2s.ic.gov however the calls I see going to metrics are ec2.us-iso-east-1.amazonaws.com and monitoring.us-iso-east-1.amazonaws.com. This leads me to believe that the endpoint is not getting to the metric checks and the region is not pushing to the initial IAM checks.
I have tried that config and the issue then gets worse as the iam and sts calls will also fail as they need to use the region in the iso env. The same issue is also present with the above config that the metric calls do not hit that endpoint. Will the endpoint PR above correct both of these issues?
So the calls need to be to sts.iam.us-iso-east-1.c2s.ic.gov, iam.us-iso-east-1.c2s.ic.gov, and ec2.iam.us-iso-east-1.c2s.ic.gov for example
This will call iam.c2s.ic.gov and ec2.us-iso-east-1.c2s.ic.gov for example. I don't think there will be anything like ec2.iam.us-iso-east-1.c2s.ic.gov though with two service names.
Is it possible to have the region included in the iam and sts calls? in the aws-iso the iam and sts addresses include the region as there is no global endpoint for those services
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.