Description
With IP Filtering on Confluent Cloud, there may be a situation in which you are implementing IP Filtering policies to prevent unauthorized access, but in doing so you find yourself locked out after applying changes.
Applies To
Confluent Cloud with IP Filtering Policies Enabled
Resolution
Please ensure you are following this guide as a first level of recovery before engaging with Confluent Support, as you will be asked to try the below method(s) first and foremost as bypassing manual access controls requires approval from the highest levels in Confluent Security Organization. This process is necessarily strict to ensure we are protecting our customers from social engineering attacks.
As a first step, please reach out to other OrgAdmins within your organization to attempt login and access connecting from different network locations, as there may be other admins able to meet the IP Filter requirements and gain access, in which they can then revert IP Filter changes made.
Please note that Confluent Support cannot provide any PII (Personal Identifiable Information) on other OrgAdmins within your organization to reach out with as this can be used as a potential attack vector or to gain private information. Confluent Support can however send out an email to other OrgAdmins within your organization to alert them of the situation with IP Filtering Policy.
If the above option is not possible, you should then open a Support Ticket with Confluent Support. Please ensure that your support ticket provides the following information.
1. Short Summary of Lockout Situation, e.g. At what time and what IP Filter rules did you implement prior to being locked out.
2. Please also confirm that you've reached out to all other orgAdmins within your Organization to confirm that they cannot access Confluent Cloud Console.
3. Indicate if this is a Request that we notify all orgAdmins within your organization of the current incident (we will provide time noted, rule implemented and who is making said request)