Release Notes


NOTE: If you see any odd behavior or anything missing after a release, you should try a force refresh of your browser after logging-in to the console and/or on any screens that appear to be having issues.  On Windows, this is typically done with Ctrl-F5, and on the Mac: CMD+SHIFT+R. 

Version 8.16.2 - Released 2020-12-28

New/changed features

  • Azure SQL Database Soft Parking - ParkMyCloud now provides the ability to "soft park" Azure SQL databases that are in the vCores and DTU pricing models. These databases are not stoppable in Azure, so we provide functionality to throttle them to a more cost efficient state using the same ParkMyCloud scheduling that you leverage for your other workload types. Please see the feature documentation at Discovery and Soft Parking Azure SQL Databases. 
  • Azure Synapse Analytics Parking - ParkMyCloud now provides the ability to park Azure Synapse Analytics (Data Warehouse) databases, using the same ParkMyCloud scheduling that you leverage for your other workload types. This pauses the workload in Azure, resulting in great cost savings.

Version 8.15.1 - Released 2020-12-07

Fixes

  • Reporting timeouts  - We have increased the timeout limits for our reports pages. This will allow larger clients to run longer reports without experiencing the 504 timeouts. A new, asynchronous workflow is forthcoming. 

Version 8.15.0 - Released 2020-11-07

Fixes

  • Resources Page Performance  - The main resources page has undergone several performance related enhancements. This will result in dramatically faster load and filtering times for large clients.

Version 8.14.1 - Released 2020-10-07

Fixes

  • Policy Rules “Test Criteria” - In the Policies section of the UI, when adding or editing a specific policy rule, the Test Criteria button would previously time-out with a gateway error if you have more than 2000 resources in the platform, and less than 100 of them match the rule. 

Version 8.14.0 - Released 2020-09-24

New/changed features

  • Azure SQL Database Metrics - ParkMyCloud will now ingest a subset of Azure DB metrics. These are visible as heatmaps and utilization visualizations for the respective databases.  

Fixes

  • Reports – Now properly deleted when a user is archived.
  • Styling - Various styling fixes to the console and reports.

Known issues

  • Policy Rules “Test Criteria” - In the Policies section of the UI, when adding or editing a specific policy rule, the Test Criteria button may time-out with a gateway error if you have more than 2000 resources in the platform, and less than 100 of them match the rule. (Yes, this one has been around a while...we are trying to fix it soon as part of an overall performance improvement.)

Version 8.13.0 - Released 2020-09-08

New/changed features

  • Azure SQL Databases - ParkMyCloud can now ingest and display the following Azure SQL database types, and their respective prices. Please find the updated Azure recommended policy here. Once the requisite permissions are added to your policy, ParkMyCloud will discover and display these resources within a few minutes. We will provide parking & scheduling features in an upcoming release.

Fixes

  • User Time Settings – There was an issue with user specified 24 hour time settings

Known issues

  • Policy Rules “Test Criteria” - In the Policies section of the UI, when adding or editing a specific policy rule, the Test Criteria button may time-out with a gateway error if you have more than 2000 resources in the platform, and less than 100 of them match the rule. (Yes, this one has been around a while...we are trying to fix it soon as part of an overall performance improvement.)

Version 8.11.0 - Released 2020-08-21

New/changed features

  • Login – Customers can now choose what screen they will view when logging in to ParkMyCloud.  To use this feature, navigate to the My Profile-->Display Settings screen and select the desired page on the Screen to show at login pulldown.

Known issues

  • Policy Rules “Test Criteria” - In the Policies section of the UI, when adding or editing a specific policy rule, the Test Criteria button may time-out with a gateway error if you have more than 2000 resources in the platform, and less than 100 of them match the rule. (Yes, this one has been around a while...we are trying to fix it soon as part of an overall performance improvement.)

Version 8.10.0 - Released 2020-08-07

