amazon web services - AWS IAM: Using restricted policy while assuming role -


I have several components that have contact with the customer's AWS resources. The customer passes an application wide AWS role in which all components have all necessary permissions and these components consider the role of essential negotiation. The issue with this approach is that a particular component gets unnecessary permissions which are not necessary and are defined for other components.

What I want to do is that a particular component should only have those permissions required by it. Before hand I know what permission is necessary for a particular component, an approach that I can think of, that my main application considers the role and passes an alternative policy document to restrict permissions for a particular component. And then passes the AWS credential to the role that the component holds.

The outcome of this approach is believed to be that the role applicants sent from the main applicant to the ward seem unsafe.

Is there no other way to pass credentials than wire? Applications in the main application have a broad role and know about the necessary permissions for each component.

Thanks


Comments

Popular posts from this blog

java - Can't add JTree to JPanel of a JInternalFrame -

javascript - data.match(var) not working it seems -

javascript - How can I pause a jQuery .each() loop, while waiting for user input? -