[Server] Allow to Add AWS IAM Role
Hi, Please allow to add AWS IAM role for VM service (remote docker & machine executor). Thanks
Support User Management via API
It is currently very difficult for CircleCI server Admins to search and find users for cleanup and deletion. Cleanup currently requires an SSH connection and a script that needs to be updated for every user. It would be helpful to have an API that can be used to delete and manage users (particularly for instances with a large number of users)
Status page for CircleCI Server Installation
Custom Status page for CircleCI Server Installation is a nice feature to have, especially when it grows big. Currently, CircleCI Server does not have any feature to communicate server incidents to developers. It would also be useful to update status page automatically, based on the metrics.
Allow HTML tagging in announcement banner in Server
Restrict Personal repos
Currently, if we integrate a GitHub Org with CircleCI. It allows users of that Org to trigger build for repos in that org as well as repos in their personal account. There should be option to restrict build only to the repos in the Organization.
Server Insights should report resource utilization by project
Customers would like the ability to view and restrict how build resources are being used on a project level
Support ACM TLS certificates for Circle 3.x load balancers
AWS provides Amazon Certificate Manager, a fully automated solution for provisioning and managing certificates, including for certificate renewals. Server 3.x currently requires a cert file for Load Balancer certificate configuration. Support for ACM would be very beneficial for AWS customers to easily setup and manage certs with Server installations.
Encrypted EBS Volumes for vm-service
Please provide option to have encrypted EBS data volumes for vm-service
Allow frontend customizations to menu, announcement banner in Server
Add the ability to add custom items to the Support menu (e.g. internal company support page link), and banner notifications after a user has signed in (e.g. maintenance window announcements) CCI-I-1367
Allow VMs to launch in multiple subnets
Depending on customer networking configuration and demand for VM executors, it can be challenging to allocate a single subnet that is large enough to meet demand and allow room for expansion. It would be helpful if Circle accepted multiple subnets when launching VMs, as it's often easier to add a second non-contiguous subnet than create a new large one and migrate all usage. While subnets could ideally be in multiple availability zones, I realize this makes cache EBS volume management more challenging. Requiring that all subnets are in the same AZ is a reasonable restriction for an initial version of this feature.