Troubleshooting AWS Elemental MediaConnect identity and access
Use the following information to help you diagnose and fix common issues that you might encounter when working with MediaConnect and IAM.
Topics
I am not authorized to perform an action in MediaConnect
If the AWS Management Console tells you that you're not authorized to perform an action, then you must contact your administrator for assistance. Your administrator is the person that provided you with your user name and password.
The following example error occurs when the mateojackson user tries
to use the console to view details about a flow but does not have
mediaconnect:DescribeFlow permissions.
User: arn:aws:iam::123456789012:user/mateojackson is not authorized to perform: mediaconnect:DescribeFlow on resource: myExampleFlow
In this case, Mateo asks his administrator to update his policies to allow him to
access the myExampleFlow resource using the
mediaconnect:DescribeFlow action.
I want to allow people outside of my AWS account to access my MediaConnect resources
You can create a role that users in other accounts or people outside of your organization can use to access your resources. You can specify who is trusted to assume the role. For services that support resource-based policies or access control lists (ACLs), you can use those policies to grant people access to your resources.
To learn more, consult the following:
-
To learn whether MediaConnect supports these features, see How AWS Elemental MediaConnect works with IAM.
-
To learn how to provide access to your resources across AWS accounts that you own, see Providing access to an IAM user in another AWS account that you own in the IAM User Guide.
-
To learn how to provide access to your resources to third-party AWS accounts, see Providing access to AWS accounts owned by third parties in the IAM User Guide.
-
To learn how to provide access through identity federation, see Providing access to externally authenticated users (identity federation) in the IAM User Guide.
-
To learn the difference between using roles and resource-based policies for cross-account access, see How IAM roles differ from resource-based policies in the IAM User Guide.
