update_instance
async
¶
update_instance(
instance_arn: InstanceArn,
*,
config_overrides: Optional[AsyncSSOAdminClientConfig] = None,
name: Optional[NameType] = None,
encryption_configuration: Optional[EncryptionConfiguration] = None,
permission_sets_enabled: Optional[bool] = None,
) -> UpdateInstanceResponse
Update the details for the instance of IAM Identity Center that is owned by the Amazon Web Services account.
In a single UpdateInstance request, you can perform only one of the following operations:
-
Update the encryption configuration of the instance by specifying
EncryptionConfiguration. -
Enable permission sets for the instance by specifying
PermissionSetsEnabled.
A request that specifies both EncryptionConfiguration and PermissionSetsEnabled returns a ValidationException. To perform both operations, call UpdateInstance separately for each. The two calls can be made in parallel.
Parameters:
-
name(Optional[NameType], default:None) –Updates the instance name.
-
instance_arn(InstanceArn) –The ARN of the instance of IAM Identity Center under which the operation will run. For more information about ARNs, see Amazon Resource Names (ARNs) and Amazon Web Services Service Namespaces in the Amazon Web Services General Reference.
-
encryption_configuration(Optional[EncryptionConfiguration], default:None) –Specifies the encryption configuration for your IAM Identity Center instance. You can use this to configure customer managed KMS keys or Amazon Web Services owned KMS keys for encrypting your instance data.
-
permission_sets_enabled(Optional[bool], default:None) –Enables permission sets for this Identity Center instance. The only accepted value is
true. After permission sets are enabled, they cannot be disabled.You can't set
EncryptionConfigurationandPermissionSetsEnabledin the same request. To configure both, make two separateUpdateInstancecalls. These calls can be made in parallel.
Raises:
-
AccessDeniedException–You do not have sufficient access to perform this action.
-
ConflictException–Occurs when a conflict with a previous successful write is detected. This generally occurs when the previous write did not have time to propagate to the host serving the current request. A retry (with appropriate backoff logic) is the recommended response to this exception.
-
InternalServerException–The request processing has failed because of an unknown error, exception, or failure with an internal server.
-
ResourceNotFoundException–Indicates that a requested resource is not found.
-
ThrottlingException–Indicates that the principal has crossed the throttling limits of the API operations.
-
ValidationException–The request failed because it contains a syntax error.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_sso_admin/_services/async_sso_admin.py
4517 4518 4519 4520 4521 4522 4523 4524 4525 4526 4527 4528 4529 4530 4531 4532 4533 4534 4535 4536 4537 4538 4539 4540 4541 4542 4543 4544 4545 4546 4547 4548 4549 4550 4551 4552 4553 4554 4555 4556 4557 4558 4559 4560 4561 4562 4563 4564 4565 4566 4567 4568 4569 4570 4571 4572 4573 4574 4575 4576 4577 4578 4579 4580 | |