lib/aws-sdk-iam/client.rb in aws-sdk-iam-1.75.0 vs lib/aws-sdk-iam/client.rb in aws-sdk-iam-1.76.0
- old
+ new
@@ -1287,10 +1287,12 @@
#
# * A list of client IDs (also known as audiences) that identify the
# application or applications allowed to authenticate using the OIDC
# provider
#
+ # * A list of tags that are attached to the specified IAM OIDC provider
+ #
# * A list of thumbprints of one or more server certificates that the
# IdP uses
#
# You get all of this information from the OIDC IdP you want to use to
# access Amazon Web Services.
@@ -1362,11 +1364,11 @@
# thumbprint string would be the hex-encoded SHA-1 hash value of the
# certificate used by `https://keys.server.example.com.`
#
# For more information about obtaining the OIDC provider thumbprint, see
# [Obtaining the thumbprint for an OpenID Connect provider][1] in the
- # *IAM User Guide*.
+ # *IAM user Guide*.
#
#
#
# [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/identity-providers-oidc-obtain-thumbprint.html
#
@@ -1735,10 +1737,19 @@
#
# IAM user, group, role, and policy names must be unique within the
# account. Names are not distinguished by case. For example, you cannot
# create resources named both "MyResource" and "myresource".
#
+ # This parameter allows (through its [regex pattern][1]) a string of
+ # characters consisting of upper and lowercase alphanumeric characters
+ # with no spaces. You can also include any of the following characters:
+ # \_+=,.@-
+ #
+ #
+ #
+ # [1]: http://wikipedia.org/wiki/regex
+ #
# @option params [required, String] :assume_role_policy_document
# The trust relationship policy document that grants an entity
# permission to assume the role.
#
# In IAM, you must provide a JSON policy that has been converted to a
@@ -2331,12 +2342,12 @@
#
# [1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/Using_Identifiers.html
# [2]: http://wikipedia.org/wiki/regex
#
# @option params [required, String] :virtual_mfa_device_name
- # The name of the virtual MFA device. Use with path to uniquely identify
- # a virtual MFA device.
+ # The name of the virtual MFA device, which must be unique. Use with
+ # path to uniquely identify a virtual MFA device.
#
# This parameter allows (through its [regex pattern][1]) a string of
# characters consisting of upper and lowercase alphanumeric characters
# with no spaces. You can also include any of the following characters:
# \_+=,.@-
@@ -5077,11 +5088,11 @@
# account in your organization. SCPs must be enabled for your
# organization root. You must have permissions to perform this
# operation. For more information, see [Refining permissions using
# service last accessed data][1] in the *IAM User Guide*.
#
- # For each service that principals in an account (root users, IAM users,
+ # For each service that principals in an account (root user, IAM users,
# or IAM roles) could access using SCPs, the operation returns details
# about the most recent access attempt. If there was no attempt, the
# service is listed without details about the most recent attempt to
# access the service. If the operation fails, it returns the reason that
# it failed.
@@ -10984,11 +10995,11 @@
# to aid in organization and search. For example, you could search for
# all resources with the key name *Project* and the value
# *MyImportantProject*. Or search for all resources with the key name
# *Cost Center* and the value *41200*.
#
- # * **Access control** - Include tags in IAM user-based and
+ # * **Access control** - Include tags in IAM identity-based and
# resource-based policies. You can use tags to restrict access to only
# an OIDC provider that has a specified tag attached. For examples of
# policies that show how to use tags to control access, see [Control
# access using IAM tags][2] in the *IAM User Guide*.
#
@@ -11403,11 +11414,11 @@
# to aid in organization and search. For example, you could search for
# all resources with the key name *Project* and the value
# *MyImportantProject*. Or search for all resources with the key name
# *Cost Center* and the value *41200*.
#
- # * **Access control** - Include tags in IAM user-based and
+ # * **Access control** - Include tags in IAM identity-based and
# resource-based policies. You can use tags to restrict access to only
# an IAM requesting user that has a specified tag attached. You can
# also restrict access to only those resources that have a certain tag
# attached. For examples of policies that show how to use tags to
# control access, see [Control access using IAM tags][1] in the *IAM
@@ -13333,10 +13344,10 @@
operation: config.api.operation(operation_name),
client: self,
params: params,
config: config)
context[:gem_name] = 'aws-sdk-iam'
- context[:gem_version] = '1.75.0'
+ context[:gem_version] = '1.76.0'
Seahorse::Client::Request.new(handlers, context)
end
# Polls an API operation until a resource enters a desired state.
#