2. FEC system diagram
Notes:
- 3 RDS instances with assess 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 que and start nightly refresh
- Redis swarm is needed to store download que
- API needs access to api.data.gov, which is whitelisted from production (Prod only)
- Mandrill API access for email error messages from the update processes
- Slack access for the apps to post what branch is deployed where (currently disabled)
- The Proxy app needs access to DNS and to route traffic for beta.fec.gov, which consists of the Web app and CMS
- The Web app and CMS need access to GitHub to post user feedback
- The CMS uses a postgres database in cloud.gov
- Testing and deploys from Travis on successful builds
- Error monitoring: NewRelic, Sentry
- FEC legal resources is working on adding an elasticsearch instance for legal documents
###All FEC repositories:
- FEC: a general discussion forum. We compile feedback from betaFEC's feedback widget here, and this is the best place to submit general feedback.
- openFEC: betaFEC's API
- swagger-ui: forked repo that generates our interactive API documentation
- openFEC-web-app: the web app for exploring campaign finance data
- fec-style: shared styles and user interface components, including this project's glossary and feedback tools
- fec-cms: this project's content management system (CMS)
- fec-eregs: the eRegulations viewer for betaFEC
- fec-proxy: this is a lightweight app that coordinates the paths between the web app and CMS