New/changed features

  • Main Resources screen
    • Performance improvement – The main resources screen now loads in half the time it had been loading. We are going to continue to work on the main resources screen, with the goal of getting load time under a second, regardless of the number of resources in your environment.
    • Copy/Paste – By customer request, we have simplified copying text from the main resources screen.  Formerly, the screen would jump to the resource details on click or mouse-up, frustrating anyone that wanted to copy a resource name or other text. The screen now only jumps to the resource details on mouse click.
  • Single Sign-On (SSO) – SSO now supports Service Provider (SP) Request Signing.  This improves the mutual authentication between your SSO Identity Provider (IDP) and ParkMyCloud, prior to a user being granted access to ParkMyCloud. To enable SP Request Signing, go to the PMC Single Sign-On configuration screen, and click SP Request Signing: Enabled. You will then be given the PMC authentication certificate which you then configure in your IDP.

Fixes

  • AWS RDS Database Utilization Data – There were issues with PMC collection of AWS RDS metrics data from CloudWatch, resulting in gaps in the data, and impairing both SmartParking and rightsizing recommendations.  The issue has been fixed, and we reloaded all RDS metrics going back to June.  All recommendations should now be correct.
  • Azure EA Pricing – There were some issues with Azure EA pricing data for some customers. 
  • SmartParking Recommendations – The SmartParking Recommendations list was not sorting by savings correctly when the list contained AutoScale Groups.
  • Rightsizing – We will no longer show rightsizing recommendations for AWS Spot instances. Also, we have blocked-off cross-family rightsizing recommendations for GCP n1 instances that are using GPUs/accelerators.

Version 8.9.0 - Released 2020-07-17

New/changed features

  • AWS Spot Instances - We now allow scheduling of AWS Persistent Spot instances.  You can now get double-savings on your workloads by both using persistent Spot and shutting them off when not in use!  By way of reminder:
    • A one-time Spot Instance request remains active until Amazon EC2 launches the Spot Instance, the request expires, or you cancel the request. AWS does not allow one-time Spot instances to be "stopped."
    • A persistent Spot Instance request remains active until it expires or you cancel it, even if the request is fulfilled.  AWS does allow persistent Spot to be stopped and started on demand.  See here for more details.
  • Rightsizing
    • We now support Rightsizing Recommendations for Google CloudSQL databases. Any new recommendations should appear within 24 hours.
    • The Manual rightsizing screens (found by clicking any resource on the main resources screen and going to the Rightsize tab) now includes details of how to install the memory utilization data collection agent particular to that resource type.  Also, we now provide some additional details if a resource does not have any eligible rightsize candidates.
  • Azure Resource Groups - For your convenience, the names of Azure Resource Groups are now prepended to all resource lists in the console.
  • Scheduling - The various weekly schedule displays now have a color key to indicate what the colors indicate. Also, the SmartParking Recommendation list will now show the percentage of potential savings.

Fixes

  • AWS RDS Rightsizing - Fix an issue where some resources did not show rightsizing candidates in their own instance family.
  • Google Cloud Pricing - Fixed a minor pricing issue with Windows instances.
  • SmartParking - Fixed an issue where some unparkable resources were still getting SmartParking recommendations. Also fixed a calculation issue with projected savings from SmartParking recommendations.
  • Reports - Removed deep links from Daily Summary Report if the customer account is enabled for SSO. If the user was not logged-in, the deep links led the user by default to the "normal" login screen instead of the SSO login screen.

Version 8.8.0 - Released 2020-07-10

New/changed features

  • Google Cloud Platform (GCP) CloudSQL Database Rightsizing - ParkMyCloud now supports manual rightsizing of CloudSQL databases. To simplify the overall resizing experience, this includes automatic enforcement of the various permitted vCPU vs memory vs. DB engine combinations, and allows custom instance types where supported.  To resize a GCP CloudSQL database, navigate to the instance on the main ParkMyCloud Resources screen, click the row to open the Resource Details, and then select the Rightsize tab.
  • GCP Memory Metrics - ParkMyCloud can now collect GCP compute instance metrics that are recorded using the Cloud Monitoring agent, also known as the stackdriver agent.  These metrics include memory utilization which can significantly improve the quality of ParkMyCloud rightsizing recommendations.  See the GCP Monitoring Agent installation instructions. Note that in addition to installing the agent, you will need to enable the Cloud Monitoring API for your project – log in to your GCP project and go to the Monitoring API page.
  • GCP Compute Extended Memory Rightsizing - GCP rightsizing for custom instance types has been enhanced to also support custom instance types with extended memory, including both manual rightsizing, and the semi-automatic Rightsizing Recommendations.

