The Automation audit log gives you visibility into events that impact your environment as they happen. See below for detail on each audit entry so you know how to read them.
ASG Scale Down & Up
Resources Affected: This refers to the number of Auto Scaling Groups that were either Scaled Up or Down during that task run. Example: "3 Instances"
Description: This gives a brief description of exactly what happened during that task run. Example: "3 groups scaled down"
EC2 Stop & Start
Resources Affected: This refers to the number of EC2 Instances that were either Stopped or Started during that task run. Example: "4 Instances"
Description: This gives a brief description of exactly what happened during that task run. Example: "4 Instances Started"
What does "X Skipped Instances" mean? - Automation doesn't support EC2 instances that have an attached volume that is encrypted. This is due to the permissions required to start instances from an external service. If you schedule a task that includes instances in this state, they will be skipped, so we don't stop something we can't start. In future versions, we will remove these resources from preview.
EBS - Cleanup Unattached Volumes
Resources Affected: This refers to the number of Volumes that were terminated during that task run. Example: "1 Instance"
Description: This gives a brief description of exactly what happened during that task run.
- "1 new attached volumes" - this indicates that we detected a new EBS volume, and it's currently attached. We will monitor it in case it becomes unattached in the future.
- "3 new detached volumes" - this indicates that have detected a new unattached volume, and tagged it with an unattached time. It will be scheduled for snapshot and termination based on the threshold set in your task configuration.
- "3 snapshots created" - This indicates that 3 unattached volumes are scheduled for termination, and we have created snapshots of them ahead of termination, which will happen on the next task run in 1 hour.
- "3 snapshots deleted" - This indicates that we can verify that snapshots were successfully taken on 3 volumes, and we've sent the API calls necessary to AWS to delete 3 volumes.
All Task Types
Last Executed: This is the last time the task ran. For tasks with a schedule, this should always be based on the task schedule. For items that run on a regular cadence like the EBS - Cleanup Unattached volumes task, this is the time related to the specific audit entry you're looking at.
Result: This indicates if the task run was successful, or in the unlikely case, failed. If failure is indicated, you can hover over the error icon for an error code. If this happens, please let us know.
What does "0 Instances Affected" mean? - This means that that audit entry isn't related to an event where we stopped, started, scaled, or terminated a resource. Examples of this are task creation, EBS volume discovery, or EBS snapshot creation.