Description of problem:
After creating a CR for E2C and then creating a compute profile on top of it, the EC2 subnet is unavailable, which prevents the 'Security Groups' field from displaying its value.

How reproducible:

100%

Is this issue a regression from an earlier version:

Yes

Steps to Reproduce:

1. Infrastructure -> Compute Resources(CR) -> Create CR with EC2 provider

2. Select CR -> Compute profiles -> Select any compute profile

Actual behavior:
For EC2 subnets, the security groups do not display any default value because the subnet is invalid and does not exist on the AWS cloud.

Expected behavior:
EC2 subnet, should remove.