Access control policy for infrastructure providers

At present for most of the infrastructure providers that we use which provide an admin console to creating and managing the machines we use a shared username and password. In order to make it easier to add/remove users we should look at the feasibility with each provider of allow them to use their own personal IDs to gain the accountability, logging, and ability to easily revoke access that this would provide. We may end up with a different solution on each provider but this will let is clarify what ius feasible and what the process is for the project.

- [ ] Amazon
- [ ] Azure
- [ ] DigitalOcean
- [x] Equinix
- [ ] Hetzner
- [x] IBM
- [ ] MacStadium
- [ ] MacInCloud
- [ ] Marist
- [ ] Nine
- [ ] OSUOSL (PPC)
- [ ] PLCTLab
- [ ] Scaleway
- [ ] Skytap