```Steps to Connect an Existing Node to a New Panel
Update the Node’s Panel URL:

SSH into your current node server.
Edit the core.json configuration file for the node (located in /etc/pterodactyl/config.yml or /srv/daemon/config/core.json depending on your setup).
Look for the panel_url field and update it with the new AWS panel's URL (e.g., https://yournewawspanel.com).
Save the changes.
Generate an API Key in the New Panel:

Log into your new AWS-hosted panel as an admin.
Go to Admin Area > Nodes and click Create Node.
Copy the Node API Key generated during this setup.
Update the API Key on the Node:

Back in your node’s configuration file, look for the token_id and token fields under the panel settings. Replace these values with the new Node API Key you generated.
Make sure that token_id matches the identifier and token is the secret part of the key.
Restart the Node Daemon:

Run the following commands to restart the node daemon:
bash
Copy code
sudo systemctl restart wings
This will reload the configuration changes and connect the node to the new panel.
Verify Connection:

In the new panel on AWS, navigate to Nodes and check if the node appears as connected.
If the connection is successful, your node should display as online and ready to deploy servers.
Test Deployments:

Try deploying a test server or checking resource stats from the panel to confirm that everything is connected properly.
Troubleshooting
Firewall: Ensure that the node can communicate with the new AWS panel IP on the necessary ports (usually port 8080 for the Wings Daemon).
SSL Configuration: If your new panel URL is using HTTPS, make sure the SSL certificate is valid; otherwise, the node might have trouble connecting if it requires a secure connection.
Logs: Check the Wings log on the node (/var/log/wings.log) for any errors if it fails to connect.
This process should link your existing node to the new AWS-based panel, allowing you to manage it from the new interface. Let me know if you run into any issues during the process!```