AWS IAM roles define two types of policies Permissions Policy – Defines what permissions the role is granted Trust Policies – Who can assume the role AWS IAM roles are ALWAYS assumed (you cannot log into an AWS role). When a role is assumed you can specify how long you want the role to be …
AWS Managed Policies – predefined AWS Policies with permissions customers cannot change – but with the right privileges they can be assigned to any principal. Customer Managed Policies – policies created by principals (users etc.) and then assigned to any principal. In-line Policies – per Amazon: An inline policy is a policy that’s embedded in a …
Per AWS IAM Roles FAQ An IAM role is an IAM entity that defines a set of permissions for making AWS service requests. IAM roles are not associated with a specific user or group. Instead, trusted entities assume roles, such as IAM users, applications, or AWS services such as EC2. Steps To Create A New …
A bit complex to implement at this time (03/09/2018) but worth remembering… References: https://cloudonaut.io/passwordless-database-authentication-for-aws-lambda/ https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.IAMDBAuth.html More from LonzoDB on AWS
AWS Authentication and Authorization Summary Authentication – prove you are who you say you are. Authorization – check to what you can or cannot do. Authentication With AWS IAM ( Identity and Access Management ) authentication is performed against principals. Principals can be of three forms. Root AWS User IAM User Roles / Temporary Tokens …