| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2019-05-17 |
blog, resource, group, access, management, identity, IAM, isolated |
vpc-on-classic |
{:shortdesc: .shortdesc} {:new_window: target="_blank"} {:codeblock: .codeblock} {:pre: .pre} {:screen: .screen} {:tip: .tip} {:important: .important} {:download: .download}
{: #other-resources}
- Blog by Faiyaz Shahpurwala, General Manager, IBM Cloud
{: new_window}
When the service becomes generally available later this year, VPC will be designed to allow clients to create an isolated cloud environment spanning multiple regions and connected to their on-premises environments. VPC is the next wave in {{site.data.keyword.cloud}} network-based isolation, enabling private endpoint connectivity for our virtual servers.
In November 2017, IBM Cloud added support for resource groups. This enables you to group resources across regions and to manage access to those resources based on their resource groups. For more information on resource group management, please visit our docs. Once you’ve created resource groups, let’s take a look at some best practices on how to manage access for those groups.
IBM Cloud Identity & Access Management enables you to securely authenticate users and control access to all cloud resources consistently in the IBM Bluemix Cloud Platform. This is a core capability of platform which means it’s no extra cost to you.