publicdata/j40-cejst-2
1
0
Fork 0
mirror of https://github.com/DOI-DO/j40-cejst-2.git synced 2025-02-22 01:31:25 -08:00
Code Issues Projects Releases Packages Wiki Activity Actions

updated readme with aws links

Browse source
This commit is contained in:
Gina Maini 2021-07-16 09:56:23 -04:00
parent 9782d54dfc
commit fc8830b12a
1 changed files with 21 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
infrastructure/README.md
View file

@ -30,6 +30,27 @@ You'll have to grab the arn of the certificate from the log output or go into th
`./node_modules/.bin/serverless deploy --aws-profile <<your profile name from ~/.aws/credentials>> --stage stg --verbose`
## View Our Resources in AWS Console
Sign in and checkout:
https://console.aws.amazon.com/lambda/home?region=us-east-1#/applications/j40-stg-justice40-data-harvester?tab=deploy
to see our Cloudformation template deploys as lambdas. You should see the `j40-stg-justice40-data-harvester` deploy events there.
To see our functions in the lambda, check out:
https://console.aws.amazon.com/lambda/home?region=us-east-1#/functions/
Right now we just have:
`stg-DetectChangesForWorker` which has no triggers and just immediately runs when you deploy. Additional work needs to be done to have it run on a cron. That code exists and is currently commented out.
To view the buckets it writes to in `stg` go to:
https://s3.console.aws.amazon.com/s3/home?region=us-east-1&region=us-east-1
Currently the logging is not setup to write to an internal S3.
# Warning! This section on is currently unimplemented, partially incorrect, and untested.
## Testing