Abstract: A domain registry (DR) service executing within a service provider network protects data, such as account data, that is associated with different accounts for testing and/or performing other operations/actions by registering an account with one or more domains. The DR service may register an account in one or more domains based on a request by a user. The operations performed that uses/changes data associated with accounts may be restricted based on the domains for which an account is registered. For example, an account that is registered in a “testing” domain may have different workflows/operations performed using the account data associated with the account registered in the testing domain as compared to an account that is not part of the testing domain.

Abstract: A system can be configured to receive an onboarding request for a service and an API associated with the service. An API configuration defining access permissions, API call structures, and available operations can be determined for the service by an onboarding service. The API configuration can be utilized by the onboarding service to register the API with a proxy server such that incoming API calls are redirected to an access endpoint associated with the service. The proxy server enables the service and the API to be updated via the onboarding requests as service modification and API modification can be submitted, validated, and integrated into a service environment due to the proxy server decoupling the API from the service.

Abstract: Techniques for auto-intrusive data pattern and test case generation for negative service testing are described. A test engine obtains negative test information specifying negative test input examples or schemas associated with tests that are expected to fail. A test generator generates multiple test cases based on the negative test information. A test execution orchestrator splits each test case up into actions that are inserted into queues, where workflow execution agents perform the tests by reading from the queues and interacting with services. The tests may also include adjusting a rate of transactions allowed between top-level services and/or downstream services. Results from the testing are analyzed by a test analysis engine and used to inform the services or the test originator of test cases where the expected failures did not arise.

Abstract: Techniques for testing and validating content generated by applications provided by a provider network are described. A test execution service is disclosed that provides users with a framework for testing the functionality of an application provided by a provider network. A content validation service is disclosed that provides users with a framework for validating content generated by the application by orchestrating the execution of objects to be validated as part of validating content generated by the application. The content validation service generates a validation result for a user by comparing expected data values corresponding to an object to be validated with corresponding actual data values. The disclosed content validation service provides users with the ability to define objects and object definitions for objects to be validated as part of validating content generated by applications provided by the provider network.

Abstract: Devices, systems, and methods are provided for detecting and mitigating application programming interface (API) anomalies. A method may include identifying, based on a first data log, first API data associated with a first API call and a first computer service, and identifying an agreement associated with the first computer service, the agreement including criteria associated with the first API data. The method may include determining that the first API data fails to satisfy the criteria. The method may include determining one or more service dependencies, the one or more service dependencies indicating that operation of the first service depends on operation of a second computer service. The method may include determining, based on the one or more service dependencies, one or more services to which to send notifications indicative of the criteria. The method may include sending the notifications to the one or more services.