Locale selector icon
May202007

FlexOrgs - General Availability

Today, we’re announcing the general availability of FlexOrgs, giving you access to a powerful set of capabilities to enable more direct alignment between sources of truth within your enterprise (like identity systems, and Organizational trees) and your configuration of CloudHealth. With FlexOrgs you can:

  • Build hierarchical organizations up to 10 levels deep. Reflect the way your business is actually structured so you can more easily communicate and drive collaboration over familiar channels.

  • Create User Groups based on the rich information in your Identity Systems. Unlock the power of SSO and allow your group membership to automatically map users to the correct groups and permissions. Allow changes within your directory to automatically change permissions and access within CloudHealth.

  • Allow users to live in multiple organizations. With the addition of Role Documents and User Groups users can have different permissions in many organizations. This ability will empower the CCoE to delegate control of CloudHealth deeper into their organization and trust that their users have the right capabilities for the right data.

This is the first release of several that will allow administrators to delegate the full power of the CloudHealth platform to their users. All of this functionality is backed by powerful GraphQL APIs that will allow you to truly manage effectively at scale.

Admins can navigate to Setup → Admin → FlexOrgs to begin using this powerful feature. Join our Power of the Platform training on May 12th to learn more about this feature, make sure to have CloudHealth Academy open prior to clicking the link. 

New Indirect Cost - Direct Connect Data Transfer

AWS announced some changes in Direct Connect Data Transfer Out charges late last year. Direct Connect’s Data Transfer Charges are not attributed to the Direct Connect resources anymore. Instead, the direct connect charge will be attributed to the AWS service that uses it. This means Product Name and Resource Id in your bills will not match to a particular service in the case of Direct Connect Data Transfer charges. To cope with these changes, we have added a new indirect cost categorization for Direct Connect Data Transfer charges. These charges are now represented as their own Indirect Cost, which can be assigned to Perspective Groups using cost reallocation rules. Previously, these charges were included under a direct service item called ‘Direct Connect - Data Transfer’.

Support for Additional AWS Services

As previously announced, we have developed a more comprehensive approach for extracting asset attributes from bills to allocate costs for AWS services using AWS and CloudHealth tags. In the next few days, we will update costs for the services mentioned below.

  1. Amazon Athena

  2. AWS Cloud Map

  3. AWS Data Exchange

  4. Amazon DocumentDB

  5. AWS Elemental MediaConnect

  6. Amazon Kendra

  7. Amazon RDS Clusters (Aurora)

  8. AWS Security Hub

  9. On-Demand Capacity reservation

Previously, these costs were lumped into the indirect cost item - ‘Other’. Going forward, costs associated with the services listed above will be distributed into the following direct charges:

  • Athena

  • Cloud Map - Service Registry

  • Data Exchange - Storage Fees

  • DocumentDB - Backup

  • DocumentDB - Compute

  • DocumentDB - I/O

  • DocumentDB - Storage

  • Elemental MediaConnect - Active Resources

  • Elemental MediaConnect - Data Transfer

  • Kendra - Enterprise Edition

  • Kendra - Storage capacity

  • Kendra - Connector

  • RDS - Compute

  • RDS - Charged Backup Usage

  • RDS - I/O

  • RDS - Backtrack

  • RDS - Multi-AZ PIOPs

  • RDS - Multi-AZ PIOPs Storage

  • RDS - Multi-AZ GP2 Storage

  • Security Hub - Checks and Events

  • EC2 - Unused Capacity Reservation

And the following indirect charges:

  • Athena - Other

  • Cloud Map - Lookup Requests

  • Cloud Map - Other

  • Data Exchange - Other

  • DocumentDB - Other

  • Elemental MediaConnect - Other

  • Kendra - Other

  • RDS - Other

  • Security Hub - Other

  • EC2 Usage

For the services mentioned above, we will be using AWS Tags, CloudHealth Tags and Resource Id for cost and asset allocation. This allocation will be applicable to the past 13 months. We recommend that you update or add your reallocation rules to adapt to this change.

Learn more about supported AWS services in this Help Center article.

Update to AWS Config Rules Governance Report

Until now, the AWS Config Rules Governance Report presented compliance state only for the resource types supported in the CloudHealth platform. Many of you used it for internal periodic audits and communicated the need for an upgrade. To provide you with the most current and reliable data as much as possible, we extended this governance report to all available resource types while bumping up the frequency of collection of Config rule assessments from your AWS environment. Going forward, we will report the most appropriate compliance state for your AWS resources. We will report an “Insufficient Data” state for those config rules for which we don’t receive any associated resources or evaluations.