AWS Resource Access Manager and AWS Organizations - AWS Organizations

AWS Resource Access Manager and AWS Organizations

AWS Resource Access Manager (AWS RAM) enables you to share specified AWS resources that you own with other AWS accounts. It's a centralized service that provides a consistent experience for sharing different types of AWS resources across multiple accounts.

For more information about AWS RAM, see the AWS RAM User Guide.

Use the following information to help you integrate AWS Resource Access Manager with AWS Organizations.

Service-linked roles created when you enable integration

The following service-linked role is automatically created in your organization's management account when you enable trusted access. This role allows AWS RAM to perform supported operations within your organization's accounts in your organization.

You can delete or modify this role only if you disable trusted access between AWS RAM and Organizations, or if you remove the member account from the organization.

  • AWSServiceRoleForResourceAccessManager

Service principals used by the service-linked roles

The service-linked role in the previous section can be assumed only by the service principals authorized by the trust relationships defined for the role. The service-linked roles used by AWS RAM grant access to the following service principals:

  • ram.amazonaws.com

Enabling trusted access with AWS RAM

For information about the permissions needed to enable trusted access, see Permissions required to enable trusted access.

You can enable trusted access using either the AWS Resource Access Manager console or the AWS Organizations console.

Important

We strongly recommend that whenever possible, you use the AWS Resource Access Manager console or tools to enable integration with Organizations. This lets AWS Resource Access Manager perform any configuration that it requires, such as creating resources needed by the service. Proceed with these steps only if you can’t enable integration using the tools provided by AWS Resource Access Manager.For more information, see this note.

If you enable trusted access by using the AWS Resource Access Manager console or tools then you don’t need to complete these steps.

To enable trusted access using the AWS RAM console or CLI

See Enable Sharing with AWS Organizations in the AWS RAM User Guide.

You can enable trusted access by using either the AWS Organizations console, by running a AWS CLI command, or by calling an API operation in one of the AWS SDKs.

AWS Management Console

To enable trusted service access using the Organizations console

  1. Sign in to the AWS Organizations console. You must sign in as an IAM user, assume an IAM role, or sign in as the root user (not recommended) in the organization’s management account.

  2. On the Services page, find the row for AWS Resource Access Manager, choose the service’s name, and then choose Enable trusted access.

  3. In the confirmation dialog box, enable Show the option to enable trusted access, enter enable in the box, and then choose Enable trusted access.

  4. If you are the administrator of only AWS Organizations, tell the administrator of AWS Resource Access Manager that they can now enable that service using its console to work with AWS Organizations.

AWS CLI, AWS API

To enable trusted service access using the OrganizationsCLI/SDK

You can use the following AWS CLI commands or API operations to enable trusted service access:

  • AWS CLI: enable-aws-service-access

    You can run the following command to enable AWS Resource Access Manager as a trusted service with Organizations.

    $ aws organizations enable-aws-service-access \ --service-principal ram.amazonaws.com

    This command produces no output when successful.

  • AWS API: EnableAWSServiceAccess

Disabling trusted access with AWS RAM

For information about the permissions needed to disable trusted access, see Permissions required to disable trusted access.

You can disable trusted access using either the AWS Resource Access Manager or AWS Organizations tools.

Important

We strongly recommend that whenever possible, you use the AWS Resource Access Manager console or tools to disable integration with Organizations. This lets AWS Resource Access Manager perform any clean up that it requires, such as deleting resources or access roles that are no longer needed by the service. Proceed with these steps only if you can’t disable integration using the tools provided by AWS Resource Access Manager.

If you disable trusted access by using the AWS Resource Access Manager console or tools then you don’t need to complete these steps.

To enable trusted access using the AWS Resource Access Manager console or CLI

See Enable Sharing with AWS Organizations in the AWS RAM User Guide.

You can disable trusted access by using either the AWS Organizations console, by running an Organizations AWS CLI command, or by calling an Organizations API operation in one of the AWS SDKs.

AWS Management Console

To disable trusted service access using the Organizations console

  1. Sign in to the AWS Organizations console. You must sign in as an IAM user, assume an IAM role, or sign in as the root user (not recommended) in the organization’s management account.

  2. On the Services page, find the row for AWS Resource Access Manager and then choose the service’s name.

  3. Choose Disable trusted access.

  4. In the confirmation dialog box, enter disable in the box, and then choose Disable trusted access.

  5. If you are the administrator of only AWS Organizations, tell the administrator of AWS Resource Access Manager that they can now disable that service using its console or tools from working with AWS Organizations.

AWS CLI, AWS API

To disable trusted service access using the Organizations CLI/SDK

You can use the following AWS CLI commands or API operations to disable trusted service access:

  • AWS CLI: disable-aws-service-access

    You can run the following command to disable AWS Resource Access Manager as a trusted service with Organizations.

    $ aws organizations disable-aws-service-access \ --service-principal ram.amazonaws.com

    This command produces no output when successful.

  • AWS API: DisableAWSServiceAccess