2. FEC system diagram
Notes:
- AWS RDS Aurora instances with access the internet so the FEC can push updates. Devs need access to Amazon so that they can scale up the instances in times of heavy traffic, like filing deadlines and schema updates. The team also responds to alerts as necessary. These are not hosted on cloud.gov
- The API needs S3 access on cloud.gov to the fec bucket to create downloadable csv resources. Those resources expire daily.
- Celery worker to create and maintain download queue and start nightly refresh
- Redis service is needed to store download queue
- API needs access to api.data.gov, which is whitelisted from production (Prod and Stage only)
- Slack access for the apps to post what branch is deployed where, and error messages from the update processes
- The Proxy app needs access to DNS and to route traffic for beta.fec.gov and transition.fec.gov
- The CMS needs access to GitHub to post user feedback
- The CMS needs access to the eCFR API to for searching regulations
- The CMS uses a postgres database in cloud.gov
- Testing and deploys from Circle on successful builds
- Uptime and error monitoring: Pingdom
- FEC legal resources is using an elasticsearch instance for legal documents