Changing any setting for Elastic Beanstalk fails with multi instance environment

Attached below is my deployment config but these steps should be reproducible with any multi instance setup (screenshot pointing out option that needs to be unchecked).

Any attempt to change any setting fails with the deployment log below. To be more specific, my own experiences was with settings under the "Server" and "Advanced" tab. It seems to be load balancer related which is why I am being very explicit about the multi instance setup.

Time | Type | Details
-- | -- | --
2020-04-09 10:55:33 UTC-0700 | INFO | The environment was reverted to the previous configuration setting.
2020-04-09 10:55:01 UTC-0700 | ERROR | Failed to deploy configuration.
2020-04-09 10:55:01 UTC-0700 | ERROR | Updating load balancer named: arn:aws:elasticloadbalancing:us-west-2:746894333746:loadbalancer/app/awseb-AWSEB-1JV5MT3RHF926/552daf6fcbb66e82 failed Reason: Property SecurityGroups contains duplicate values.
2020-04-09 10:55:00 UTC-0700 | ERROR | Service:AmazonCloudFormation, Message:Stack named 'awseb-e-kh4jczkhpc-stack' aborted operation. Current state: 'UPDATE_ROLLBACK_IN_PROGRESS' Reason: The following resource(s) failed to update: [AWSEBV2LoadBalancer].
2020-04-09 10:54:44 UTC-0700 | INFO | Updating environment EBLabB-prod's configuration settings.
2020-04-09 10:54:38 UTC-0700 | INFO | Environment update is starting.

[ebconfig.txt](https://github.com/aws/aws-toolkit-visual-studio/files/4457827/ebconfig.txt)


Start with the attached ebconfig.txt and screenshot, then reproduce the failure in a multi-instance Elastic Beanstalk environment using settings from the Server or Advanced tab. Check the deployment log for the duplicate SecurityGroups error and rollback; done means changing a setting completes without the load balancer update failing.

Written by the indexing model from the issue text.