As previously announced, we will be officially deprecating all support for GCP Billing CSVs on July 30, 2021. This includes the Cost History, Compute Engine, and Billing Statements Reports. On this date, we will stop collecting costs from Billing CSVs and will solely rely on the BigQuery Billing Exports. Although, these reports will not have any data updates after July 30th, they will continue to be available in the navigation for some time. If you have not done so, please update your configuration in CloudHealth to use the BigQuery Billing Export as outlined in this Help Center article.
We have released a new Y-axis option on the Azure Amortized Cost and Cost History Reports to give visibility into the utilization of your monthly payment reservations. Especially important for shared scope reservations, you can categorize by subscription when viewing this axis, to see which subscriptions received the benefit of the utilized reservations so that you can chargeback for that usage. Please note, this axis reports on the usage of those reservations so costs for unused reservations will not be captured here.
We have released the next phase of support for reservations for all services in Azure. Using the Asset Type Reservations V2, you can now allocate these in Perspectives and the costs for those upfront purchases will follow.
We now have three new templates for GCP BigQuery Billing Export and AWS Cost & Usage Report datasets.
Monthly Cost by GCP Services
Monthly Savings for AWS Elasticsearch Service RIs
Monthly Usage and Cost Details for SQS
We have also added support for two more SQL functions in FlexReports, DATE and FROM_ISO8601_TIMESTAMP. You can find the complete list of supported functions and examples in this Help Center article.
We will be adding the following policy conditions in the coming week to the default security policy to fully align with CIS 1.3. This will be the final update to align with the latest CIS release.
4.3.1 Ensure 'Enforce SSL connection' is set to 'ENABLED' for PostgreSQL Database Server
4.3.3 Ensure server parameter 'log_checkpoints' is set to 'ON' for PostgreSQL Database Server
4.3.4 Ensure server parameter 'log_connections' is set to 'ON' for PostgreSQL Database Server
4.3.5 Ensure server parameter 'log_disconnections' is set to 'ON' for PostgreSQL Database Server
4.3.6 Ensure server parameter 'connection_throttling' is set to 'ON' for PostgreSQL Database Server
4.3.7 Ensure server parameter 'log_retention_days' is greater than 3 days for PostgreSQL Database Server
6.6 Ensure that UDP Services are restricted from the Internet
5.2.2 Ensure that Activity Log Alert exists for Delete Policy Assignment