Closed
Bug 1212341
Opened 10 years ago
Closed 10 years ago
Add S3 event source for net-mozaws-prod-us-west-2-pipeline-data to telemetry_index_ping lambda function
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rvitillo, Unassigned)
Details
Please add a S3 event source for net-mozaws-prod-us-west-2-pipeline-data (event type: PUT) to the telemetry_index_ping lambda function (old dev).
After updating the lambda function, the event source disappeared. I tried to add it back manually but I couldn't find net-mozaws-prod-us-west-2-pipeline-data in the list of available sources.
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(whd)
Comment 1•10 years ago
|
||
Found the command I used last time in my history. The GUI doesn't let you use buckets from other IAMs.
aws --profile=stage --region=us-west-2 lambda add-permission --cli-input-json "$(cat lambda/newcli.json)"
$ cat lambda/newcli.json
{
"FunctionName": "arn:aws:lambda:us-west-2:142069644989:function:telemetry_index_ping",
"StatementId": "net-mozaws-prod-us-west-2-pipeline-data",
"Action": "lambda:InvokeFunction",
"Principal": "s3.amazonaws.com",
"SourceAccount": "361527076523",
"SourceArn": "arn:aws:s3:::net-mozaws-prod-us-west-2-pipeline-data"
}
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(whd)
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•