resource

Resources, in the most general sense, are things, usually physical or logical components, onto which services are provisioned. Resources are considered to be grid components within the context of the EGA reference model. Examples include server hardware, network switches, disc arrays, software media and so forth. See also: Grid Component

As part of the WSRF strategy of keeping the web service and the state information separate from each other, the state information is kept in a separate entity called a resource.

Any component in a computing system or network used to perform a specific computing task (storage, servers, data, database server, application server, etc.).

Data, metadata, a collection of data, or a collection of metadata accessed as a content item. Examples: a document, a database table, a content class.

In real-time collaboration, a user object in Active Directory that represents a facility. A resource is used by Outlook users for booking meetings and data conferences. Resources are stored in the "System Exchange" Organization Unit in the Active Directory. [Exchange 2000]

Anything placed in the Exchange store. A resource can be an e-mail message, an appointment, another folder, a Web page, or any structured document, such as a Microsoft Excel spreadsheet. [Exchange 2003]

Anything that has a valid unique resource identifier (URI).

For failover clusters or server clusters, a physical or logical entity that is capable of being managed by a cluster, brought online and taken offline, and moved between nodes. A resource can be owned only by a single node at any point in time.

1. The objects you work with on AWS. This includes buckets, domains, instances, queues, and so on.
2. Tools, code, and documents that AWS provides to support users.
3. An object that the principal requests access to. The resource is C in the statement "A has permission to do B to C where D applies."
4. A required element of an AWS CloudFormation stack. Each stack contains at least one resource, such as an Auto Scaling LaunchConfiguration. All resources in a stack must be created successfully for the stack to be created.

See Uniform Resource Locator (URL).

Anything used or consumed while performing a function. The categories of resources are: time, information, objects (information containers), or processors (the ability to use information).Specific examples are: CPU time; terminal connect time; amount of directly-addressable memory; disk space; number of I/O requests per minute, etc [TCSEC].