create_cluster
¶
create_cluster(
hsm_type: HsmType,
subnet_ids: SubnetIds,
*,
config_overrides: Optional[CloudHSMV2ClientConfig] = None,
backup_retention_policy: Optional[BackupRetentionPolicy] = None,
source_backup_id: Optional[BackupArn] = None,
network_type: Optional[NetworkType] = None,
tag_list: Optional[TagList] = None,
mode: Optional[ClusterMode] = None,
) -> CreateClusterResponse
Creates a new CloudHSM cluster.
Cross-account use: Yes. To perform this operation with an CloudHSM backup in a different AWS account, specify the full backup ARN in the value of the SourceBackupId parameter.
Parameters:
-
backup_retention_policy(Optional[BackupRetentionPolicy], default:None) –A policy that defines how the service retains backups.
-
hsm_type(HsmType) –The type of HSM to use in the cluster. The allowed values are
hsm1.mediumandhsm2m.medium. -
source_backup_id(Optional[BackupArn], default:None) –The identifier (ID) or the Amazon Resource Name (ARN) of the cluster backup to restore. Use this value to restore the cluster from a backup instead of creating a new cluster. To find the backup ID or ARN, use DescribeBackups. If using a backup in another account, the full ARN must be supplied.
-
subnet_ids(SubnetIds) –The identifiers (IDs) of the subnets where you are creating the cluster. You must specify at least one subnet. If you specify multiple subnets, they must meet the following criteria:
-
All subnets must be in the same virtual private cloud (VPC).
-
You can specify only one subnet per Availability Zone.
-
-
network_type(Optional[NetworkType], default:None) –The NetworkType to create a cluster with. The allowed values are
IPV4andDUALSTACK. -
tag_list(Optional[TagList], default:None) –Tags to apply to the CloudHSM cluster during creation.
-
mode(Optional[ClusterMode], default:None) –The mode to use in the cluster. The allowed values are
FIPSandNON_FIPS.
Raises:
-
CloudHsmAccessDeniedException–The request was rejected because the requester does not have permission to perform the requested operation.
-
CloudHsmInternalFailureException–The request was rejected because of an CloudHSM internal failure. The request can be retried.
-
CloudHsmInvalidRequestException–The request was rejected because it is not a valid request.
-
CloudHsmResourceNotFoundException–The request was rejected because it refers to a resource that cannot be found.
-
CloudHsmServiceException–The request was rejected because an error occurred.
-
CloudHsmTagException–The request was rejected because of a tagging failure. Verify the tag conditions in all applicable policies, and then retry the request.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_cloudhsm_v2/_services/cloud_hsmv2.py
263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 | |