Cloud connections

you can establish a connection for common services for the following cloud providers ibm cloud microsoft azure (csp, ea, application insights, mpa and subscription) google cloud aws alibaba cloud vmware vsphere demo cloud byod private container cluster registering a connection after creating your cloud account with certain policy permissions, you need to register a connection in the credentials of your account are the ones that will be added to the page the configuration and credential details required will vary based on the selected cloud provider please ensure that you complete all fields on the page with the correct information the following example outlines the onboarding process for an aws connection from the side panel menu, select the cloud connections option select add connection the add connection page opens complete the following information to onboard your supported cloud connection connection name enter the connection name of your choice description enter the description for the connection technology category select cloud provider from the drop down menu connection type select the cloud connection from the drop down menu tags select a tag from the drop down menu if no access tags have been created, you can add them directly on the tool page to learn more about access tags, see access tags management docid\ ecmgteantw7m2dkr4 jth add the configuration details not all the details are required; it depends on the cloud provider selected billing data toggle toggle on if you are using this connection for billing data if the billing data is enabled, complete the following information cost and usage report path enter the cost and usage report path account number enter the account number for which the bill is to be generated account number enter the account number s3 bucket enter the s3 bucket credential additional info enter any additional info required region enter the id of the region where the service will be accessed in the context of setting up a credential for aws, the region refers to the aws region that will be specified in all aws apis calls made through this connection this setting ensures that the content returned by api calls is limited to the specified aws region advance click the down arrow and complete the following information delegated access enter the arn external id enter the external id add the credential details not all the details are required; it depends on the cloud provider selected access key id enter the access key id secret access key enter the secret access key client id enter the client id secret enter the secret id or api key user enter the username api key enter the api key data set enter data set service key enter the billing json key (in base 64) click test connection to test whether the credentials are valid this is a crucial step prior to adding the connection typically, the connection fails because the credentials are incorrect or the data cannot be displayed due to a permission limitation click add a “success \[connection name] has been successfully added” alert is displayed additionally, the new connection can be viewed on the page if the connection is not successful, a “failed \[connection name] could not be added” alert with the reasons for failure is displayed if all the information added is correct, and you are still encountering issues, create a support ticket docid\ nfbfvqtijz6zesjmhg8b9 deleting a connection often, you may want to unregister a connection to maintain control of your it data from the cloud page click the actions icon next to the connection you want to delete and select delete type the name of the connection and click confirm click the global menu icon click services and select common inventory the common inventory page opens on the top left corner, click on the page filter icon located below the inventory header expand the provider information and select the account name radio button, if not selected already type the name of the connection and click confirm search by the connection name that was deleted if a user has added multiple connections with the same account number, deleting one connection will only remove that specific connection and its resource information the account number will still be visible in the page, as it is also associated with other connections