We have a done a poc using Amazon EC2 Container Service Plugin and we are successfully able to spin up fargate containers in AWS.
we have multiple Projects and we require multiple Amazon Ec2 container service cloud . As of now we have created multiple Ec2 container service clouds but
we have observed there is no restrictions for binding/restricting the agents on the Folder.
We use Cloud Bees Jenkins and we are familiar with controlled slaves so we were expecting similar kind of functionality to restrict the agents across the
Projects/folders using this plugin
our intention if some one knows the label of the Amazon Ec2 container service cloud from X Project then if he tries to use that label in his Jenkins
job for other project then the containers get spinned up in X account so we wanted to avoid this situation and restrict the agents .