<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00007eRP55CAGOkta Identity EngineAdvanced Server AccessAnswered2024-04-16T13:09:34.000Z2022-05-16T15:47:52.000Z2022-05-23T20:45:58.000Z

u0w3z (u0w3z) asked a question.

Updating AWS CLI version caused Okta ASA to reregister EC2 instances

We updated our AWS CLI version and it appears to have caused an issue where Okta ASA created a duplicate entry in the UI (where hostname and IP address are the same but all other metadata is different). Does anyone have a fix for this? or any recommendations on a move-forward approach on this?

Thanks!!


  • This has typically not been seen but the best way is to view the logs and see what is causing the new server id to be created/issued

This question is closed.
Loading
Updating AWS CLI version caused Okta ASA to reregister EC2 instances