AWS instances monitoring in ca-central-1 region

mike — Thu, 01 Jul 2021 13:29:23 GMT

We're trying to integrate our AWS environment with Dynatrace, we used the key-based access with the following policy:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "autoscaling:Describe*",
                "cloudwatch:Describe*",
                "cloudwatch:List*",
                "cloudwatch:Get*",
                "ec2:Describe*",
                "ec2:Get*",
                "ec2:ReportInstanceStatus",
                "elasticache:DescribeCacheClusters",
                "elasticloadbalancing:Describe*",
                "sqs:GetQueueAttributes",
                "sqs:ListQueues",
                "rds:DescribeDBInstances",
                "SNS:ListTopics",
                "s3:Get*",
                "s3:List*"
            ],
            "Effect": "Allow",
            "Resource": "*"
        }
    ]
}

But the problem is when we go check in the AWS section, we can only see our instance in the us-east-1 region, not in the ca-central-1 region. We have only 1 instance in us-east but 8 in ca-central.

Strangely though, we can see all the buckets, both the ones in us-east and ca-central.

I was told by support that it might have something to do with Cloudwatch but we checked it and it seems to be working fine.

Anyone has an idea?

Re: AWS instances monitoring in ca-central-1 region

pawel_brzoska — Tue, 26 Jun 2018 09:13:57 GMT

Sorry for late reply, ca-central-1 is supported since 1.121. Should work now.

topic AWS instances monitoring in ca-central-1 region in Cloud platforms

AWS instances monitoring in ca-central-1 region

Re: AWS instances monitoring in ca-central-1 region