Governing it the Cloud-Native Way!
Each cloud irrespective of private or public, have its own set of service offerings. These service offerings vary in the way it is configured, provisioned and consumed. This is because of its architecture, capabilities, options to integrate with other services within the same or across cloud platforms.
So, orchestrating the cloud platforms are to be done without impacting its native service capabilities and then extend each service to add more values that these cloud platforms don’t support either directly or indirectly.
One of the USPs of CoreStack is to do everything cloud native, be it Orchestration or Governance. And then add extend some additional features not supported by them natively.
Don’t just automate, Govern the 4Cs of Cloud!
CoreStack being an Autonomous Cloud Governance platform, does much more than orchestrate services across cloud platforms. It provides values in terms of
- Cloud Operations & Governance
- Compliance & Security
- Cost Visibility & Optimization
- Consumption (Self-Service based on request-approval workflow)
How does it work?
Typically, an account or a subscription with a cloud platform can be orchestrated and managed using different ways such as,
- API Access Keys & Secret Keys
- Username & password along with authentication endpoint
- Authentication Tokens
Above mentioned authentication mechanisms vary from one cloud platform to the other.
A “Cloud Account” is an account or a subscription with a cloud platform that is onboarded into CoreStack using one of the above authentication mechanisms. By onboarding a cloud account, users provide the required permissions to CoreStack for orchestration & management of the different services within the cloud platform.
In some cases, Cloud COE/Admin need to perform certain pre-requisite configuration in Cloud Platform before onboarding into CoreStack. The steps involved vary based on cloud platform, so detailed steps can be referred in the respective Cloud Account onboarding sections of this documentation.
Configure your Governance Level
As part of the cloud account onboarding, users can configure the account for Activity Monitoring, Alerts & Notification, Compliance Standards, Security, Budget and so on. There are three types of Cloud Account Settings supported by CoreStack,
- Custom – Allow configuration of different CoreStack functions for the cloud account. Detailed level of customization of settings is possible
- Express – Configurations are pre-defined as per the recommendations of CoreStack
- None – Only allow the orchestration and no other cloud functions of CoreStack are configured or allowed
With Custom & Express settings,
- While Onboarding a Cloud account, CoreStack will setup certain services, create few resources, modify settings of certain Cloud Native Services or enable periodic checks based on the configuration information captured during onboarding. These settings help CoreStack govern the cloud accounts effectively as per the industry standards.
- While Disabling a Cloud Account, CoreStack disables the periodic checks, stops the resources created during onboarding, however they will not be cleaned up completely. This is to allow enabling the cloud accounts in CoreStack later if required.
- While Deleting a Cloud Account, all the settings or services configured will automatically be reverted or cleaned. Details of the same will be available further in the documentation for respective clouds.