Skip to content
This repository has been archived by the owner on Oct 4, 2024. It is now read-only.

Error: "Component arn:aws:ec2:xxxxxxxeast-2:xxxxxxx:instance/i-xxxxxx is grouped in another component" #25

Open
ar33bm opened this issue May 6, 2022 · 1 comment

Comments

@ar33bm
Copy link

ar33bm commented May 6, 2022

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

@davmayd
Copy link
Contributor

davmayd commented May 13, 2022

When using default values with AWS Managed AD, Application Insights deploys successfully, however when using non-default values it fails.
image

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants