Managing access for apps in compute resources
This tutorial guides you through the steps to centrally manage fine-grained authorization for all applications that are running in a compute resource without creating service IDs or managing the API key lifecycle for applications. By completing this tutorial, you learn how to create a trusted profile, establish trust with compute resources based on specific attributes, and define a policy to assign access to resources.
By using trusted profiles, you can establish a flexible, secure way for apps that are running on a compute resource to access other IBM Cloud® resources. All compute resource instances that share certain attributes, such as name, namespace, tags, or location, are mapped to a common profile and can share access to IBM Cloud resources. This common identity makes it possible to give the applications within various compute resources access to an external resource one time, rather than cluster-by-cluster.
You must enable the Service Account Token Volume Projection on the Kubernetes cluster to apply the trusted profile identity. For more information, see Authorizing pods in your cluster to IBM Cloud services with IAM trusted profiles
Let's say that you are the lead developer on a project for your team that is planning to run a new chatbot app on an IBM Cloud® Kubernetes Service cluster. You want the app to have access to IAM-enabled services but without storing credentials in the code. Your manager has given you an administrator access in the account to create trusted profiles and give your runtime environments access to the resources you need to build the chatbot app.
Before you begin
- This tutorial might incur costs. Use the Cost Estimator to generate a cost estimate based on your projected usage.
- Make sure you have the following access:
- Administrator role in the account to create a trusted profile
- Administrator role on the specific resources to which you are assigning access
- Create a cluster that runs IBM Cloud Kubernetes Service Version 1.21 or later. For information about creating a cluster, see Getting started with IBM Cloud Kubernetes Service.
Create a trusted profile
First, create your trusted profile:
- Go to Manage > Access (IAM) in the IBM Cloud console, and select Trusted profiles.
- Click Create profile.
- Name the profile
Chatbot Project
. - In the description, list the level of access you want to assign to the profile. This helps you quickly identify different profiles from the list of trusted profiles. In this case:
- Writer
- Manager
- Click Continue.
Make sure that your profile name is short and human readable. For compute resources, the name of the profile is required to get the compute resource token, so a simple name is easier for developers to use in the program.
Establish trust with the Kubernetes cluster
Now that you created your trusted profile, you want to establish trust with the Kubernetes cluster you created for the project:
-
For trust entity type, select Compute resources.
-
For compute service, select Kubernetes from the list.
-
Select Specific resources to establish trust with one or more existing compute resource instances.
-
Click Add another resource.
-
Select the cluster that you created for this tutorial.
-
Enter the values for the
namespace
andservice account
fields.The Kubernetes namespace and service account names that you enter do not have to exist already. Any future namespaces or service accounts with these names can establish trust. To list existing namespaces, log in to your cluster and run
kubectl get ns
. To list existing service accounts, log in to your cluster and runkubectl get sa -n <namespace>
. You can also enterdefault
for both. -
Click Continue.
Assign access to other IBM Cloud services
Now, you can create an access policy to give your compute resource instance access to other IBM Cloud services you need for your team's chatbot project.
- Select Access policy.
- Select Watson Assistant from the list of services. Make sure you have access on the service you want to give access to in this profile.Click Next.
- Scope the access to Specific resources based on selected attributes.
- Select Service Instance and input the service instance name to give permission to a specific instance. Click Next.
- Select Writer and Manager roles to define the scope of access, and click Review.
- Click Add to add your policy configuration to your policy summary.
- Click Assign.
Next steps
To learn more about establishing trust with a Kubernetes cluster, see Using Trusted Profiles in your Kubernetes and OpenShift Clusters. To learn how to use trusted profiles with VPC virtual server instances, see Introducing Trusted Profiles for VPC Virtual Server Instances.
Now that you learned the basics of how to create a trusted profile, you can continue to establish trust with additional compute resources. For more information, see Updating trusted profiles.
You can also use Activity Tracker to monitor which federated users and compute resources apply a trusted profile. For more information, see Monitoring login sessions for trusted profiles.