Fixes

  • AWS Compute Rightsizing - Fixed an issue where Graviton (ARM)-based instances could get Intel-based rightsizing options, and vice versa. Also fixed an issue where AWS metadata inconsistencies caused some instances to not get rightsizing options within the same instance family.
  • Console - Fixed team and cred filters on rightsizing screen that caused a UI error.

Version 8.7.0 - Released 2020-06-27

New/changed features

  • Azure Storage – The system will now import Azure disks and snapshots associated with compute instances.  Navigate to a compute instance in the main Resources screen, and click on the row to open the resource details screen.  Navigate to the Storage tab. (Note that it may take up to 24 hours for all storage to appear in PMC)
  • Recommendations - We have also added the ability to re-run SmartParking and Rightsizing calculations on demand.  Before, you could only manually invoke new recommendations by changing the recommendation configuration.  To force recalculation, navigate to the appropriate Recommendations screen and select Options→Update Recommendations.

Fixes

  • Fixed an issue with pricing for Google Cloud pricing on custom-extended instances.
  • Fix an issue with loading Azure cloud resources for customers with > 10K compute resources in a single subscription.

Version 8.6.0 - Released 2020-06-21

New/changed features

  • SmartParking:
    • Google Cloud Platform (GCP) Databases: The system now collects metrics for GCP CloudSQL databases and will present SmartParking schedule recommendations if idle time is detected.  Note that it will be about a week before we have gathered enough metrics for recommendations.
    • Scale groups: We now support SmartParking schedule recommendations for Scale Groups, and Scalesets, Managed Instance Groups (collectively labelled within PMC as Autoscale Groups, or ASGs).  The system is coalescing the metrics data for all instances assigned to an ASG during the configured evaluation window to see if the ASG as a whole should be scheduled to be shut down. Note that we do not collect metrics for instances that are only active for less than a day, so highly volatile ASGs are not likely to get a recommendation (though, in all likelihood, a volatile ASG is very busy.) 

Fixed issues

  • Notifications: Added filtering to reduce the number of transient credential error notifications.
  • GCP Pricing: Corrected pricing for GCP custom-extended instances.
  • Alibaba: Fixed an issue with displaying compute instance details for Alibaba Cloud.

Version 8.5.0 - Released 2020-06-05

New/changed features

  • Rightsizing – The Rightsizing Recommendation screen has been updated with a number of enhancements:
    • We now can provide rightsizing recommendations for individual AWS Database Cluster members.  This applies to regular RDS, Aurora, and other AWS databases shown in ParkMyCloud that use the RDS APIs.  Note that if your cluster has multiple members intended to provide high availability, you should not schedule all of the members to be resized at the same time...
    • We can now also provide rightsizing recommendations for database and compute members of ParkMyCloud Logical Groups.
    • The Rightsizing Recommendation list has been enhanced to provide a better presentation of the potential savings for each recommendation, and a measure of the recommendation quality, based on the type and quantity of metrics that are available. 
    • The downloadable recommendation report has been enhanced to include the full level of detail needed to decide the best recommendation to execute. This report can be downloaded from Rightsizing > Recommendations > Options > Download CSV.
  • Reports – Added two new reports to show Savings Summary by Team and Savings Summary by Credential.  These reports are very similar to the longstanding Cost/Savings Summary by x reports...but without the cost data.

Version 8.3.0 - Released 2020-05-19

