Abstract:
A distributed execution environment provides resources such as computing resources, hardware resources, and software resources. One or more resource data providers might also operate in conjunction with the distributed execution environment to provide resource data describing various aspects of the resources in the distributed execution environment. A query service may obtain resource data provided by the resource data providers in order to generate responses to queries. In order to obtain the resource data from the resource data providers, the query service may utilize various “pull” and “push” mechanisms. Using a push mechanism, the resource data providers push resource data to the query service. Utilizing a pull mechanism, the query service pulls the resource data from the resource data providers. The query service might also store resource data received from the resource data providers in a cache and utilize the cached resource data when responding to queries for resource data.
Abstract:
A distributed execution environment includes various resources, such as instances of computing resources, hardware resources, software resources, and others. A resource state viewing tool executing in conjunction with the distributed execution environment provides access to data regarding the state of each resource in the form of a resource page associated with the resource. The resource page for a resource might also include one or more annotations assigned to the resource by a user or by a component within the distributed execution environment. The annotations might have associated expiration data, such as an expiration time or event, which may be utilized to expire the annotations. The annotations might also have a namespace assigned thereto that is utilized when responding to requests to retrieve the annotations. The annotations might also have permissions assigned thereto that identify the rights of one or more users and/or components to read, modify, or delete the annotations.
Abstract:
A network visualization service may auto-generate graphical, dynamic, and interactive network diagrams of the infrastructure (resource instances, connections, etc.) of clients' virtual private networks as implemented on a provider network. A network diagram may include representations of various virtualized components of a client's virtual private network, as well as relationships among and connections between and among the various components. The diagram may also display logical and/or geographical groupings of the virtual resources in the client's virtual private network. The service may track changes to the virtual private network and update the diagram accordingly. The diagram may provide a user interface via which the client may select particular graphical objects on diagram to display additional information about a respective resource instance or connection and/or to change the client's virtual private network configuration via the network diagram.
Abstract:
A network visualization service may auto-generate graphical, dynamic, and interactive network diagrams of the infrastructure (resource instances, connections, etc.) of clients' virtual private networks as implemented on a provider network. A network diagram may include representations of various virtualized components of a client's virtual private network, as well as relationships among and connections between and among the various components. The diagram may also display logical and/or geographical groupings of the virtual resources in the client's virtual private network. The service may track changes to the virtual private network and update the diagram accordingly. The diagram may provide a user interface via which the client may select particular graphical objects on diagram to display additional information about a respective resource instance or connection and/or to change the client's virtual private network configuration via the network diagram.
Abstract:
Requests to change attributes of servers or other computing resources can be validated by a veto service. For example, the veto service can receive requests to register for notification of changes to an attribute for a server, send a notification of a pending change to the attribute to each of a plurality of services, determine a response to the notification for each service, and based on the responses decide whether to allow or deny the pending change to the attribute. The responses from the notified services can be received responses or default responses.