1回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
IMHO, you can use EBS notification feature in your case. https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.managing.sns.html
You will receive a notification like example below:
{
"Records": [
{
"EventSource": "aws:sns",
"EventVersion": "1.0",
"EventSubscriptionArn": "arn:aws:sns:us-east-1...ElasticBeanstalkNotifications-Environment-foo-app...",
"Sns": {
"Type": "Notification",
"MessageId": "111",
"TopicArn": "arn:aws:sns:us-east-1...ElasticBeanstalkNotifications-Environment-foo-app",
"Subject": "AWS Elastic Beanstalk Notification - New application version was deployed to running EC2 instances",
"Message": "Timestamp: Thu May 07 23:38:22 UTC 2015\nMessage: Lambda Function Test: New application version was deployed to running EC2 instances.\n\nEnvironment: foo-app\nApplication: FooApp\n\nEnvironment URL: http://foo.com\nRequestId: 222\nNotificationProcessId: 333",
"Timestamp": "2015-05-07T23:39:18.628Z",
"SignatureVersion": "1",
"Signature": "hello-sig",
"SigningCertUrl": "https://sns.us-east-1.amazonaws.com/...",
"UnsubscribeUrl": "https://sns.us-east-1.amazonaws.com/...",
"MessageAttributes": {}
}
}
]
}
You might use the 'Environment' value in 'Message' of this notification to modify grafana's resource in Lambda
回答済み 4年前
関連するコンテンツ
- AWS公式更新しました 1年前