copyright

lastupdated

keywords

subcollection

years
2024, 2025

2025-01-16

cloud-logs

Creating a S2S authorization to grant {{site.data.keyword.logs_full_notm}} access to {{site.data.keyword.en_full_notm}}

{: #iam-service-auth-en}

Use {{site.data.keyword.iamlong}} (IAM) to create an authorization that grants {{site.data.keyword.logs_full_notm}} access to the {{site.data.keyword.en_full_notm}} service. {: shortdesc}

Before you begin

{: #iam-service-auth-en-prereqs}

Read about Managing authorizations to grant access between services.
You must have access to the {{site.data.keyword.en_full_notm}} target service to manage authorization between services. For more information, see Permissions to manage authorizations.
The target service is located always in the account where the authorization is created.
The autorization that you define for the {{site.data.keyword.logs_full_notm}} service requires that you have Administrator role for the {{site.data.keyword.en_full_notm}} target.
If you create an authorization between a service in another account and a target service in your current account, you need to have access only to the target resource. For the source account, you need only the account ID.

Service access roles

{: #iam-service-auth-en-roles}

You can select any of the following roles that the source can use to interact with the target. You can grant only the level of access that you have as a user of the target that you selected.

Event Source Manager: You must grant Event Source Manager role to handle source integration with the {{site.data.keyword.en_full_notm}} service.
Reader: You must grant Reader role to perform read-only actions within a service such as viewing service-specific resources.
Viewer: You must grant Viewer role to list the {{site.data.keyword.en_full_notm}} service instances.

For more information, see Creating a S2S authorization to work with the {{site.data.keyword.en_full_notm}} service.

Creating an authorization through the console

{: #iam-service-auth-en-create-ui} {: ui}

Complete the following steps:

In the {{site.data.keyword.cloud_notm}} console, click Manage > Access (IAM), and select Authorizations.
Click Create.
Select a source account.

If the source service that needs access to the target service is in this account, select This account.

If the source service that needs access to the target service is in a different account, select Other account. Then, enter the account ID of the source account.
Select Cloud Logs as the source service. Then, set the scope of the access.

Select All resources to grant access for all instances in the account.

Select Source service instance to grant access to 1 {{site.data.keyword.logs_full_notm}} instance.
Select Events Notification as the target service. Then, set the scope of the access.

To grant access to all {{site.data.keyword.en_full_notm}} instances and resources in the account, select All resources.

To grant access to a specific instance, select single instance by configuring Resources based on selected attributes > Service Instance.
In the Service Access section, select the role to assign access to the source service that accesses the target service.

Select Reader to perform read-only actions within a service such as viewing service-specific resources.

Select Event Source Manager to handle source integration with the event-notifications service.
Click Authorize.

If you create an authorization between a service in another account and a target service in your current account, you need to have access only to the target resource. For the source account, you need only the account number. {: note}

Creating an authorization by using the CLI

{: #iam-service-auth-en-create-cli} {: cli}

Run the following command to create an authorization for the {{site.data.keyword.logs_full_notm}} service.

ibmcloud iam authorization-policy-create logs event-notifications "Reader" [--source-service-instance-name SOURCE_SERVICE_INSTANCE_NAME | --source-service-instance-id SOURCE_SERVICE_INSTANCE_ID] [--target-service-instance-name TARGET_SERVICE_INSTANCE_NAME | --target-service-instance-id TARGET_SERVICE_INSTANCE_ID]

{: codeblock}

For more information about all of the parameters that are available for this command, see ibmcloud iam authorization-policy-create.

Creating an authorization by using Terraform

{: #iam-service-auth-en-create-terra} {: terraform}

Before you can create an authorization by using Terraform, make sure that you have completed the following:

Install the Terraform CLI and configure the {{site.data.keyword.cloud_notm}} Provider plug-in for Terraform. For more information, see the tutorial for Getting started with Terraform on {{site.data.keyword.cloud_notm}}. The plug-in abstracts the {{site.data.keyword.cloud_notm}} APIs that are used to complete this task.
Create a Terraform configuration file that is named main.tf. In this file, you define resources by using HashiCorp Configuration Language. For more information, see the Terraform documentation{: external}.

Use the following steps to create an authorization by using Terraform:

Create an authorization policy between services by using the ibm_iam_authorization_policy resource argument in your main.tf file.

The following example creates an authorization between 2 services:
```
resource "ibm_iam_authorization_policy" "policy" {
 source_service_name = "logs"
 target_service_name = "event-notifications"
 roles               = ["Reader"]
 description         = "Authorization Policy"
 transaction_id     = "terraformAuthorizationPolicy"
}
```
{: codeblock}

The following example creates an authorization between 2 specific service instances:
```
resource "ibm_iam_authorization_policy" "policy" {
  source_service_name         = "logs"
  source_resource_instance_id = ibm_resource_instance.instance1.guid
  target_service_name         = "event-notifications"
  target_resource_instance_id = ibm_resource_instance.instance2.guid
  roles                       = ["Reader"]
}
```
{: codeblock}

The ibm_iam_authorization_policy resource requires the source service, target service, and role. The source service is granted access to the target service, and the role is the level of permission that the access allows. Optionally, you can add a description for the authorization and a transaction ID. {: note}
- You can provide a target_resource_instance_id to scope a {{site.data.keyword.en_full_notm}} target instance.
- For more examples, see the Terraform documentation for authorization resources{: external}.
After you finish building your configuration file, initialize the Terraform CLI. For more information, see Initializing Working Directories{: external}.
```
terraform init
```
{: pre}
Provision the resources from the main.tf file. For more information, see Provisioning Infrastructure with Terraform{: external}.
1. Run terraform plan to generate a Terraform execution plan to preview the proposed actions.
```
terraform plan
```
  {: pre}
2. Run terraform apply to create the resources that are defined in the plan.
```
terraform apply
```
  {: pre}

Creating an authorization by using the API

{: #iam-service-auth-en-create-api} {: api}

To authorize a source service access to a target service, use the IAM Policy Management API. See the following API example for create a policy method with the type=authorization specified for a event-notifications target.

The supported attributes for creating an authorization policy depend on what each service supports. For more information about the supported attributes for each service, see the documentation for the services that you're using. {: note}

curl --request POST \
  --url https://iam.cloud.ibm.com/v1/policies \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "type": "authorization",
    "subjects": [
        {
            "attributes": [
                {
                    "name": "accountId",
                    "value": "<account-id>"
                },
                {
                    "name": "serviceName",
                    "value": "logs"
                }
            ]
        }
    ],
    "roles": [
        {
            "role_id": "crn:v1:bluemix:public:event-notifications::::serviceRole:Reader"
        }
    ],
    "resources": [
        {
            "attributes": [
                {
                    "name": "serviceName",
                    "value": "event-notifications"
                }
            ]
        }
    ]
}'

{: curl} {: codeblock}

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

iam-service-auth-en.md

iam-service-auth-en.md

Creating a S2S authorization to grant {{site.data.keyword.logs_full_notm}} access to {{site.data.keyword.en_full_notm}}

Before you begin

Service access roles

Creating an authorization through the console

Creating an authorization by using the CLI

Creating an authorization by using Terraform

Creating an authorization by using the API

Files

iam-service-auth-en.md

Latest commit

History

iam-service-auth-en.md

File metadata and controls

Creating a S2S authorization to grant {{site.data.keyword.logs_full_notm}} access to {{site.data.keyword.en_full_notm}}

Before you begin

Service access roles

Creating an authorization through the console

Creating an authorization by using the CLI

Creating an authorization by using Terraform

Creating an authorization by using the API