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

RFE: "monitoring" of AWS configuration using regular CFE dry-runs #106

Open
mikeoleary opened this issue Oct 6, 2022 · 2 comments
Open
Labels
enhancement New feature or request
Milestone

Comments

@mikeoleary
Copy link

Do you already have an issue opened with F5 support?

No

Description

I would like to know if we could have the CFE perform regular "dry-run" failovers, so that if a change was made in the AWS environment that would adversely affect CFE operations, we would find out right away.

Today's scenario:

  1. NetOps team sets up F5 and CFE. Tests failover successfully.
  2. 6 months may pass. Another team may "clean up" tags, edit IAM Roles, or make other changes that aren't communicated.
  3. DR situation occurs but CFE is unable to perform failover due to mis-configuration.

My preferred scenario:

  1. NetOps team sets up F5 and tests CFE.
  2. Another team makes a change to AWS infrastructure but CFE notices this change within a specified time, perhaps 60 mins? It could log the failed Dry Run attempt, which could be monitored by an external system. Ideally, CFE config and AWS config do not get out of sync in this scenario.

Severity level :

  1. Severity 3 (Medium) : Defect is causing intermittent errors in system operations.
@shyawnkarim
Copy link

Thanks for submitting this RFE. I've added it to our backlog, internal ID ESECLDTPLT-3198, to discuss with the team.

@shyawnkarim shyawnkarim added the enhancement New feature or request label Oct 10, 2022
@shyawnkarim shyawnkarim added this to the backlog milestone Oct 10, 2022
@mikeoleary
Copy link
Author

Thank you @shyawnkarim , please email me if you want customer details.

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

No branches or pull requests

2 participants