Move to cloud.gov in govcloud

[jcscottiii]

• Use RDS instance

[jcscottiii]

cc: @erik-burgess @alain-hoang

[digiphile]

Is open.foia.fov now running on GovCloud?

Have there been any changes it hosting or features since last year?

On Wed, Mar 1, 2017 at 11:53 AM James C Scott III notifications@github.com wrote:

cc: @erik-burgess https://github.com/erik-burgess @alain-hoang https://github.com/alain-hoang

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/18F/foia-hub/pull/838#issuecomment-283399014, or mute the thread https://github.com/notifications/unsubscribe-auth/ACcoN23P218d_bCeOy4rZG3svPZkk5neks5rhaJ-gaJpZM4MP6dj .

-- Alexander B. Howard Deputy Director http://sunlightfoundation.com/author/ahoward/, Sunlight Foundation Phone: 410.849.9808 | @digiphile http://twitter.com/digiphile Social Media: http://j.mp/ContactABH

[jcscottiii]

@digiphile sorry for the confusion. currently it runs on the cloud.gov platform that resides in AWS E/W. that cloud.gov environment is going away. cloud.gov has a new FedRAMP'ed environment in AWS GovCloud. This PR is just some small changes to make so it will work there eventually.

[alain-hoang]

The changes associated with this pull request addresses compatibility modifications to adapt open.foia.gov for the new cloud.gov that has been FedRAMPed. A note for the person(s) who can perform merge (and deploy) these changes include:

• Updated the meta-information in the dependencies on required software libraries to run with versions compatible with open.foia.gov
• Updated the hosts information so that it is compatible with running in the updated cloud.gov environment
• Removed dependency on unnecessary credentials for accessing object storage assets (S3) in AWS
• Updated documentation in README for new FedRAMPED environment
  • Included clarifications for setup, running, and deployment of this application
• Updated the Python runtime to a more compatible version with Cloud Foundry
• Updated location for database to point to new location in new FedRAMPed environment

While the main issue is that the pull request for these modifications is that someone with the necessary permissions can perform the merge, it is also recommended that someone with access should deploy the application post merge. This will help verify that the master branch (post merge) for this project is in sync with application in cloud.gov.