Grouped EB Environments, env.yaml, and .ebextensions

Recently, we've decided to pull our workers out of our servers and have them run in their own EB environment. Since both server and worker environments require the same code base, we established them as a "Group" and deploy to them using the eb deploy --modules component-a component-b command.
Deployment is successful; however, there seems to be a clash between the env.yaml file required for grouping EB environments and the .ebextensions folder. For example, during deployment the following error is thrown:

WARN: Error processing file (Skipping): 'env.yaml' - Contains invalid key: 'SolutionStack'. For information about valid keys, see http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/ebextensions.html

And upon further inspection, the .ebextension folder (both nested in their respective modules) doesn't execute uniquely per environment. Both environments operate as if they shared the same .ebextensions folder. For reference here's our folder setup:

~/project-name
|-- component-a
|-- .elasticbeanstalk |_______-- config.yml
|-- .ebextensions |_______-- unique config files for component-a...
|___-- env.yaml -- component-b
___-- .elasticbeanstalk _______-- config.yml
___-- .ebextensions _______-- unique config files for component-b...
___`-- env.yaml

Removing .ebextensions doesn't change the outcome as expected... I'm not sure if I've set up my configuration files correctly? I'm hoping these forums can shed some light on this issue.

Edited by: dpfeifer on Jun 19, 2020 4:14 PM