Oracle Cloud Infrastructure Documentation

Resource Sharing (Optional)

Resource Sharing uses AWS Resource Access Manager (RAM) to grant controlled access without duplicating resources. This helps reduce costs, centralize management, and simplify cross-account networking and service usage.

You can share the following Oracle Database@AWS resources:
  • ODB Network
  • Oracle Exadata Infrastructure
Note

You can only share resources with a trusted account that has not accepted any private Oracle Database@AWS offer.

  • Share Resources from the Buyer Account to Trusted Account

    Complete the following steps:
    1. Sign in to your AWS buyer account.
    2. From the AWS console, select Resource Access Manager, and then select the Resource shares link from the left menu.
    3. Select the Create resource share button, and then complete the following substeps:
      1. In the Specify resource share details section, enter the following information:
        1. Enter a Name to provide a description for your resource share.
          Note

          The resource share name must contain only alphabetic characters, numbers, spaces, periods, and dashes.
        2. The Resources section is optional. For example, if you select your resource type as Oracle Database@AWS Exadata Infrastructure from the dropdown list, it populates available Exadata Infrastructure resource(s) that you can choose to add to the resource share.
        3. From the Selected resources section, select the checkbox of your resource.
        4. The Tags section is optional. Select the Add new tag button if you want to add one.
          Note

          Tags are key-value pairs that enable you to add to AWS resources to identify, organize and secure them.
        5. Select the Next button to proceed.
        This screenshot shows how to create a resource share.
      2. In the Associate managed permissions section, you can view the Managed Permissions, Version and View the policy template for this managed permission details. These automatically populates based on your Resource selection. The View the policy template for this managed permission section lists all permissions that are going to be granted. Select the Next button to proceed.This screenshot shows how to create resource share.
      3. In the Grant access to principals step, enter the following information:
        1. The Principal section is optional. If you want to grant access to principal, complete the following steps:
          1. Select the Allow sharing only within your organization option.
          2. From the dropdown list, select the principal type.
          3. Enter an AWS account ID of trusted account.
          4. Select the Add button to grant access to your selected principals.
          5. Once you add your principal(s), the Selected principals section displays the list of Principal ID. Select the checkbox to allow principals access to the shared resources.
          6. Select the Next button to proceed.
          This screenshot shows how to create resource share.
      4. In the Review and create step, review your selection and return to previous steps if you want to make any changes. Once you complete, select the Create resource share.
      This screenshot shows how to create resource share.

    Activate and Access Shared Resources from the Trusted Account

    1. Sign in to your AWS trusted account.
    2. From the AWS console, select Oracle Database@AWS, and then select the Activate account button to activate a trusted account and create resource(s) for this account. This screenshot shows the activate button.
    3. Once the activation is complete, the Dashboard button will be enabled. Select the Dashboard button.
    4. From the Oracle Database@AWS dashboard, you can access the shared resources.This screenshot shows how to activate account.
    Note

    • Currently, ODB Network and Exadata Infrastructure creation is only allowed in the buyer account.
    • You can only create ODB peering connection with a ODB Network which is not peered with any existing VPC.

  • Resource sharing is only available through the AWS Console and AWS CLI.

  • There is currently no content for this page. Oracle Database@AWS team intends to add content here, and this placeholder text is provided until that text is added. The Oracle Database@AWS team is excited about future new features, enhancements, and fixes to this product and this accompanying documentation. We strongly recommend you watch this page for those updates.

  • Resource sharing is only available through the AWS Console and AWS CLI.

  • There is currently no content for this page. Oracle Database@AWS team intends to add content here, and this placeholder text is provided until that text is added. The Oracle Database@AWS team is excited about future new features, enhancements, and fixes to this product and this accompanying documentation. We strongly recommend you watch this page for those updates.

What's Next?

You can now create Exadata VM Cluster, Autonomous VM Cluster, Exadata Databases and Autonomous Databases in trusted account using the Exadata Infrastructure created in the owner account.