Abstract: Systems and methods for inter-service authentication are disclosed. In one embodiment, a system may include a plurality of services and a cloud platform. The first service may generate a token comprising a first service identifier for communicating with a second service, and may request, from the cloud platform, a private key for the first service. The cloud platform may provide the private key to the first service. The first service may sign the token with the private key and may communicate a request to the second service with the signed token. The second service may retrieve the first service identifier and may request, from the cloud platform, a public key for the first service identifier. The cloud platform may provide the public key to the second service. The second service may validate the token using the public key, and may grant the request in response to the validation.

Abstract: A system and method for injecting network chaos between a client system and a server system within a network are disclosed. A processor implement a chaos controller DNS (Domain Name System) server and configures a client application running on the client system to utilize the chaos controller DNS server as a DNS server. The processor also selects the chaos controller DNS as the DNS server and implements a chaos controller application programming interface (API) and a chaos controller central server; and orchestrates a type and a duration of a network chaos injection by utilizing the chaos controller API and the chaos controller central server without modifying an application code of the client application.

Abstract: Systems and methods for inter-service authentication are disclosed. In one embodiment, a system may include a plurality of services and a cloud platform. The first service may generate a token comprising a first service identifier for communicating with a second service, and may request, from the cloud platform, a private key for the first service. The cloud platform may provide the private key to the first service. The first service may sign the token with the private key and may communicate a request to the second service with the signed token. The second service may retrieve the first service identifier and may request, from the cloud platform, a public key for the first service identifier. The cloud platform may provide the public key to the second service. The second service may validate the token using the public key, and may grant the request in response to the validation.

Abstract: Systems and methods for inter-service authentication are disclosed. In one embodiment, a system may include a plurality of services and a cloud platform. The first service may generate a token comprising a first service identifier for communicating with a second service, and may request, from the cloud platform, a private key for the first service. The cloud platform may provide the private key to the first service. The first service may sign the token with the private key and may communicate a request to the second service with the signed token. The second service may retrieve the first service identifier and may request, from the cloud platform, a public key for the first service identifier. The cloud platform may provide the public key to the second service. The second service may validate the token using the public key, and may grant the request in response to the validation.

Abstract: Embodiments disclosed herein provide for systems and methods for implementing chaos engineering in distributed systems with chaos engineering trials. The systems and methods provide for a RESTful API that is configured to generate a chaos engineering experiment including a plurality of steps that test one or more conditions in the distributed system as well as generate a chaos engineering trial based on the chaos engineering experiment and one or more parameters.

Abstract: A system and method for injecting network chaos between a client system and a server system within a network are disclosed. A processor implement a chaos controller DNS (Domain Name System) server and configures a client application running on the client system to utilize the chaos controller DNS server as a DNS server. The processor also selects the chaos controller DNS as the DNS server and implements a chaos controller application programming interface (API) and a chaos controller central server; and orchestrates a type and a duration of a network chaos injection by utilizing the chaos controller API and the chaos controller central server without modifying an application code of the client application.

Abstract: Systems and methods for automated cloud infrastructure operations using a structured inventory are disclosed. In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for automated cloud infrastructure operations using a structured inventory may include: (1) receiving unstructured data from a platform, wherein the unstructured data comprises unstructured inventory operational data; (2) transforming the unstructured data into structured data; (3) identifying at least some of the structured data as emerging reference data based on a request for at least some of the structured data; (4) providing at least some of the emerging reference data to an inventory event stream; and (5) applying a template to the inventory event stream to generate an authoritative inventory.

Abstract: Embodiments disclosed herein provide for systems and methods for implementing chaos engineering in distributed systems with chaos engineering trials. The systems and methods provide for a RESTful API that is configured to generate a chaos engineering experiment including a plurality of steps that test one or more conditions in the distributed system as well as generate a chaos engineering trial based on the chaos engineering experiment and one or more parameters.

Abstract: Systems and methods for inter-service authentication are disclosed. In one embodiment, a system may include a plurality of services and a cloud platform. The first service may generate a token comprising a first service identifier for communicating with a second service, and may request, from the cloud platform, a private key for the first service. The cloud platform may provide the private key to the first service. The first service may sign the token with the private key and may communicate a request to the second service with the signed token. The second service may retrieve the first service identifier and may request, from the cloud platform, a public key for the first service identifier. The cloud platform may provide the public key to the second service. The second service may validate the token using the public key, and may grant the request in response to the validation.

Abstract: Systems and methods for inter-service authentication are disclosed. In one embodiment, a system may include a plurality of services and a cloud platform. The first service may generate a token comprising a first service identifier for communicating with a second service, and may request, from the cloud platform, a private key for the first service. The cloud platform may provide the private key to the first service. The first service may sign the token with the private key and may communicate a request to the second service with the signed token. The second service may retrieve the first service identifier and may request, from the cloud platform, a public key for the first service identifier. The cloud platform may provide the public key to the second service. The second service may validate the token using the public key, and may grant the request in response to the validation.

Abstract: Systems and methods for automated cloud infrastructure operations using a structured inventory are disclosed. In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for automated cloud infrastructure operations using a structured inventory may include: (1) receiving unstructured data from a platform, wherein the unstructured data comprises unstructured inventory operational data; (2) transforming the unstructured data into structured data; (3) identifying at least some of the structured data as emerging reference data based on a request for at least some of the structured data; (4) providing at least some of the emerging reference data to an inventory event stream; and (5) applying a template to the inventory event stream to generate an authoritative inventory.