- 最新
- 投票最多
- 评论最多
I found the issue. When replicating the on premise server, I had an AnyDesk installed which is what I used to connect remotely to the Oracle Linux 8.5 instances. It seems that both servers having the same connection key, when connecting through my work PC using the same key it was alternating between both somehow. I went ahead and disabled AnyDesk on the EC2 instances.
Rookie mistake.
Thank you very much for your response.
Hello,
Regarding the situation you mentioned:
However, today I found out that the on-premise application and database server are now showing AWS EC2's public IPv4 and private IPv4. I got extremely worried because I changed a user's password on premise but the on premise but the user was unable to enter with the new password, I launched the test environment and I managed to login with the credentials I had just changed.
This behavior is not normal for the AWS Application Migration Service migration process as the purpose of this process is to essentially replicate your source machine in AWS, not alter or make significant changes (such as IP address changes or existing user password changes) within the source machine. I would strongly recommend opening up a support case with the AWS Application Migration Service team to investigate this further.
相关内容
AWS 官方已更新 1 年前
Hey Juan,
I found the issue. When replicating the on premise server, I had an AnyDesk installed which is what I used to connect remotely to the Oracle Linux 8.5 instances. It seems that both servers having the same connection key, when connecting through my work PC using the same key it was alternating between both somehow. I went ahead and disabled AnyDesk on the EC2 instances.
Rookie mistake.
Thank you very much for your response.