cloud.gov news

Certain versions of NGINX will be removed in upcoming releases of the Cloud Foundry Staticfile and NGINX buildpacks.

Certain versions of the Node.js runtime will be removed in upcoming releases of the Cloud Foundry Node.js buildpack.

With so many ways to organize and prioritize work - scrum, Kanban, SAFE - it can be helpful to learn about a team’s experience with using different practices and processes. In the spirit of sharing knowledge and translating theory into practice, we’ll use this blog post to explain how cloud.gov manages its work and what we’ve learned along the way.

This is a repost of our StatusPage notice, originally posted August 7th, 2020

Join us on March 17 for a tech talk to learn more about internal routes on cloud.gov. Our engineers will show you how to use internal routes for secure, direct, container-to-container communication between applications.

We share a sample “System Environment” SSP response for a Low-impact system

The cloud.gov platform acts as a concierge for your cloud deployments, removing a lot of the hard work of setting up a scalable and compliant infrastructure, and streamlining the ATO process.

With an update to our compliancy policy, we will begin notifying and deactivating inactive accounts that use our cloud.gov IDP for authentication. Our customers that use their agencies’ credentials to authenticate into our platform will not be affected. Users that do not log into the platform within the past 90 days will be deactivated. We will send you email notifications 10 days and 1 day before deactivation instructing you to log into the platform to reset the 90 day threshold. If you are unable to log into the platform within the allotted time, you will need to email support@cloud.gov to have your account reactivated.