New/changed features

  • AWS RedShift – ParkMyCloud now supports discovery and scheduling of AWS Redshift clusters. 
    • We can also generate SmartParking recommendations for Redshift – to view or edit Redshift “idle” thresholds, navigate to Scheduling > SmartParking Recommendations > Options > Settings.  Select the team for you which want to edit settings, Cloud Provider: AWS and Resource Type: Databases.  Note that most of the settings apply to RDS, settings that are specific to Aurora or Redshift are specifically identified in the Metric Name.
    • An IAM Policy update is required to see and schedule Redshift. See the Recommended Policy link on the ParkMyCloud AWS credential edit screen, or download the latest policy from our github.  This most recent policy change also includes an update to allow access to Elastic Container Service (ECS), which we will be adding over the next couple months.

Fixed items

  • Audit log for resize actions now includes the item name instead of an internal ID.
  • Improved performance and display of listed schedules.
  • Fixed an issue sending excessive “discovery failed” notifications for customer AWS regions that are disabled.

Version 8.2.0 - Released 2020-05-09

New/changed features

  • Google Kubernetes Engine (GKE) – Completing our Kubernetes management suite, ParkMyCloud now supports scheduling of GKE Clusters and Nodepools.
    • An GCP IAM policy update is required to allow ParkMyCloud to access your GKE details. See the Recommended Policy link on the ParkMyCloud GCP credential edit screen, or download the latest policy from our github. Follow the instructions in the ParkMyCloud User Guide.
  • New AWS Milan and Cape Town Regions – We now support all ParkMyCloud functions for these two new AWS regions.
  • Schedules – The main Scheduling screen (Scheduling > Schedules) has been enhanced to show how many workloads are attached to the schedule, the schedule time zone, and the last time the schedule was updated.
  • Disable Credential – You can now manually disable a cloud credential, allowing you to temporarily turn-off discovery and scheduling of workloads under the credential, without having to completely delete the credential.  To disable a credential, navigate to the Cloud Credentials screen, click the credential to Edit it, and then select the Disable button.
    • Note that ParkMyCloud will automatically disable any credential that has not had a successful discovery in any region for more than seven days in a row.  If you subscribe to Notifications for Credential Errors, you will be sent a notification.
    • You can re-enable a credential that has been manually or automatically disabled by clicking the credential to Edit it, and then select the Test button.  If the credential passes the test successfully, you will be given the option to re-enable it.
    • The Cloud Credentials screen has been updated to show the credential enabled/disabled state.
  • SmartParking – SmartParking recommendations can now be disabled on a team-by-team basis.  The setting can be found both under the team details under the Teams menu, and under the Scheduling > SmartParking Recommendations > Options > Settings menu.

Fixed items

  • Fixed an issue with Discovery of Managed Instance Groups for Google Cloud (shown as Scale Groups in ParkMyCloud). In some cases, managed instance groups could not be Discovered for a period of time, and any associated schedules, team assignments, scaling configuration, or Logical Group assignment could have been lost.  All customers should double-check to make sure all GCP managed instance group settings are configured as desired.

Version 8.1.0 - Released 2020-04-17

