update_instance
¶
update_instance(
instance_arn: InstanceArn,
*,
config_overrides: Optional[SSOAdminClientConfig] = 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/sso_admin.py
4450 4451 4452 4453 4454 4455 4456 4457 4458 4459 4460 4461 4462 4463 4464 4465 4466 4467 4468 4469 4470 4471 4472 4473 4474 4475 4476 4477 4478 4479 4480 4481 4482 4483 4484 4485 4486 4487 4488 4489 4490 4491 4492 4493 4494 4495 4496 4497 4498 4499 4500 4501 4502 4503 4504 4505 4506 4507 4508 4509 4510 4511 4512 | |