Changed IP settings inside the RDP instance in windows settings, now I can't access the instance.

1. Access the EC2 Console: Log in to your AWS Management Console. Navigate to the EC2 Dashboard.
2. Stop the Instance: Select the instance you are having trouble with. Click on the "Instance state" dropdown and choose "Stop instance." Wait for the instance to fully stop.
3. Detach the Root Volume: After the instance is stopped, select the instance, then go to the "Actions" menu. Under "Instance Settings," choose "Detach Volume." Note the volume ID for later use.
4. Attach the Volume to a Different Instance: Attach the detached root volume to another instance as an additional volume (e.g., /dev/sdf). You can create a temporary instance if needed.
5. Access the Attached Volume: RDP into the instance where you attached the volume. Open "Disk Management" in Windows, and find the attached volume. Assign a drive letter to the volume if it doesn't have one already.
6. Modify the Network Settings: Navigate to the \Windows\System32\drivers\etc\ directory on the attached volume. Open the interfaces file in a text editor. Revert the changes you made or set it to use DHCP by editing the IP settings.
7. Detach and Reattach the Volume: Once you've fixed the network settings, detach the volume from the temporary instance. Reattach it to the original instance as the root volume.
8. Start the Instance: Go back to the EC2 console, select your original instance, and start it. Attempt to connect to it via RDP using the correct IP settings.
9. Reconfigure Network Settings (Optional): Once you've regained access, consider setting the IP settings to use DHCP to avoid this issue in the future or ensure that any static IP addresses you use are correctly configured within the network's subnet.

** Be cautious about modifying the root volume, as it contains all your instance data.**