cloud.gov news

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.

We have put together a new video tutorial to focus on new features of the cf7 CLI. This tutorial will get you familiar with the new “rolling” app deployment strategy available for zero downtime deployments. With these new features available in the cf7 cli, the rolling, zero-downtime deployment option is the most anticipated feature and could improve your workflows the most. The older versions of cli did not provide zero downtime deployments natively which meant needing to use a third party plugin or complicated blue/green deployment pipeline to accommodate your needs.

On December 13, 2020, the DHS Cybersecurity and Infrastructure Security Agency (CISA) published Emergency Directive 21-01, “Mitigate SolarWinds Orion Code Compromise”.

As part of our reliability and stability enhancements to cloud.gov, the legacy Redis 3.2 and Elasticsearch 5.6 offerings from cloud.gov will be deprecated as of April 5, 2021. In accordance with our deprecation policy, provisioning of new instances will be disabled on December 6, 2020 and on April 5, 2021 we will shut down all active instances. This work is an important step in moving cloud.gov towards a more stable and reliable platform by moving away from a bespoke Kubernetes cluster to AWS-hosted services. Learn more about our deprecation policy here:https://cloud.gov/docs/technology/responsibilities/#deprecation-policy

Learn more about how you can run .NET apps on the cloud.gov platform and get answers to commonly asked questions about .NET development and deployment for cloud.gov