Abstract: Methods and server systems for computing fraud risk scores for various merchants associated with an acquirer described herein. The method performed by a server system includes accessing merchant-related transaction data including merchant-related transaction indicators associated with a merchant from a transaction database. Method includes generating a merchant-related transaction features based on the merchant-related indicators. Method includes generating via risk prediction models, for a payment transaction with the merchant, merchant health and compliance risk scores, merchant terminal risk scores, merchant chargeback risk scores, and merchant activity risk scores based on the merchant-related transaction features. Method includes facilitating transmission of a notification message to an acquirer server associated with the merchant.

Abstract: A resource tag service of a provider network may be used to protect integration between resources of different services by generating dependency tags. When a service receives, from a client, a request for a resource of the service to use another resource of another service, a dependency tag is generated by the resource tag service. The dependency tag indicates that the resource depends on the other resource (e.g., the resources are integrated). When the other service receives, from the client, a request to delete or modify the other resource, the deletion or modification of the other resource is prevented based on the existence of the dependency tag for the other resource (e.g., the dependency tag is attached to the other resource, indicating that the other resource of the other service is integrated with the resource of the service).

Abstract: A resource tag service of a provider network may be used to protect integration between resources of different services by generating dependency tags. When a service receives, from a client, a request for a resource of the service to use another resource of another service, a dependency tag is generated by the resource tag service. The dependency tag indicates that the resource depends on the other resource (e.g., the resources are integrated). When the other service receives, from the client, a request to delete or modify the other resource, the deletion or modification of the other resource is prevented based on the existence of the dependency tag for the other resource (e.g., the dependency tag is attached to the other resource, indicating that the other resource of the other service is integrated with the resource of the service).

Abstract: A managed directory service obtains a request to generate a first account of a first directory within a first network. In response to the request, the managed directory service creates the first account within the first directory. From the request, the managed directory service also obtains credential information of a second account of a second directory within a second network. The managed directory service updates the first account to include this credential information to enable the first account to be used to access the second directory within the second network.

Abstract: A managed directory service receives a request to add a domain controller to a directory. In response to the request, the managed directory service determines, based on locations of other domain controllers of the directory, a location for the domain controller. The managed directory service provisions the domain controller at the location and associates the domain controller to the directory. The domain controller is activated in order to perform directory operations for the directory.

Abstract: Techniques for load balancing based on relative credit balances are described. For example, one embodiment of a method comprises: determining current credit balances for a plurality of compute instances; receiving a request; selecting one of the compute instances to be a destination for the request based on a comparison of the current credit balances; and transmitting the request to the selected compute instance.