Symptoms

You see an error similar to the following during instance launch:

Security group sg‑xxx and subnet subnet‑xxx belong to different networks.

Cause

The Elastigroup configuration includes one or more subnet IDs that are not compatible with the configured security groups. Although both resources exist, they belong to different VPC networks, which AWS does not allow for instance launches.

Solution

1. Open the Elastigroup configuration

   In the Flexera console, navigate to Elastigroup, select Groups, and then select the affected Elastigroup.
   
   

2. Edit the configuration in JSON mode

   Select Actions, then Edit configuration, choose Review, and open the JSON view in Edit mode.
   
   

3. Update the subnet configuration

   In the compute.availabilityZones section, locate the subnetIds list.

   Remove the subnet IDs that are referenced in the error message and do not belong to the same VPC as the configured security groups.
   
   

4. Save the configuration

   Save your changes and apply the updated configuration.