Switch to using Cloud.gov-brokered SES service

[neilmb]

User Story

In order to save money and complexity, Data.gov devs want to use an AWS SES server that is not provided by a service broker that we maintain.

Acceptance Criteria

• GIVEN Cloud.gov has opened a private beta for brokered SES
  WHEN our services send an email
  THEN it goes out through an email server that is not provided by our own service broker

Background

We need to investigate to see if this applies to just H2.0 or CKAN or both at the same time.

Security Considerations (required)

This is a substantial improvement if we can turn off the SES broker that we are currently maintaining.

Sketch

We can start in dev by creating service instances using the new Cloud.gov-provided plan, binding them to our services, restarting our services and testing to see if they work. We can then extend that to staging and production, and changing the infrastructure provisioning scripts that we run on every deploy.

[tdlowden]

@neilmb what's a ballpark LOE on this?

[neilmb]

I'm going to switch staging tomorrow morning and if it goes smoothly, I'll do prod.