To share a resource that you own by using AWS RAM, do the following:
NotesSharing a resource with principals outside of the AWS account that owns the resource doesn't change the permissions or quotas that apply to the resource within the account that created it.
AWS RAM is a Regional service. The principals that you share with can access resource shares in only the AWS Regions in which the resources were created.
Some resources have special considerations and prerequisites for sharing. For more information, see Shareable AWS resources.
When your account is managed by AWS Organizations, you can take advantage of that to share resources more easily. With or without Organizations, a user can share with individual accounts. However, if your account is in an organization, then you can share with individual accounts, or with all accounts in the organization or in an OU without having to enumerate each account.
To share resources within an organization, you must first use the AWS RAM console or AWS Command Line Interface (AWS CLI) to enable sharing with AWS Organizations. When you share resources in your organization, AWS RAM doesn't send invitations to principals. Principals in your organization gain access to shared resources without exchanging invitations.
When you enable resource sharing within your organization, AWS RAM creates a service-linked role called AWSServiceRoleForResourceAccessManager. This role can be assumed by only the AWS RAM service, and grants AWS RAM permission to retrieve information about the organization it is a member of, by using the AWS managed policy AWSResourceAccessManagerServiceRolePolicy.
When sharing with AWS Organizations is enabled, any resource sharing within the organization is restricted to consumers within the same organization. This means if the consumer leaves the organization, they will lose access to the resources in the resource share. This is true when the resource is shared with an OU, the entire organization, or an individual account in the organization.
If you no longer need to share resources with your entire organization or OUs, you can disable resource sharing. For more information, see Disabling resource sharing with AWS Organizations.
Minimum permissionsTo run the procedures below, you must sign in as a principal in the organization's management account that has the following permissions:
ram:EnableSharingWithAwsOrganization
iam:CreateServiceLinkedRole
organizations:enableAWSServiceAccess
organizations:DescribeOrganization
You can perform these steps only while signed in as a principal in the organization's management account.
The organization must have all features enabled. For more information, see Enabling all features in your organization in the AWS Organizations User Guide.
You must enable sharing with AWS Organizations by using the AWS RAM console or the enable-sharing-with-aws-organization AWS CLI command. This ensures that the AWSServiceRoleForResourceAccessManager service-linked role is created. If you enable trusted access with AWS Organizations by using the AWS Organizations console or the enable-aws-service-access AWS CLI command, the AWSServiceRoleForResourceAccessManager service-linked role isn't created, and you can't share resources within your organization.
Open the Settings page in the AWS RAM console.
Choose Enable sharing with AWS Organizations, and then choose Save settings.
Use the enable-sharing-with-aws-organization command.
This command can be used in any AWS Region, and it enables sharing with AWS Organizations in all Regions in which AWS RAM is supported.
$ aws ram enable-sharing-with-aws-organization
{
"returnValue": true
}To share resources that you own, create a resource share. Here's an overview of the process:
Add the resources that you want to share.
For each resource type that you include in the share, specify the managed permission to use for that resource type.
You can choose from one of the available AWS managed permissions, an existing customer managed permission, or create a new customer managed permission.
AWS managed permissions are created by AWS to cover standard use cases.
Customer managed permissions allow you to tailor your own managed permissions to meet your security and business needs.
If the selected managed permission has multiple versions, then AWS RAM automatically attaches the default version. You can attach only the version that is designated as the default.
Specify the principals that you want to have access to the resources.
If you later need to delete an AWS resource that you included in a share, we recommend that you first either remove the resource from any resource share that includes it, or delete the resource share.
The resource types that you can include in a resource share are listed at Shareable AWS resources.
You can share a resource only if you own it. You can't share a resource that's shared with you.
AWS RAM is a Regional service. When you share a resource with principals in other AWS accounts, those principals must access each resource from the same AWS Region that it was created in. For supported global resources, you can access those resources from any AWS Region that's supported by that resource's service console and tools. You can view such resource shares and their global resources in the AWS RAM console and tools only in the designated home Region, US East (N. Virginia), us-east-1. For more information about AWS RAM and global resources, see Sharing Regional resources compared to global resources.
If the account you're sharing from is part of an organization in AWS Organizations and sharing within your organization is enabled, any principals in the organization that you share with are automatically granted access to the resource shares without the use of invitations. A principal in an account with whom you share outside of the context of an organization receives an invitation to join the resource share and is granted access to the shared resources only after they accept the invitation.
If you share with a service principal, you can't associate any other principals with the resource share.
If the sharing is between accounts or principals that are part of an organization, then any changes to organization membership dynamically affect access to the resource share.
If you add an AWS account to the organization or an OU that has access to a resource share, then that new member account automatically gets access to the resource share. The administrator of the account you shared with can then grant individual principals in that account access to the resources in that share.
If you remove an account from the organization or an OU that has access to a resource share, then any principals in that account automatically lose access to resources that were accessed through that resource share.
If you shared directly with a member account or with IAM roles or users in the member account and then remove that account from the organization, then any principals in that account lose access to the resources that were accessed through that resource share.
When you share with an organization or an OU, and that scope includes the account that owns the resource share, all principals in the sharing account automatically get access to the resources in the share. The access granted is defined by the managed permissions associated with the share. This is because the resource-based policy that AWS RAM attaches to each resource in the share uses "Principal": "*". For more information, see Implications of using "Principal": "*" in a resource-based policy.
Principals in the other consuming accounts don't immediately get access to the share's resources. The other accounts' administrators must first attach identity-based permission policies to the appropriate principals. Those policies must grant Allow access to the ARNs of individual resources in the resource share. The permissions in those policies can't exceed those specified in the managed permission associated with the resource share.
You can add only the organization your account is a member of, and OUs from that organization to your resource shares. You can't add OUs or organizations from outside your own organization to a resource share as principals. However, you can add individual AWS accounts or, for supported services, IAM roles and users from outside your organization as principals to a resource share.
NoteNot all resource types can be shared with IAM roles and users. For information about resources that you can share with these principals, see Shareable AWS resources.
For the following resource types you have seven days to accept the invitation to join the share for the following resource types. If you don't accept the invitation before it expires, the invitation is automatically declined.
ImportantFor shared resource types not on the following list, you have 12 hours to accept the invitation to join the resource share. After 12 hours, the invitation expires and the end user principal in the resource share is disassociated. The invitation can no longer be accepted by end users.
Amazon Aurora â DB clusters
Amazon EC2 â capacity reservations and dedicated hosts
AWS License Manager â License configurations
AWS Outposts â Local gateway route tables, outposts, and sites
Amazon Route 53 â Forwarding rules
Amazon VPC â Customer-owned IPv4 addresses, prefix lists, subnets, traffic mirror targets, transit gateways, transit gateway multicast domains
Open the AWS RAM console.
Because AWS RAM resource shares exist in specific AWS Regions, choose the appropriate AWS Region from the dropdown list in the upper-right corner of the console. To see resource shares that contain global resources, you must set the AWS Region to US East (N. Virginia), (us-east-1). For more information about sharing global resources, see Sharing Regional resources compared to global resources. If you want to include global resources in the resource share, then you must choose the designated home Region, US East (N. Virginia), us-east-1.
If you're new to AWS RAM, choose Create a resource share from the home page. Otherwise, choose Create resource share from the Shared by me : Resource shares page.
In Step 1: Specify resource share details, do the following:
For Name, enter a descriptive name for the resource share.
Under Resources, choose resources to add to the resource share as follows:
For Select resource type, choose the type of resource to share. This filters the list of shareable resources to only those resources of the selected type.
In the resulting list of resources, select the checkboxes next to the individual resources that you want to share. The selected resources move under Selected resources.
If you're sharing resources that are associated with a specific availability zone, then using the Availability Zone ID (AZ ID) helps you determine the relative location of these resources across accounts. For more information, see Availability Zone IDs for your AWS resources.
(Optional) To attach tags to the resource share, under Tags, enter a tag key and value. Add others by choosing Add new tag. Repeat this step as needed. These tags apply to only the resource share itself, not to the resources in the resource share.
Choose Next.
In Step 2: Associate a managed permission with each resource type, you can choose to associate a managed permission created by AWS with the resource type, choose an existing customer managed permission, or you can create your own customer managed permission for supported resource types. For more information, see Types of managed permissions.
Choose Create customer managed permission to construct a customer managed permission that meets the requirements of your sharing use case. For more information see Create a customer managed permission. After completing the process, choose and then you can select your new customer managed permission from the Managed permissions dropdown list.
NoteIf the selected managed permission has multiple versions, then AWS RAM automatically attaches the default version. You can attach only the version designated as the default.
To display the actions that the managed permission allows, expand View the policy template for this managed permission.
Choose Next.
In Step 3: Grant access to principals, do the following:
By default, Allow sharing with anyone is selected, which means that, for those resource types that support it, you can share resources with AWS accounts that are outside of your organization. This doesn't affect resource types that can be shared only within an organization, such as Amazon VPC subnets. You can also share some supported resource types with IAM roles and users.
To restrict resource sharing to only accounts and principals in your organization, choose Allow sharing only within your organization.
For Principals, do the following:
To add the organization, an organizational unit (OU), or an AWS account that is part of an organization, turn on Display organizational structure. This displays a tree view of your organization. Then, select the checkbox next to each principal that you want to add.
ImportantWhen you share with an organization or an OU, and that scope includes the account that owns the resource share, all principals in the sharing account automatically get access to the resources in the share. The access granted is defined by the managed permissions associated with the share. This is because the resource-based policy that AWS RAM attaches to each resource in the share uses "Principal": "*". For more information, see Implications of using "Principal": "*" in a resource-based policy.
Principals in the other consuming accounts don't immediately get access to the share's resources. The other accounts' administrators must first attach identity-based permission policies to the appropriate principals. Those policies must grant Allow access to the ARNs of individual resources in the resource share. The permissions in those policies can't exceed those specified in the managed permission associated with the resource share.
If you select the organization (the ID begins with o-), then principals in all AWS accounts in the organization can access the resource share.
If you select an OU (the ID begins with ou-), then principals in all AWS accounts in that OU and its child OUs can access the resource share.
If you select an individual AWS account, then only principals in that account can access the resource share.
The Display organizational structure toggle appears only if sharing with AWS Organizations is enabled and you're signed in to the management account for the organization.
You can't use this method to specify an AWS account outside your organization, or an IAM role or user. Instead, you must turn off Display organizational structure and use the drop down list and text box to enter the ID or ARN.
To specify a principal by ID or ARN, including principals that are outside of the organization, then for each principal, select the principal type. Next, enter the ID (for an AWS account, organization, or OU) or ARN (for an IAM role or user), and then choose Add. The available principal types and ID and ARN formats are as follows:
AWS account â To add an AWS account, enter the 12-digit account ID. For example:
123456789012
Organization â To add all of the AWS accounts in your organization, enter the ID of the organization. For example:
o-abcd1234
Organizational unit (OU) â To add an OU, enter the ID of the OU. For example:
ou-abcd-1234efgh
IAM role â To add an IAM role, enter the ARN of the role. Use the following syntax:
arn:partition:iam::account:role/role-name
For example:
arn:aws:iam::123456789012:role/MyS3AccessRole
IAM user â To add an IAM user, enter the ARN of the user. Use the following syntax:
arn:partition:iam::account:user/user-name
For example:
arn:aws:iam::123456789012:user/bob
Service principal â To add a service principal, choose Service principal from the Select principal type dropbox. Enter the AWS service principal's name. Use the following syntax:
service-id.amazonaws.com
For example:
pca-connector-ad.amazonaws.com
For Selected principals, verify that the principals you specified appear in the list.
Choose Next.
In Step 4: Review and create, review the configuration details for your resource share. To change the configuration for any step, choose the link that corresponds to the step you want to go back to and make the required changes.
After you finish reviewing the resource share, choose Create resource share.
It can take a few minutes for the resource and principal associations to complete. Allow this process to complete before you try to use the resource share.
You can add and remove resources and principals or apply custom tags to your resource share at any time. You can change the managed permission for resource types that are included in your resource share, for those types that support more than the default managed permission. You can delete your resource share when you no longer want to share the resources. For more information, see Share AWS resources owned by you.
Use the create-resource-share command. The following command creates a resource share that is shared with all of the AWS accounts in the organization. The share contains an AWS License Manager license configuration, and it grants the default managed permissions for that resource type.
NoteIf you want to use a customer managed permission with a resource type in this resource share, you can either use an existing customer managed permission or create a new customer managed permission. Make note of the ARN for the customer managed permission, and then create the resource share. For more information, see Create a customer managed permission.
$ aws ram create-resource-share \
--region us-east-1 \
--name MyLicenseConfigShare \
--permission-arns arn:aws:ram::aws:permission/AWSRAMDefaultPermissionLicenseConfiguration \
--resource-arns arn:aws:license-manager:us-east-1:123456789012:license-configuration:lic-abc123 \
--principals arn:aws:organizations::123456789012:organization/o-1234abcd
{
"resourceShare": {
"resourceShareArn": "arn:aws:ram:us-east-1:123456789012:resource-share/12345678-abcd-09876543",
"name": "MyLicenseConfigShare",
"owningAccountId": "123456789012",
"allowExternalPrincipals": true,
"status": "ACTIVE",
"creationTime": "2021-09-14T20:42:40.266000-07:00",
"lastUpdatedTime": "2021-09-14T20:42:40.266000-07:00"
}
}RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4