Bug 1251234 - Unavailable AWS Config service causes many SNS requests
Summary: Unavailable AWS Config service causes many SNS requests
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.6.0
Assignee: Greg Blomquist
QA Contact: Jeff Teehan
URL:
Whiteboard: ec2:cloud:event
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-06 18:02 UTC by Greg Blomquist
Modified: 2016-10-03 16:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-29 14:59:08 UTC
Category: ---
Cloudforms Team: AWS
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 0 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 18:50:04 UTC

Description Greg Blomquist 2015-08-06 18:02:00 UTC
https://github.com/ManageIQ/manageiq/issues/3740

Manage IQ creates excessive SNS requests when it has Event Monitor role enabled, Amazon Cloud provider enabled but AWS Config Topic for SNS was not setup. This has potential to wipe out the 'free' 1 million SNS requests limit within a day or two.

Comment 1 Greg Blomquist 2016-02-19 21:48:41 UTC
https://github.com/ManageIQ/manageiq/pull/4939

Comment 2 Jeff Teehan 2016-04-25 18:12:04 UTC
It's a little hard for me to turn off amazon temporarily, so I just left it running over the weekend to make sure there were no regressions.  I read the code changes and they look good.

I'll leave the CloudWatch SNS reports running for a while and will reopen if I see something.  If you know how to take amazon offline, please let me know.

Comment 4 errata-xmlrpc 2016-06-29 14:59:08 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1348


Note You need to log in before you can comment on or make changes to this bug.