Government Cloud Computing: A Current Bibliography

I gave a webinar today called, “Beyond Fairy Dust & The No Police: How Cloud Computing Makes Government Better“.  Below is the “virtual handout” for the webinar, which lists recent activity both in the government cloud world as well as the platform-as-a-service world.  A recording is archived here.

Enjoy!

Suggested Gov Cloud Reading

Extreme Heroku: A Polyglot PaaS Civic Application!

Amazon Cloud Gets Federal Stamp Of Approval

FedRAMP – Federal Risk and Authorization Management Program

Amazon Web Services, Douglas County, NE case study.

2014 Federal Government IT Priorities (including cloud computing plans).

Feds Use Cloud to Clean Up Nuclear Site.

Docker – PaaS for IaaS OpenStack

Docker OpenStack Summit Presentation & Demo

Code for America “read me” example from code built for PaaS hosting: ShortStack app

Farmers Feed Us, an app built during National Day of Civic Hacking, hosted on PogoApp, a PaaS provider

Migrating from one PaaS to another (Heroku and Ruby to RedHat’s OpenShift)

Dokku, the smallest PaaS

Notable Code For America Government Apps Running on PaaS:

Adopt a Hydrant – Boston, MA

Honolulu Answers – Honolulu, HI

Blight Status – New Orleans, LA

###

FedRAMP-cloud-computing

Comments

  1. says

    I understand everything that was said, but the real issues with cloud computing (at least SaaS) were ignored:
    1) Vendors need published APIs and webservices that enable integration with other systems and most importantly with the IM systems (e.g. Active Directory) of government organizations.
    2) They need to develop clear ownership and exit strategies that protect the data that’s stored in the cloud. That usually means having a complete schema/data dictionary of the system database and regular premise backups that can be used as a test.
    3) The procurement model of government requires that certain dollar volume thresholds be acquired through competitive procurement. The “30 day free trial” and “you can leave any time you’re not satisfied” argument is not applicable. Likewise, we need to have access to the financial viability metrics of the company, most of which resist such disclosure.

    • says

      Hi Dennis. I hear what you’re saying; it’s all about use case. Let me suggest that what I said about not everything being an appropriate use case for SaaS probably applies to the majority of your comments. If you can live without schema, if you can live without AD integration, it may be a use case. Note that the business unit, not IT, should really be making the decision in this matter: IT should be there to translate and explain the risks and benefits. Thanks!

Trackbacks

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>