I have a fully working example in my blog, which demonstrates it with a CA you create using openssl, and a step-by-step for everything.
check it out:
https://medium.com/cyberark-engineering/calling-aws-services-from-your-on-premises-servers-using-iam-roles-anywhere-3e335ed648be Answer from royb on repost.aws
AWS
docs.aws.amazon.com › iam roles anywhere › user guide › getting started with iam roles anywhere
Getting started with IAM Roles Anywhere - IAM Roles Anywhere
To use IAM Roles Anywhere for authentication you must first create a trust anchor, and then configure roles, and create a profile through the console.
Help setting up IAM Roles Anywhere
Very excited to read about new AWS Capability; namely, IAM Roles Anywhere. We have a number of on-prem servers, where we would like to copy logs to S3. Now we are using user profiles, which are obviously not the best practice! More on repost.aws
What is IAM Roles Anywhere?
Great find! This must be something they’ll cover at the Re:Inforce conference. Reminds me of ECS Anywhere where AWS is creating capabilities to help facilitate hybrid workloads with components not running in AWS. In this case, it seems to be setting up a system for an on-prem system/workload to use IAM roles without a complex system/architecture in place. This was a pain point previously. This could be promising! More on reddit.com
IAM Roles Anywhere
Anecdotally I have heard that the transition is not really that seamless, requires some additional architectural setup and most I've worked with have stuck with using OIDC/SAML and STS. I think the documentation states that the keyCertSign bit in the keyUsage extension of the certificate used as the trust anchor must be set. This allows IAM Roles Anywhere to use the public key of the certificate provided as the trust anchor to verify the signature in the request that was created by the "end entity" certificate was issued by the same CA. Maybe this links helps a little. https://docs.aws.amazon.com/rolesanywhere/latest/userguide/trust-model.html More on reddit.com
Przykłady użycia funkcji IAM Roles Anywhere : r/aws
Videos
13:22
AWS IAM Roles Anywhere - Introduction & Demo | Amazon Web Services ...
IAM Roles Anywhere: Secure AWS Access - AWS
06:10
AWS IAM Roles Anywhere certificate attribute mapping | Amazon Web ...
30:46
Use IAM Roles Anywhere to reduce the use of static IAM keys - Mike ...
IAM Roles Anywhere: Secure Workload Access - AWS
Amazon Web Services
aws.amazon.com › security, identity, and compliance › aws identity and access management (iam) › aws iam roles anywhere
Extend IAM roles to workloads in multicloud with AWS IAM Roles Anywhere
1 week ago - IAM Roles Anywhere integrates with your existing enterprise PKI so that your non-AWS workloads can use the same IAM policies and IAM roles that you use for workloads running in AWS without having to manage long-term credentials.
AWS
docs.aws.amazon.com › iam roles anywhere › user guide › what is aws identity and access management roles anywhere?
What is AWS Identity and Access Management Roles Anywhere? - IAM Roles Anywhere
To use IAM Roles Anywhere, your workloads must use X.509 certificates issued by your certificate authority (CA). You register the CA with IAM Roles Anywhere as a trust anchor to establish trust between your public-key infrastructure (PKI) and IAM Roles Anywhere.
AWS
docs.aws.amazon.com › iam roles anywhere › api reference › welcome
Welcome - IAM Roles Anywhere
To use IAM Roles Anywhere, your workloads must use X.509 certificates issued by their certificate authority (CA). You register the CA with IAM Roles Anywhere as a trust anchor to establish trust between your public key infrastructure (PKI) and IAM Roles Anywhere.
AWS
docs.aws.amazon.com › none › reference guide › authentication and access using aws sdks and tools › using iam roles anywhere to authenticate aws sdks and tools
Using IAM Roles Anywhere to authenticate AWS SDKs and tools - AWS SDKs and Tools
Learn how to authenticate calls for AWS SDKs and tools by using IAM Roles Anywhere. This uses credential_process in the shared AWS config file.
AWS
docs.aws.amazon.com › iam roles anywhere › user guide › iam roles anywhere cloud security and shared responsibility › identity and access management for iam roles anywhere › how iam roles anywhere works with iam
How IAM Roles Anywhere works with IAM - IAM Roles Anywhere
The Action element of a JSON policy describes the actions that you can use to allow or deny access in a policy. Include actions in a policy to grant permissions to perform the associated operation. To see a list of IAM Roles Anywhere actions, see Actions defined by AWS Identity and Access Management Roles Anywhere in the Service Authorization Reference.
Top answer 1 of 2
3
I have a fully working example in my blog, which demonstrates it with a CA you create using openssl, and a step-by-step for everything.
check it out:
https://medium.com/cyberark-engineering/calling-aws-services-from-your-on-premises-servers-using-iam-roles-anywhere-3e335ed648be
2 of 2
0
Simply put, you need a certificate indicated by `--certificate` to present to AWS in exchange for access keys. This certificate can be the same as a certificate that you see on this page. But the owner of the certificate will have the private key key. This is the parameter `--private-key` that you must point to. Any certificate has a certificate chain with the root CA at the top of the chain. This chain is the certificate bundle that you need to configure when setting up the trust anchor.
AWS
docs.aws.amazon.com › iam roles anywhere › user guide › iam roles anywhere cloud security and shared responsibility › identity and access management for iam roles anywhere
Identity and access management for IAM Roles Anywhere - IAM Roles Anywhere
How to authenticate requests and manage access your IAM Roles Anywhere resources.
AWS
aws.amazon.com › blogs › security › use-iam-roles-anywhere-to-help-you-improve-security-in-on-premises-container-workloads
Use IAM Roles Anywhere to help you improve security in on-premises container workloads | Amazon Web Services
November 29, 2023 - In this blog post, we focus on these key areas to help you set up IAM Roles Anywhere in your own environment: determining whether an existing on-premises public key infrastructure (PKI) can be used with IAM Roles Anywhere, creating the necessary AWS resources, creating an IAM Roles Anywhere enabled Docker image, and using this image to issue AWS Command Line Interface (AWS CLI) commands.
Amazon Web Services
boto3.amazonaws.com › v1 › documentation › api › latest › reference › services › rolesanywhere.html
IAMRolesAnywhere - Boto3 1.42.34 documentation
This guide describes the IAM Roles Anywhere operations that you can call programmatically. For more information about IAM Roles Anywhere, see the IAM Roles Anywhere User Guide. import boto3 client = boto3.client('rolesanywhere')
Hendrikhagen
hendrikhagen.com › blog › iam-roles-anywhere
Using IAM Roles Anywhere to Eliminate Static AWS Credentials
April 24, 2025 - Configure IAM Roles Anywhere - With the PKI in place, we’ll register the CA certificate as a Trust Anchor in IAM Roles Anywhere. We’ll also create a Profile, which specifies the IAM roles that can be assumed and what actions the temporary credentials allow.
Reddit
reddit.com › r/aws › what is iam roles anywhere?
r/aws on Reddit: What is IAM Roles Anywhere?
July 6, 2022 -
Saw these API changes and wondering if anyone knows more about these new apis?
https://awsapichanges.info/archive/changes/8d00b9-rolesanywhere.html
EDIT: the blog post now: https://aws.amazon.com/about-aws/whats-new/2022/07/aws-identity-access-management-iam-roles-anywhere-workloads-outside-aws/
Top answer 1 of 4
15
Great find! This must be something they’ll cover at the Re:Inforce conference. Reminds me of ECS Anywhere where AWS is creating capabilities to help facilitate hybrid workloads with components not running in AWS. In this case, it seems to be setting up a system for an on-prem system/workload to use IAM roles without a complex system/architecture in place. This was a pain point previously. This could be promising!
2 of 4
5
From CreateTrustAnchor in the link you posted: Creates a trust anchor. You establish trust between IAM Roles Anywhere and your certificate authority (CA) by configuring a trust anchor. A Trust Anchor is defined either as a reference to a AWS Certificate Manager Private Certificate Authority (ACM PCA), or by uploading a Certificate Authority (CA) certificate. Your AWS workloads can authenticate with the trust anchor using certificates issued by the trusted Certificate Authority (CA) in exchange for temporary AWS credentials. Sounds like you'll be able to use X.509 certs instead of API keys or STS tokens to assume a role from outside of AWS. Very cool if you already have the necessary cert processes and infrastructure set up.