New/changed features

  • Azure Kubernetes Service (AKS): As a follow-on to our AWS EKS release a couple weeks ago, we now support AKS Cluster and Nodepool scheduling.  Assuming you have applied the Azure Policy update discussed below, you will see our new icon for Nodepools:  and when you click the Nodepool for more details, you will see the Nodepool and AKS Cluster details. Some notes:
    • To manage the size of the nodepool, go to the Nodepool details in ParkMyCloud and adjust the number of members on the Settings tab. Azure manages AKS nodepools internally as Scale Groups, and so the settings are very similar. We strongly recommend that if you plan to shut the nodepool down, shut it all the way down to zero active nodes.
    • To manage an entire AKS Cluster, consisting of multiple Nodepools, assign the different Nodepools to a ParkMyCloud Logical Group.
    • An Azure Access Policy update is required to allow ParkMyCloud to access your AKS details. See the Recommended Policy link on the ParkMyCloud AWS credential edit screen, or download the latest policy from our github. Follow the instructions in the ParkMyCloud User Guide to update your policy using the Azure CLI or Windows PowerShell.
  • Rightsizing: The system now fully supports gathering memory metrics for the platforms listed below, allowing for significantly improved rightsizing recommendations.  Before this release we had support for gathering memory metrics for Linux systems on AWS only, and workloads without memory metrics only received rightsizing recommendations that downsized the CPU resources.  Note that due to limitations on Windows servers, both the AWS and Azure agents pull the % Committed Bytes In Use counter, as opposed to the more specific “Percent Memory Used” metrics available from Linux.  The site linked here has an excellent overview of how the Windows metric can be used to evaluate memory utilization.
    • AWS EC2 Windows Memory metrics using the AWS CloudWatch Agent for Windows
    • AWS EC2 Linux Memory metrics using the latest AWS CloudWatch Agent for Linux
    • AWS EC2 Linux Memory metrics using the older AWS CloudWatch monitoring scripts for Linux
    • Azure Compute Windows Memory metrics using the Azure Monitor Agent for Windows
    • Azure Compute Linux Memory metrics using the Azure Monitor Agent for Linux
    • All of the metrics above and several other new metrics are also available for SmartParking recommendation settings - Navigate to Scheduling>SmartParking Recommendations, and select Options>Settings.
    • You can also view the actual data graphed on the Utilization tab under the workload details screen (click on a specific workload on the main Resources screen).
    • Note that we are forcing rediscovery of all metrics in the system for the last two weeks of data to ensure your system have all available metrics. It may be 24 hours before all of your metrics are updated.

Fixed items

  • Updated rightsizing not use certain instance types with certain AWS RDS databases and engine versions per this guidance.
  • Improved the UX by replacing all console actions that appeared as just a plain hyperlink with actual buttons. We are also hiding tabs on the main resources screen for cloud providers that you are not using.
  • Fixed an issue with deleting a team when there are no active users.

Version 8.0.0 - Released 2020-03-27

New/changed features

  • AWS Elastic Kubernetes Service (EKS): We now support EKS Cluster and Nodegroup scheduling.  Assuming you have applied the IAM Policy update discussed below, you will see our new icon for Nodegroups:  and when you click the Nodegroup for more details, you will see the Nodegroup and EKS Cluster details. Some notes:
    • EKS Nodegroups are managed essentially as Autoscale Groups.  On the Settings screen of the Nodegroup details, you can scale up and down the number of nodes in the group. We strongly recommend that if you plan to shut the nodegroup down, shut it all the way down to zero active nodes.
    • To manage an entire EKS Cluster, consisting of multiple Nodegroups, assign the different Nodegroups to a ParkMyCloud Logical Group.
    • As mentioned in the last release, an IAM Policy update is required to see EKS details. See the Recommended Policy link on the ParkMyCloud AWS credential edit screen, or download the latest policy from our github.  This most recent policy change also includes an update to allow access to Elastic Container Service (ECS), which we will be adding over the next couple months.
  • User interface: As you have likely noticed already, the main Resources screen has been changed to have quick-filtering tabs instead of the older filters in the upper left. This should help make it easier to locate the workloads you are seeking. The new EKS workloads are under the Containers tab.  The Filter control has maintained its previous function, and will apply to whichever tab you are viewing. We have also cleaned up our other tabbed screens, making the tabs easier to see.
  • Rightsizing:
    • Rightsizing Savings: We have fixed an issue with accounting for Savings from accepting rightsizing recommendations, and also given customers the flexibility to configure how long you can take credit for these savings.  To configure the rightsizing savings time window, SuperAdmin users can navigate to the Organization Settings menu in the upper right of the Console (click your name), and select the Rightsizing Savings tab.  Note that this only configures savings for accepted recommendations – it will not account for manually-applied resizing actions.
    • Windows Memory Metrics: In our AWS GovCloud environment, added support for the AWS CloudWatch Agent for Windows. This adds support for memory metrics for Windows, allowing for improved rightsizing recommendations. This fix will be coming to the main ParkMyCloud deployment within the next week.

