Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added clarification on instance profile arn #1865

Closed
wants to merge 1 commit into from
Closed

Added clarification on instance profile arn #1865

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions website/source/docs/auth/aws-ec2.html.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,8 @@ backend and associated with various optional restrictions, such as the set
of allowed policies and max TTLs on the generated tokens. Each role can
be specified with the constraints that are to be met during the login. For
example, currently the constraint that is supported is to bind against AMI
ID. A role which is bound to a specific AMI, can only be used for login by
ID or the instance profile.
A role which is bound to a specific AMI, can only be used for login by
those instances that are deployed on the same AMI.

In many cases, an organization will use a "seed AMI" that is specialized after
Expand Down Expand Up @@ -831,7 +832,7 @@ in its identity document to match the one specified by this parameter.
<li>
<span class="param">bound_iam_role_arn</span>
<span class="param-flags">optional</span>
If set, defines a constraint on the EC2 instances that they should be using the IAM Role ARN specified by this parameter.
If set, defines a constraint on the EC2 instances that they should be using the instance profile ARN specified by this parameter.
</li>
</ul>
<ul>
Expand Down