An issue today uncovered the fact that we are using the incorrect IAM user for connecting to S3 on processor nodes. We will update to use the existing prod/stage processor users for each respective env.
2 years ago
Assignee: jschneider → miles
This is going to become irrelevant when we move to the new deployment model.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.