Fixed items

  • Cleaned up layout for some screens that were difficult to read on a narrow window.
  • Fixed the AWS EKS Cluster label when performing AWS Credential Test.

Version 7.19.0 - Released 2020-03-05

New/changed features

  • AWS Savings Plans: We now have the ability to display your purchased AWS Savings Plans.  Navigate to Reports > Reserved Instances > AWS Savings Plans. In a future release we will be taking the Savings Plans and Reserved Instances into consideration when generating our various recommendations.  Note that if you created your AWS Credential before January 9, 2020, you will need to update the AWS IAM Security Policy on your credentials in order to allow ParkMyCloud access to your savings plans.  See the Recommended Policy link on the AWS credential edit screen, or download the latest policy from our github.  Savings Plan information is discovered every 24 hours.
  • AWS Neptune Database Clusters: Neptune database clusters can now be stopped and started, allowing you to schedule them for operations only when you need them.
  • AWS Elastic Kubernetes Service (EKS): We are now collecting EKS cluster and nodegroup data, with the plan to support full EKS scheduling in about two weeks.  As with Savings Plans, an IAM Policy update is required. See the Recommended Policy link on the AWS credential edit screen, or download the latest policy from our github.  This most recent policy change also includes an update to allow access to Elastic Container Service (ECS), which we will be adding over the next couple months.

Fixed items

  • Cleaned up a couple UI elements, like adding spaces between tabs.
  • Clicking the “Force Discover” refresh button in the upper right was opening an empty page.
  • Fixed access to the Organization Settings page for users with the Purchasing role.
  • Fixed a race condition issue with creating Logical Groups (LG) where sometimes the LG and all of its assigned resources would get shut off immediately after creation...even if that was not the desired state.
  • The Azure credential expiration indicator would sometimes show expired when it was not supposed to.
  • Reports Dashboard sub-report titles did not show up when reports first opened.
  • Memory metrics for older versions of the AWS CloudWatch agent are now supported in addition to those from the latest agent version.

Version 7.18.0 - Released 2020-02-19

New/changed features

  • AWS EBS Volumes and EC2 Snapshots: AWS instance details now include a single-page view of all volumes and snapshots associated with the specific EC2 instance - a view not available in the AWS console.  To see this data, click on the row of an AWS instance on the main Resources screen, or on the “>” at the right-end of the row, and then navigate to the new Storage tab.  We will soon be helping you identify unattached EBS Volumes, old and/or excessive snapshots, all of which add to your cloud costs.  Volumes and Snapshots update nightly.  Other clouds and resource types will be coming soon!
  • Filters: Any filters set on the main Resources screen are cleared when the user logs-in.

Fixed items

  • Credential error notifications: Eliminated some noisy notifications related to disabled regions and/or cloud features.
  • Reports: Fixed sorting of dates in some reports that were sorting by month-day-year instead of year-month-day. Fixed an issue with the Dashboard report where it was using the previous selected date range instead of the current selected date range.
  • Logical Groups: Fixed a problem where a newly created logical group would sometimes (though rarely) be turned off immediately after creation, when it was supposed to be turned on.

Known Issues

  • Sorting the Rightsizing and SmartParking recommendations by maximum savings value is not working correctly for resources that have both a Rightsizing recommendation and a SmartParking recommendation. This will be fixed soon...

Version 7.17.0 - Released 2020-02-08

