Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Events are not being deposited to custom EventBus QuotaMonitorBus from spoke accounts #188

Open
1 task
mguja-fcc opened this issue Mar 6, 2024 · 5 comments
Labels

Comments

@mguja-fcc
Copy link

mguja-fcc commented Mar 6, 2024

Describe the bug

Events are not being deposited to custom EventBus QuotaMonitorBus from spoke accounts.

To Reproduce

  1. Deploy solution
  2. Have at least a warning item in Trusted Advisor
  3. Invoke Trusted advisor refresh
  4. There is invocation error for StackSet-QM-TA-Spoke-StackSet-3e-TAWarnRule* rule.

Assuming same issue is for the QuotaMonitorSpokeBus

Expected behavior

Warning is sent to SNS topic.

Please complete the following information about the solution:

  • Version: [v6.2.5]
    Temporary fix: had to add scoped down policy to the custom bus QuotaMonitorBus to allow events:PutEvents . Notifications started to come in.
@mguja-fcc mguja-fcc added the bug label Mar 6, 2024
@G-Lenz
Copy link
Contributor

G-Lenz commented Mar 11, 2024

We have added this to our backlog for investigation. Are you able to share the error you saw?

@mguja-fcc
Copy link
Author

I do not but I am sure you will be able easily reproduce. Make sure to remove the solution and then redeploy it.

@mguja-fcc
Copy link
Author

Any update on this ? we want to deploy though code without a need of manual steps. Thanks.

@francotel
Copy link

In my case have this error from lambda spoke (target account):
[WARN] [getMetricData] ValidationError - The values for parameter id in MetricDataQueries are not unique.
[WARN] [getMetricData] ValidationError - Maximum number of SERVICE_QUOTA functions (100) exceeded

@G-Lenz
Copy link
Contributor

G-Lenz commented May 29, 2024

Those errors are a separate issue which we are currently looking into, if you'd like you can open a separate issue for tracking purposes which we can also use to provide any updates on that particular error.

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

No branches or pull requests

3 participants