Skip to main content

The api.lacework.net agent url will retire on October 31, 2023, and will be replaced with agent.lacework.net.

  • Is there a way to have the agent change its own target?
  • Is there a way to get a report on which IP addresses are using the old endpoint before the retirement?

Agent

N/A

Platform

Using Lacework/Operationalizing

Cloud

AWS

Hello, thank you for posting your question on the Lacework Community! 

 

The Lacework notification of the agent url migration was released too early and was recently pulled back. We are making adjustments to ensure customer impact is as small as possible. The agent url migration will go into effect in 2024 and additional communications with details will be released. 

 

To answer your questions, when the agent url migration occurs next year, agents as of v6.2 will be able to auto-redirect to the correct URL so we encourage all customers to upgrade to the latest agent version if possible.  Lacework also stores the config for each agent in the backend so we would be able to generate a report indicating with IP addresses are using the old endpoint. 

 

Please follow up if there are any additional questions! :) 

Reply


Terms of UseCookie settings