EC2 Instance in Non-existent VPC after Shared Resource Deletion

Question

I have create a shared resource (subnet ) using AWS Resource Access Manager (RAM) in Account A and share a subnet with organization account   Account B and then in the other account Account B, i created an EC2 instance in that shared subnet in Account B.
The shared resource in Account A was deleted after some time and I went back to Account B to check if the EC2 instance was still working. Ec2 instance was active and running. However, the shared VPC does not exist anymore in Account B.
If this is the correct behavior, If yes does it mean we can run an EC2 instance with a non-existent VPC?

Accepted Answer

I can't start a new one, but I don't think it affects resources that are already active.  
https://repost.aws/knowledge-center/delete-shared-vpc  
> Un-sharing subnets doesn't have a direct impact on the active resources. However, you must terminate all active resources within the shared or un-shared VPC to delete the parent VPC. To verify active resources, do the following:

EC2 Instance in Non-existent VPC after Shared Resource Deletion

Relevant content