2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
1
Consider looking at CloudWatch Metrics to gain insight into the operations aspect. CloudWatch metrics for Data Lifecycle Manager reports success and error metrics. These metrics might be enough for you to create alarms to be triggered when resources are not created, copied or deleted, allowing you to take immediate action to diagnose and fix potential issues.
Additionally, Data Lifecycle Manager generates a “DLM Policy State Change” event if a policy enters the error state. Refer to Monitor your policies using CloudWatch Events. You could look at triggering a notification based rule based on this type of event.
beantwortet vor 2 Jahren
0
I think it would be best to use EventBridge and SNS.
Sample Event Pattern
{
"source": ["aws.backup"]
}
Sample Test Event
{
"version": "0",
"id": "12345678-5f35-d9a2-76d1-613683e4e024",
"detail-type": "Backup Vault State Change",
"source": "aws.backup",
"account": "123456789012",
"time": "2020-06-24T23:18:19Z",
"region": "us-east-1",
"resources": ["arn:aws:backup:us-west-2:123456789012:backup-vault:SampleVault"],
"detail": {
"backupVaultName": "SampleVault",
"state": "CREATED"
}
}
beantwortet vor 2 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 10 Monaten
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 5 Monaten
I think you have shared for AWS backup service suggestion instead of Data Life Cycle Manager.