Closed Bug 1456654 Opened 6 years ago Closed 6 years ago

set up stage submitter aws lambda function in prod

Categories

(Socorro :: Infra, task, P2)

Product:
Socorro
Component:
Infra
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: willkg, Assigned: miles)

References

Details

In the previous infrastructure, we had a stage submitter. It ran as a process every couple of minutes kicked off my cron living in a small shack on a deserted island in the AWS account. No one visited. It was alone for months on end. It had a volleyball for a friend.

We've switched to a new infrastructure and decided to switch things up a bit and rewrite the stage submitter as an AWS Lambda function. That's covered in bug #1430937.

The initial code drop has landed. It's time to set that up in prod.

This bug covers setting it up in prod.
Repository for the new stage submitter is here:

https://github.com/mozilla-services/socorro-submitter

In that repo is a README that talks about required env vars. We want these:

SUBMITTER_ENV_NAME=prod
SUBMITTER_THROTTLE=10
SUBMITTER_DESTINATION_URL=https://crash-reports.allizom.org/submit

We need to set these--Miles and Brian will know the values needed:

SUBMITTER_S3_BUCKET
SUBMITTER_S3_REGION_NAME

I don't know if we need to set these or not:

SUBMITTER_S3_ACCESS_KEY
SUBMITTER_S3_SECRET_ACCESS_KEY


Miles: Do you need anything else from me?
Assignee: nobody → miles
Status: NEW → ASSIGNED
Flags: needinfo?(miles)
Priority: -- → P2
Bug #1456956 covered switching the submitter to trigger on processed crashes. That's landed, so we should be good to go on this now.
Depends on: 1456956
Miles set it all up and it's working now! Yippie!
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(miles)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.