IAM Roles Anywhere now supports modifying the mapping of certificate attributes
AWS Identity and Access Management (IAM) Roles Anywhere now provides the capability to define a set of mapping rules, allowing you to specify which data is extracted from your X.509 end-entity certificates. The data that is mapped is referred to as attributes and used as session tags in the IAM policy condition in order to allow or deny permissions. These attributes can be in one of the subject, issuer, or subject alternative name (SAN) fields of the X.509 certificate.
AWS Identity and Access Management (IAM) Roles Anywhere now provides the capability to define a set of mapping rules, allowing you to specify which data is extracted from your X.509 end-entity certificates. The data that is mapped is referred to as attributes and used as session tags in the IAM policy condition in order to allow or deny permissions. These attributes can be in one of the subject, issuer, or subject alternative name (SAN) fields of the X.509 certificate.
By default, all relative distinguished names (RDNs) from the certificate’s subject and issuer are mapped, along with the first value of the domain name system (DNS), directory name (DN), and uniform resource identifier (URI) from the certificate’s SAN. With this launch, you can now define a set of mapping rules and choose only a subset of those certificate’s attributes that meet your business needs. Thus, reducing the size and the complexity of the tags used for the authorization policies. These mapped attributes are associated with your profile. You can define those mapping rules by using the put-attribute-mapping or delete-attribute-mapping APIs from the IAM Roles Anywhere console, AWS SDKs, and AWS CLI.
This functionality is supported in all AWS Regions where IAM Roles Anywhere is available including the AWS GovCloud (US) Regions. To learn more about this functionality, see the User Guide, API Reference Guide, and AWS CLI Reference.