You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 4, 2024. It is now read-only.
When deploying into an existing VPC with self-managed Active Directory, with EnableAppInsights set to true, we are getting the following error:
"Component arn:aws:ec2:xxxxxxxeast-2:xxxxxxx:instance/i-xxxxxx is grouped in another component" (Service: ApplicationInsights, Status Code: 400, Request ID: f9d3b316-xxxxxxxxxxxxxxxx)" (RequestToken: ef4e2bee-xxxxxxxxxxxxxxxxxx, HandlerErrorCode: InvalidRequest)
As from the error it is evident that ApplicationInsights service is reporting the above error as it finds a conflict with different component name grouping same resources . It was confirmed that another component name “SQLFCI” was created grouping the resource which should be grouped by “SQLHAClusterInstances-MSSQL” instead .
Also CreateComponent API call was only initiated for “SQLHAClusterInstances-MSSQL” which failed .
When deploying into an existing VPC with self-managed Active Directory, with EnableAppInsights set to true, we are getting the following error:
"Component arn:aws:ec2:xxxxxxxeast-2:xxxxxxx:instance/i-xxxxxx is grouped in another component" (Service: ApplicationInsights, Status Code: 400, Request ID: f9d3b316-xxxxxxxxxxxxxxxx)" (RequestToken: ef4e2bee-xxxxxxxxxxxxxxxxxx, HandlerErrorCode: InvalidRequest)
As from the error it is evident that ApplicationInsights service is reporting the above error as it finds a conflict with different component name grouping same resources . It was confirmed that another component name “SQLFCI” was created grouping the resource which should be grouped by “SQLHAClusterInstances-MSSQL” instead .
Also CreateComponent API call was only initiated for “SQLHAClusterInstances-MSSQL” which failed .
Additional Info:
We have launched our self-managed AD by following the following QuickStart: https://aws-quickstart.github.io/quickstart-microsoft-activedirectory/
Deploy scenario 1 (self-managed AD) into a new VPC
The text was updated successfully, but these errors were encountered: