I have a VPC set up in AWS. we have created 2 subnets (A/24 and B/24), straight using all the IP having no IP\'s/Subnets for further usage.
We find that the b/24 is not
It's true that you will never get the AWS web console to display any other value for "Subnet ID" in the instance details. Others have explained how to create new instances that will "be on" the desired subnet. I needed to take an existing server running software that was licensed to "one non-transferable Host ID" and "put it on" a different subnet. (Of course when I say licensed software, I'm talking about Windows software from a vendor who "doesn't support AWS"!) I solved this by:
route print
from the command line.Now everything the machine does is on the desired subnet. It is still reachable on the old IP (and previous subnet) as well as on the new IP (and desired subnet).
This is a pretty narrow case, but I hope it helps someone.