payments-dashboard/package.json
Adam Moussa 90accf2f39 Migrate secrets from SSM to Secrets Manager
API tokens and credentials must live in Secrets Manager per
secrets-and-config.md, but the four original payment Lambdas still
read 10 SecureString SSM params. Move them to three grouped secrets
(slack-bot-token plaintext, boa-check-mgmt and boa-reporting as JSON),
matching the pattern the expense Lambdas already use. IAM is scoped to
secretsmanager:GetSecretValue per secret; the VPC Lambdas reach the
public endpoint over the existing NAT path. Test/reissue scripts and
the client-ssm dependency are updated/removed accordingly.

Refs: #3
2026-06-02 20:29:18 -04:00

19 lines
545 B
JSON

{
"name": "payments-dashboard",
"version": "1.0.0",
"type": "module",
"description": "Payments CSV ingestion, Slack App Home dashboard, and expense approval routing",
"files": [
"src/"
],
"dependencies": {
"@aws-sdk/client-dynamodb": "^3.1059.0",
"@aws-sdk/client-lambda": "^3.1059.0",
"@aws-sdk/client-s3": "^3.1059.0",
"@aws-sdk/client-secrets-manager": "^3.1059.0",
"@aws-sdk/client-sqs": "^3.1059.0",
"@aws-sdk/lib-dynamodb": "^3.1059.0",
"csv-parse": "^6.2.1",
"mailparser": "^3.9.9"
}
}