What type of logging operation is used to capture changes to resources, such as EC2 instances?

The concept of capturing changes to resources, such as EC2 instances, typically relies on logging operations that can track modifications or alterations made to those resources over time. The appropriate mechanism for this purpose often involves operations that log changes rather than just the initial state or any read operations.

Change logs specifically track changes; hence, they maintain an audit of modifications happening to configurations or states of resources. This enables administrators to review what changes occurred, when, and potentially who made those changes. Logging these operations helps in maintaining compliance, diagnosing issues, and understanding the evolution of resource statuses.

Thus, the correct answer for the operation that captures changes to resources is inherently connected to the nature of logging those changes, which is often characterized as capturing write operations rather than just read operations or maintaining a complete historical log without focus on changes. The option that aligns best with the requirement of tracking those alterations directly is the change-log, as it is designed explicitly for this purpose. The implementation of such logs is crucial for effective resource management and security oversight, particularly in environments like cloud infrastructure where resource state can change frequently.