cloud.gov news
For Humans and Agencies: The cloud.gov Deprecation Policy
We want to talk about two crucial aspects of being a cloud provider: consistency and predictability. Consistency is the ability to do something the same way every time, and predictability means that you can count on it happening. When it comes to communicating changes about our platform, we believe we have been neither consistent nor predictable, and we’d like to talk about how we intend to change that.
Changes to cloud.gov services and prices
Cloud.gov’s funding source (the Acquisition Services Fund) requires us to review our expenditures and adjust rates to cover the cost of running the service. Starting on October 1, 2019, new interagency agreements (including renewals) will use the following prices. Agreements already in place will not change, and any modification or amendment to an existing agreement in FY20 will retain the original rate until FY21.
VPN backhaul, Drupal 8 example, and new team members
Curious what’s new that you might find helpful as a cloud.gov user? Here are highlights from our recent changes.
Final warning: cflinuxfs2 will be removed May 21st
Background: We announced on February 26 that cloud.gov would remove support for the cflinuxfs2 stack (the operating system image for applications). This was the default stack for cloud.gov applications deployed before April 15. On April 15 we set the default stack for new applications to cflinuxfs3.
Quarterly update - An OS upgrade, cross-IaaS services, R Shiny apps, and more!
An OS upgrade, cross-IaaS services, R Shiny apps, and more!
Release notes
Here’s the latest on how we’ve been trying to make cloud.gov simpler and more secure. (If you find yourself needing to explain cloud.gov to coworkers or leadership, take a look at our new two-pager!)
New S3 plan for sandboxes
In the past, we’ve had issues with users being notified of a sandbox purge even though the sandbox didn’t actually get cleared. So in order to provide a more seamless experience, cloud.gov now offers S3 service plans for sandboxes that automatically clear your S3 contents whenever your sandbox is cleared.
New custom domain service
For custom domain support, cloud.gov provides a CDN service that uses AWS CloudFront. AWS CloudFront is outside the AWS FedRAMP P-ATO boundary, so we’ve updated the CDN service documentation to explain the compliance impact of using this service more clearly.