New/changed features

  • Cloud Credentials: We have added a few enhancements to help improve the reliability of your credentials:
    • Azure Credential Expiration: By default, the secret/password for Azure Credentials expires after one years. This has led to unexpected disconnection of ParkMyCloud from a few customer Azure Subscriptions.  We now allow you to set the credential expiration time in the Azure Credential settings, allowing us to send you a Notification a week before the credential expires. Navigate to any existing Azure Credential and add the expiration date if you know it.  To find the expiration date in the Azure console, use the procedure described in our User Guide here.
    • Credential Error Notifications: We have moved most of the existing credential error notifications out of the System Errors notification into a new notification type: Credential Errors.  This includes the new Credential Expiration warning notification mentioned above. This is intended to help customers direct the right notification types to the right staff members.  To configure your notifications, navigate to the Notifications menu item in the left-menu.
    • Last Discovered: Besides the Azure credential expiration issues noted above, there can be other reasons why credentials can stop working, such as unintended permissions changes on the cloud side. Such changes can go unnoticed for a little while, especially for some of our larger customers that make heavy use of our Policies for schedule automation.  To help quickly diagnose issues, we have added a column to the Credentials screen that will show you the last time the Credential was successfully used to discovery workloads in your cloud accounts. 
  • SmartParking: The SmartParking default settings for RDS now require 0 connections to the database in order to generate a recommendation.  You can customize this setting on a per-team basis at Scheduling>SmartParking Recommendations>Options>Settings>Resource Type: Databases
  • Savings Summary Report: We have added a new report type for Scheduled Reports, the Savings Summaryreport.  This report will summarize your savings for the past 7 days, 30 days, month-to-date and year-to-date.  It also summarizes the quantity and potential savings from pending SmartParking and rightsizing recommendations.  This report is enabled daily by default for Admin users of new accounts, and will be enabled soon for all existing Admins, sent on a weekly basis.  You may add or edit this report manually in Reports>Scheduled Reports, and then add or Edit the ParkMyCloud Savings Summary report.
  • Teams: The maximum allowed length of a team name has been increased to 40 characters.
  • AWS EBS Volumes and EC2 Snapshots: We have started to collect AWS EBS Volume and EC2 Snapshot data in anticipation of our next release that will add management for these resources. We will soon be helping you identify unattached EBS Volumes, old and/or excessive snapshots, all of which add to your cloud costs.  We will also be providing a single-page view of all volumes and snapshots associated with a specific EC2 instance - a view not available in the AWS console.  Other clouds and resource types will be coming soon!
  • Schedules:
    • When adding/editing/viewing a weekly Schedule, we now show the numbers for "hours up" and "hours down" for the week, in addition to the percentage.
    • There is now a confirmation message if you try to navigate away from editing a schedule without saving it.

Fixed items

  • Login: Fixed an issue where selecting the login screen "Remember Me" button would give an error back from the server.
  • Serverless Aurora: These resources cannot be stopped, and so they are marked as unstoppable in the Console.
  • AWS RDS Pricing: Fixed some issues with Postgres and MySQL RDS pricing for the m5 and r5 families, caused by some undocumented price list changes related to AWS Outposts.

Version 7.16.0 - Released 2020-01-21

New/changed features

  • Logical Group Member Override: By request from a number of customers, it is now possible to override a member of a ParkMyCloud Logical Group, turning the resource on or off, regardless of the schedule assigned to the Logical Group itself.  This will allow for much easier maintenance activities on LG members, without the cost and potential delay and disruption of activating the entire LG.
  • Time format display: Also by customer request, we now allow users to set their preferred time format display, such as 4:30 PM vs 16:30.  Click your user name in the upper right of the Console, select My Profile > Display Settings > Time Format.
  • Invoicing: Invoice emails should now also have PDF attachments to simplify expanse management.

Fixed items

  • Reports: Cleaned up which reports should allow for selection of a time range, credentials, and/or teams.
  • AWS EC2 Reserved Instances Inventory Report: Fixed some data consistency issues.
  • Savings calculations: Fixed an issue related to calculating ParkMyCloud Savings for AWS EC2 handling of Windows instances. (From https://docs.aws.amazon.com/cli/latest/reference/ec2/stop-instances.html: Every time you start your Windows instance, Amazon EC2 charges you for a full instance hour. If you stop and restart your Windows instance, a new instance hour begins and Amazon EC2 charges you for another full instance hour even if you are still within the same 60-minute period when it was stopped. Every time you start your Linux instance, Amazon EC2 charges a one-minute minimum for instance usage, and thereafter charges per second for instance usage. Weird but true...)
  • Login: Fixed an issue where selecting the login screen "Remember Me" button would give an error back from the server.