Currently this functionality is not available in Atlas, which is not ideal.
The use case of this is to be able to lock down SCRAM DB users accounts that are used as application service accounts. We should be able to lock these accounts down so that they are only ever used from the application source IPs.... i.e. restricting a support staff user using this service account to gain access to the DB from a place other than the application host.
We cannot use the generic database level ip whitelist functionality for this as it would mean that our support user accounts (that utilise IAM roles) would not be able to connect from support jumphosts.
Hi MongoDB Support,
Currently this functionality is not available in Atlas, which is not ideal.
The use case of this is to be able to lock down SCRAM DB users accounts that are used as application service accounts. We should be able to lock these accounts down so that they are only ever used from the application source IPs.... i.e. restricting a support staff user using this service account to gain access to the DB from a place other than the application host.
We cannot use the generic database level ip whitelist functionality for this as it would mean that our support user accounts (that utilise IAM roles) would not be able to connect from support jumphosts.
Sam