选择您的 Cookie 首选项

我们使用必要 Cookie 和类似工具提供我们的网站和服务。我们使用性能 Cookie 收集匿名统计数据,以便我们可以了解客户如何使用我们的网站并进行改进。必要 Cookie 无法停用,但您可以单击“自定义”或“拒绝”来拒绝性能 Cookie。

如果您同意,AWS 和经批准的第三方还将使用 Cookie 提供有用的网站功能、记住您的首选项并显示相关内容,包括相关广告。要接受或拒绝所有非必要 Cookie,请单击“接受”或“拒绝”。要做出更详细的选择,请单击“自定义”。

Create non-admin roles

聚焦模式
Create non-admin roles - AWS Elemental MediaConnect
此页面尚未翻译为您的语言。 请求翻译

Users in the Administrators group for an account have access to all AWS services and resources in that account. Granting direct access to all AWS resources goes against the best practice of applying the least privileged permissions to a user. This section describes how you can create roles with permissions that are limited to AWS Elemental MediaConnect. This section also describes how your users can assume that role to grant secure and temporary credentials.

Step 1: Create a non-admin policy

Create two policies for AWS Elemental MediaConnect: one to provide read/write access and one to provide read-only access. Perform these steps one time only for each policy. Later, you will attach these policies to roles. Those roles can then be temporarily assumed by users to grant access to MediaConnect.

To create policies
  1. Use your AWS account ID or account alias, and the credentials for your admin user, to sign in to the IAM console.

  2. In the navigation pane of the console, choose Policies.

  3. On the Policies page, create a policy named MediaConnectAllAccess that allows all actions on all resources in AWS Elemental MediaConnect:

    1. Choose Create policy.

    2. Choose the JSON tab and paste the following policy:

      { "Version": "2012-10-17", "Statement": [ { "Action": [ "mediaconnect:*" ], "Effect": "Allow", "Resource": "*" }, { "Action": [ "ec2:DescribeAvailabilityZones" ], "Effect": "Allow", "Resource": "*" }, { "Action": [ "cloudwatch:GetMetricData" ], "Effect": "Allow", "Resource": "*" }, { "Action": [ "iam:PassRole" ], "Effect": "Allow", "Resource": "*", "Condition": { "StringLike": { "iam:PassedToService": "mediaconnect.amazonaws.com" } } } ] }

      This policy allows all actions on all resources in AWS Elemental MediaConnect.

    3. Choose Next: Tags.

    4. Choose Next: Review.

    5. On the Review and create page, for Policy name, enter MediaConnectAllAccess, and then choose Create policy.

  4. On the Policies page, create a read-only policy named MediaConnectReadOnlyAccess for AWS Elemental MediaConnect:

    1. Choose Create policy.

    2. Choose the JSON tab and paste the following policy:

      { "Version": "2012-10-17", "Statement": [ { "Action": [ "mediaconnect:List*", "mediaconnect:Describe*" ], "Effect": "Allow", "Resource": "*" }, { "Action": [ "ec2:DescribeAvailabilityZones" ], "Effect": "Allow", "Resource": "*" }, { "Action": [ "cloudwatch:GetMetricData" ], "Effect": "Allow", "Resource": "*" }, { "Action": [ "iam:PassRole" ], "Effect": "Allow", "Resource": "*", "Condition": { "StringLike": { "iam:PassedToService": "mediaconnect.amazonaws.com" } } } ] } .
    3. Choose Next: Tags.

    4. Choose Next: Review.

    5. On the Review and create page, for Policy name, enter MediaConnectReadOnlyAccess, and then choose Create policy.

Step 2: Create non-admin roles

You can create a role for each policy and users can assume that role, rather than attaching individual policies to each user. Using the following procedure, create two roles: one for the MediaConnectAllAccess policy and one for the MediaConnectReadOnlyAccess policy.

To create roles
  1. In the navigation pane of the IAM console, choose Roles.

  2. On the Roles page, create an administrator role using the MediaConnectAllAccess policy:

    1. Choose Create role.

    2. In the Select trusted entity section, select AWS account.

    3. In the An AWS account section, select the account with the users that will be assuming this role.

      1. If a third-party will be accessing this role, it is a best practice to select Require external ID. For more information about external IDs, visit: Using an external ID for third-party access in the IAM User Guide.

      2. It is a best practice to require multi-factor authentication (MFA). You can select the checkbox next to Require MFA. For more information about MFA, visit: Multi-factor authentication (MFA) in the IAM User Guide.

    4. Choose Next to move to the Add permissions section.

    5. In the Permissions policy section, choose the MediaConnectAllAccess policy that you created in the procedure in Step 3a: Create a Policy.

    6. Verify that the correct policies are added to this group, and then choose Next.

    7. In the Name, review and create section, name the role MediaConnectAdmins. (Optional) Add a description for the role. Select Create role.

  3. On the Roles page, create an administrator role using the MediaConnectReadOnlyAccess policy:

    1. Choose Create role.

    2. In the Select trusted entity section, select AWS account.

    3. In the An AWS account section, select the account with the users that will be assuming this role.

      1. If a third-party will be accessing this role, it is a best practice to select Require external ID. For more information about external IDs, visit: Using an external ID for third-party access in the IAM User Guide.

      2. It is a best practice to require multi-factor authentication (MFA). You can select the checkbox next to Require MFA. For more information about MFA, visit: Multi-factor authentication (MFA) in the IAM User Guide.

    4. Choose Next to move to the Add permissions section.

    5. In the Permissions policy section, choose the MediaConnectReadOnlyAccess policy that you created in the procedure in Step 3a: Create a Policy.

    6. Verify that the correct policies are added to this group, and then choose Next.

    7. In the Name, review and create section, name the role MediaConnectReaders. (Optional) Add a description for the role. Select Create role.

Step 3: Assume the role

After creating a policy and attaching that policy to a role, your users will need to assume that role to be granted secure and temporary access to MediaConnect.

View the following resources for learning about granting permissions for users to assume the role and how users can switch to the role from the console or AWS CLI.

隐私网站条款Cookie 首选项
© 2024, Amazon Web Services, Inc. 或其附属公司。保留所有权利。