Activates a public third-party extension, making it available for use in stack templates. For more information,\n see Using public\n extensions in the CloudFormation User Guide.
\nOnce you have activated a public third-party extension in your account and Region, use \n SetTypeConfiguration\n to specify configuration properties for the extension. For more information, see Configuring extensions at the account level in the CloudFormation User Guide.
Activates a public third-party extension, making it available for use in stack templates. For more information,\n see Using public\n extensions in the CloudFormation User Guide.
\nOnce you have activated a public third-party extension in your account and Region, use \n SetTypeConfiguration\n to specify configuration properties for the extension. For more\n information, see Configuring extensions at\n the account level in the CloudFormation User Guide.
In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order\n for CloudFormation to create the stack.
\n\n CAPABILITY_IAM and CAPABILITY_NAMED_IAM\n
Some stack templates might include resources that can affect permissions in your Amazon Web Services account;\n for example, by creating new Identity and Access Management (IAM) users. For those stacks, you must explicitly\n acknowledge this by specifying one of these capabilities.
\nThe following IAM resources require you to specify either the CAPABILITY_IAM or\n CAPABILITY_NAMED_IAM capability.
If you have IAM resources, you can specify either capability.
\nIf you have IAM resources with custom names, you must specify\n CAPABILITY_NAMED_IAM.
If you don't specify either of these capabilities, CloudFormation returns an\n InsufficientCapabilities error.
If your stack template contains these resources, we suggest that you review all permissions associated with\n them and edit their permissions if necessary.
\n\n \n AWS::IAM::AccessKey\n \n
\n \n AWS::IAM::Group\n \n
\n \n AWS::IAM::Policy\n \n
\n \n AWS::IAM::Role\n \n
\n \n AWS::IAM::User\n \n
For more information, see Acknowledging IAM resources in\n CloudFormation templates.
\n\n CAPABILITY_AUTO_EXPAND\n
Some template contain macros. Macros perform custom processing on templates; this can include simple actions\n like find-and-replace operations, all the way to extensive transformations of entire templates. Because of this,\n users typically create a change set from the processed template, so that they can review the changes resulting from\n the macros before actually creating the stack. If your stack template contains one or more macros, and you choose\n to create a stack directly from the processed template, without first reviewing the resulting changes in a change\n set, you must acknowledge this capability. This includes the \n AWS::Include\n and \n AWS::Serverless\n transforms, which\n are macros hosted by CloudFormation.
This capacity doesn't apply to creating change sets, and specifying it when creating change sets has no\n effect.
\nIf you want to create a stack from a stack template that contains macros and nested\n stacks, you must create or update the stack directly from the template using the CreateStack or\n UpdateStack action, and specifying this capability.
\nFor more information about macros, see Using CloudFormation macros to perform custom processing on\n templates.
\nOnly one of the Capabilities and ResourceType parameters can be specified.
In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order\n for CloudFormation to create the stack.
\n\n CAPABILITY_IAM and CAPABILITY_NAMED_IAM\n
Some stack templates might include resources that can affect permissions in your Amazon Web Services account;\n for example, by creating new Identity and Access Management (IAM) users. For those stacks, you must explicitly\n acknowledge this by specifying one of these capabilities.
\nThe following IAM resources require you to specify either the CAPABILITY_IAM or\n CAPABILITY_NAMED_IAM capability.
If you have IAM resources, you can specify either capability.
\nIf you have IAM resources with custom names, you must specify\n CAPABILITY_NAMED_IAM.
If you don't specify either of these capabilities, CloudFormation returns an\n InsufficientCapabilities error.
If your stack template contains these resources, we suggest that you review all permissions associated with\n them and edit their permissions if necessary.
\n\n \n AWS::IAM::AccessKey\n \n
\n \n AWS::IAM::Group\n \n
\n \n AWS::IAM::Policy\n \n
\n \n AWS::IAM::Role\n \n
\n \n AWS::IAM::User\n \n
For more information, see Acknowledging IAM resources in\n CloudFormation templates.
\n\n CAPABILITY_AUTO_EXPAND\n
Some template contain macros. Macros perform custom processing on templates; this can include simple actions\n like find-and-replace operations, all the way to extensive transformations of entire templates. Because of this,\n users typically create a change set from the processed template, so that they can review the changes resulting from\n the macros before actually creating the stack. If your stack template contains one or more macros, and you choose\n to create a stack directly from the processed template, without first reviewing the resulting changes in a change\n set, you must acknowledge this capability. This includes the \n AWS::Include\n and \n AWS::Serverless\n \n transforms, which are macros hosted by CloudFormation.
This capacity doesn't apply to creating change sets, and specifying it when creating change sets has no\n effect.
\nIf you want to create a stack from a stack template that contains macros and nested\n stacks, you must create or update the stack directly from the template using the CreateStack or\n UpdateStack action, and specifying this capability.
\nFor more information about macros, see Using CloudFormation macros to perform custom processing on\n templates.
\nOnly one of the Capabilities and ResourceType parameters can be specified.
Determines what action will be taken if stack creation fails. If this parameter is specified, the\n DisableRollback parameter to the \n ExecuteChangeSet\n API operation must not\n be specified. This must be one of these values:
\n DELETE - Deletes the change set if the stack creation fails. This is only valid when the\n ChangeSetType parameter is set to CREATE. If the deletion of the stack fails, the status\n of the stack is DELETE_FAILED.
\n DO_NOTHING - if the stack creation fails, do nothing. This is equivalent to specifying\n true for the DisableRollback parameter to the \n ExecuteChangeSet\n API\n operation.
\n ROLLBACK - if the stack creation fails, roll back the stack. This is equivalent to specifying\n false for the DisableRollback parameter to the \n ExecuteChangeSet\n API\n operation.
For nested stacks, when the OnStackFailure parameter is set to DELETE for the change\n set for the parent stack, any failure in a child stack will cause the parent stack creation to fail and all stacks to\n be deleted.
Determines what action will be taken if stack creation fails. If this parameter is specified, the\n DisableRollback parameter to the \n ExecuteChangeSet\n API\n operation must not be specified. This must be one of these values:
\n DELETE - Deletes the change set if the stack creation fails. This is only valid when the\n ChangeSetType parameter is set to CREATE. If the deletion of the stack fails, the status\n of the stack is DELETE_FAILED.
\n DO_NOTHING - if the stack creation fails, do nothing. This is equivalent to specifying\n true for the DisableRollback parameter to the \n ExecuteChangeSet\n API\n operation.
\n ROLLBACK - if the stack creation fails, roll back the stack. This is equivalent to specifying\n false for the DisableRollback parameter to the \n ExecuteChangeSet\n API\n operation.
For nested stacks, when the OnStackFailure parameter is set to DELETE for the change\n set for the parent stack, any failure in a child stack will cause the parent stack creation to fail and all stacks to\n be deleted.
A list of Parameter structures that specify input parameters for the stack. For more information,\n see the \n Parameter\n \n data type.
A list of Parameter structures that specify input parameters for the stack. For more information,\n see the \n Parameter\n data type.
In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order\n for CloudFormation to create the stack.
\n\n CAPABILITY_IAM and CAPABILITY_NAMED_IAM\n
Some stack templates might include resources that can affect permissions in your Amazon Web Services account;\n for example, by creating new Identity and Access Management (IAM) users. For those stacks, you must explicitly\n acknowledge this by specifying one of these capabilities.
\nThe following IAM resources require you to specify either the CAPABILITY_IAM or\n CAPABILITY_NAMED_IAM capability.
If you have IAM resources, you can specify either capability.
\nIf you have IAM resources with custom names, you must specify\n CAPABILITY_NAMED_IAM.
If you don't specify either of these capabilities, CloudFormation returns an\n InsufficientCapabilities error.
If your stack template contains these resources, we recommend that you review all permissions associated with\n them and edit their permissions if necessary.
\n\n \n AWS::IAM::Group\n \n
\n \n AWS::IAM::Policy\n \n
\n \n AWS::IAM::Role\n \n
\n \n AWS::IAM::User\n \n
For more information, see Acknowledging IAM Resources in\n CloudFormation Templates.
\n\n CAPABILITY_AUTO_EXPAND\n
Some template contain macros. Macros perform custom processing on templates; this can include simple actions\n like find-and-replace operations, all the way to extensive transformations of entire templates. Because of this,\n users typically create a change set from the processed template, so that they can review the changes resulting from\n the macros before actually creating the stack. If your stack template contains one or more macros, and you choose\n to create a stack directly from the processed template, without first reviewing the resulting changes in a change\n set, you must acknowledge this capability. This includes the \n AWS::Include\n and \n AWS::Serverless\n transforms, which\n are macros hosted by CloudFormation.
If you want to create a stack from a stack template that contains macros and nested\n stacks, you must create the stack directly from the template using this capability.
\nYou should only create stacks directly from a stack template that contains macros if you know what processing\n the macro performs.
\nEach macro relies on an underlying Lambda service function for processing stack templates. Be\n aware that the Lambda function owner can update the function operation without CloudFormation being\n notified.
\nFor more information, see Using CloudFormation macros to perform custom processing\n on templates.
\nOnly one of the Capabilities and ResourceType parameters can be specified.
In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order\n for CloudFormation to create the stack.
\n\n CAPABILITY_IAM and CAPABILITY_NAMED_IAM\n
Some stack templates might include resources that can affect permissions in your Amazon Web Services account;\n for example, by creating new Identity and Access Management (IAM) users. For those stacks, you must explicitly\n acknowledge this by specifying one of these capabilities.
\nThe following IAM resources require you to specify either the CAPABILITY_IAM or\n CAPABILITY_NAMED_IAM capability.
If you have IAM resources, you can specify either capability.
\nIf you have IAM resources with custom names, you must specify\n CAPABILITY_NAMED_IAM.
If you don't specify either of these capabilities, CloudFormation returns an\n InsufficientCapabilities error.
If your stack template contains these resources, we recommend that you review all permissions associated with\n them and edit their permissions if necessary.
\n\n \n AWS::IAM::AccessKey\n \n
\n \n AWS::IAM::Group\n \n
\n \n AWS::IAM::Policy\n \n
\n \n AWS::IAM::Role\n \n
\n \n AWS::IAM::User\n \n
For more information, see Acknowledging IAM Resources in\n CloudFormation Templates.
\n\n CAPABILITY_AUTO_EXPAND\n
Some template contain macros. Macros perform custom processing on templates; this can include simple actions\n like find-and-replace operations, all the way to extensive transformations of entire templates. Because of this,\n users typically create a change set from the processed template, so that they can review the changes resulting from\n the macros before actually creating the stack. If your stack template contains one or more macros, and you choose\n to create a stack directly from the processed template, without first reviewing the resulting changes in a change\n set, you must acknowledge this capability. This includes the \n AWS::Include\n and \n AWS::Serverless\n \n transforms, which are macros hosted by CloudFormation.
If you want to create a stack from a stack template that contains macros and nested\n stacks, you must create the stack directly from the template using this capability.
\nYou should only create stacks directly from a stack template that contains macros if you know what processing\n the macro performs.
\nEach macro relies on an underlying Lambda service function for processing stack templates. Be\n aware that the Lambda function owner can update the function operation without CloudFormation being\n notified.
\nFor more information, see Using CloudFormation macros to perform custom processing\n on templates.
\nOnly one of the Capabilities and ResourceType parameters can be specified.
A list of stack set parameters whose values you want to override in the selected stack instances.
\nAny overridden parameter values will be applied to all stack instances in the specified accounts and Amazon Web Services Regions. When specifying parameters and their values, be aware of how CloudFormation sets parameter values\n during stack instance operations:
\nTo override the current value for a parameter, include the parameter and specify its value.
\nTo leave an overridden parameter set to its present value, include the parameter and specify\n UsePreviousValue as true. (You can't specify both a value and set\n UsePreviousValue to true.)
To set an overridden parameter back to the value specified in the stack set, specify a parameter list but\n don't include the parameter in the list.
\nTo leave all parameters set to their present values, don't specify this property at all.
\nDuring stack set updates, any parameter values overridden for a stack instance aren't updated, but retain their\n overridden value.
\nYou can only override the parameter values that are specified in the stack set; to add or\n delete a parameter itself, use \n UpdateStackSet\n to update the stack set\n template.
A list of stack set parameters whose values you want to override in the selected stack instances.
\nAny overridden parameter values will be applied to all stack instances in the specified accounts and Amazon Web Services Regions. When specifying parameters and their values, be aware of how CloudFormation sets parameter values\n during stack instance operations:
\nTo override the current value for a parameter, include the parameter and specify its value.
\nTo leave an overridden parameter set to its present value, include the parameter and specify\n UsePreviousValue as true. (You can't specify both a value and set\n UsePreviousValue to true.)
To set an overridden parameter back to the value specified in the stack set, specify a parameter list but\n don't include the parameter in the list.
\nTo leave all parameters set to their present values, don't specify this property at all.
\nDuring stack set updates, any parameter values overridden for a stack instance aren't updated, but retain their\n overridden value.
\nYou can only override the parameter values that are specified in the stack set; to add or\n delete a parameter itself, use \n UpdateStackSet\n to update the\n stack set template.
In some cases, you must explicitly acknowledge that your stack set template contains certain capabilities in\n order for CloudFormation to create the stack set and related stack instances.
\n\n CAPABILITY_IAM and CAPABILITY_NAMED_IAM\n
Some stack templates might include resources that can affect permissions in your Amazon Web Services account;\n for example, by creating new Identity and Access Management (IAM) users. For those stack sets, you must explicitly\n acknowledge this by specifying one of these capabilities.
\nThe following IAM resources require you to specify either the CAPABILITY_IAM or\n CAPABILITY_NAMED_IAM capability.
If you have IAM resources, you can specify either capability.
\nIf you have IAM resources with custom names, you must specify\n CAPABILITY_NAMED_IAM.
If you don't specify either of these capabilities, CloudFormation returns an\n InsufficientCapabilities error.
If your stack template contains these resources, we recommend that you review all permissions associated with\n them and edit their permissions if necessary.
\n\n \n AWS::IAM::AccessKey\n \n
\n \n AWS::IAM::Group\n \n
\n \n AWS::IAM::Policy\n \n
\n \n AWS::IAM::Role\n \n
\n \n AWS::IAM::User\n \n
For more information, see Acknowledging IAM Resources in\n CloudFormation Templates.
\n\n CAPABILITY_AUTO_EXPAND\n
Some templates reference macros. If your stack set template references one or more macros, you must create the\n stack set directly from the processed template, without first reviewing the resulting changes in a change set. To\n create the stack set directly, you must acknowledge this capability. For more information, see Using CloudFormation Macros to\n Perform Custom Processing on Templates.
\nStack sets with service-managed permissions don't currently support the use of macros in templates. (This\n includes the \n AWS::Include\n and \n AWS::Serverless\n transforms, which\n are macros hosted by CloudFormation.) Even if you specify this capability for a stack set with service-managed permissions,\n if you reference a macro in your template the stack set operation will fail.
In some cases, you must explicitly acknowledge that your stack set template contains certain capabilities in\n order for CloudFormation to create the stack set and related stack instances.
\n\n CAPABILITY_IAM and CAPABILITY_NAMED_IAM\n
Some stack templates might include resources that can affect permissions in your Amazon Web Services account;\n for example, by creating new Identity and Access Management (IAM) users. For those stack sets, you must explicitly\n acknowledge this by specifying one of these capabilities.
\nThe following IAM resources require you to specify either the CAPABILITY_IAM or\n CAPABILITY_NAMED_IAM capability.
If you have IAM resources, you can specify either capability.
\nIf you have IAM resources with custom names, you must specify\n CAPABILITY_NAMED_IAM.
If you don't specify either of these capabilities, CloudFormation returns an\n InsufficientCapabilities error.
If your stack template contains these resources, we recommend that you review all permissions associated with\n them and edit their permissions if necessary.
\n\n \n AWS::IAM::AccessKey\n \n
\n \n AWS::IAM::Group\n \n
\n \n AWS::IAM::Policy\n \n
\n \n AWS::IAM::Role\n \n
\n \n AWS::IAM::User\n \n
For more information, see Acknowledging IAM Resources in\n CloudFormation Templates.
\n\n CAPABILITY_AUTO_EXPAND\n
Some templates reference macros. If your stack set template references one or more macros, you must create the\n stack set directly from the processed template, without first reviewing the resulting changes in a change set. To\n create the stack set directly, you must acknowledge this capability. For more information, see Using CloudFormation Macros to\n Perform Custom Processing on Templates.
\nStack sets with service-managed permissions don't currently support the use of macros in templates. (This\n includes the \n AWS::Include\n and \n AWS::Serverless\n \n transforms, which are macros hosted by CloudFormation.) Even if you specify this capability for a stack set with\n service-managed permissions, if you reference a macro in your template the stack set operation will fail.
Determines what action will be taken if stack creation fails. When this parameter is specified, the\n DisableRollback parameter to the \n ExecuteChangeSet\n API operation must not\n be specified. This must be one of these values:
\n DELETE - Deletes the change set if the stack creation fails. This is only valid when the\n ChangeSetType parameter is set to CREATE. If the deletion of the stack fails, the status\n of the stack is DELETE_FAILED.
\n DO_NOTHING - if the stack creation fails, do nothing. This is equivalent to specifying\n true for the DisableRollback parameter to the \n ExecuteChangeSet\n API\n operation.
\n ROLLBACK - if the stack creation fails, roll back the stack. This is equivalent to specifying\n false for the DisableRollback parameter to the \n ExecuteChangeSet\n API\n operation.
Determines what action will be taken if stack creation fails. When this parameter is specified, the\n DisableRollback parameter to the \n ExecuteChangeSet\n API\n operation must not be specified. This must be one of these values:
\n DELETE - Deletes the change set if the stack creation fails. This is only valid when the\n ChangeSetType parameter is set to CREATE. If the deletion of the stack fails, the status\n of the stack is DELETE_FAILED.
\n DO_NOTHING - if the stack creation fails, do nothing. This is equivalent to specifying\n true for the DisableRollback parameter to the \n ExecuteChangeSet\n API\n operation.
\n ROLLBACK - if the stack creation fails, roll back the stack. This is equivalent to specifying\n false for the DisableRollback parameter to the \n ExecuteChangeSet\n API\n operation.
A JSON string that represent the current configuration data for the extension in this account and Region.
\nTo set the configuration data for an extension, use \n SetTypeConfiguration\n . For more\n information, see Configuring extensions at\n the account level in the CloudFormation User Guide.
A JSON string that represent the current configuration data for the extension in this account and Region.
\nTo set the configuration data for an extension, use \n SetTypeConfiguration\n .\n For more information, see Configuring extensions at\n the account level in the CloudFormation User Guide.
Preserves the state of previously provisioned resources when an operation fails. This parameter can't be\n specified when the OnStackFailure parameter to the \n CreateChangeSet\n API operation was\n specified.
\n True - if the stack creation fails, do nothing. This is equivalent to specifying\n DO_NOTHING for the OnStackFailure parameter to the \n CreateChangeSet\n API operation.
\n False - if the stack creation fails, roll back the stack. This is equivalent to specifying\n ROLLBACK for the OnStackFailure parameter to the \n CreateChangeSet\n API operation.
Default: True\n
Preserves the state of previously provisioned resources when an operation fails. This parameter can't be\n specified when the OnStackFailure parameter to the \n CreateChangeSet\n API\n operation was specified.
\n True - if the stack creation fails, do nothing. This is equivalent to specifying\n DO_NOTHING for the OnStackFailure parameter to the \n CreateChangeSet\n API\n operation.
\n False - if the stack creation fails, roll back the stack. This is equivalent to specifying\n ROLLBACK for the OnStackFailure parameter to the \n CreateChangeSet\n API\n operation.
Default: True\n
Returns summary information about deployment targets for a stack set.
" + } + }, + "com.amazonaws.cloudformation#ListStackSetAutoDeploymentTargetsInput": { + "type": "structure", + "members": { + "StackSetName": { + "target": "com.amazonaws.cloudformation#StackSetNameOrId", + "traits": { + "smithy.api#clientOptional": {}, + "smithy.api#documentation": "The name or unique ID of the stack set that you want to get automatic deployment targets for.
", + "smithy.api#required": {} + } + }, + "NextToken": { + "target": "com.amazonaws.cloudformation#NextToken", + "traits": { + "smithy.api#documentation": "A string that identifies the next page of stack set deployment targets that you want to retrieve.
" + } + }, + "MaxResults": { + "target": "com.amazonaws.cloudformation#MaxResults", + "traits": { + "smithy.api#documentation": "The maximum number of results to be returned with a single call. If the number of available results exceeds this\n maximum, the response includes a NextToken value that you can assign to the NextToken\n request parameter to get the next set of results.
Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
\nBy default, SELF is specified. Use SELF for StackSets with self-managed\n permissions.
If you are signed in to the management account, specify SELF.
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated\n administrator in the CloudFormation User Guide.
\nAn array of summaries of the deployment targets for the stack set.
" + } + }, + "NextToken": { + "target": "com.amazonaws.cloudformation#NextToken", + "traits": { + "smithy.api#documentation": "If the request doesn't return all the remaining results, NextToken is set to a token. To retrieve\n the next set of results, call \n ListStackSetAutoDeploymentTargets\n again and use that value for the NextToken\n parameter. If the request returns all results, NextToken is set to an empty string.
Registers an extension with the CloudFormation service. Registering an extension makes it available for use in\n CloudFormation templates in your Amazon Web Services account, and includes:
\nValidating the extension schema.
\nDetermining which handlers, if any, have been specified for the extension.
\nMaking the extension available for use in your account.
\nFor more information about how to develop extensions and ready them for registration, see Creating Resource\n Providers in the CloudFormation CLI User Guide.
\nYou can have a maximum of 50 resource extension versions registered at a time. This maximum is per account and\n per Region. Use \n DeregisterType\n to deregister specific extension versions if necessary.
Once you have initiated a registration request using RegisterType, you can use DescribeTypeRegistration to monitor the progress of the registration request.
\nOnce you have registered a private extension in your account and Region, use \n SetTypeConfiguration\n to specify\n configuration properties for the extension. For more information, see Configuring extensions at\n the account level in the CloudFormation User Guide.
Registers an extension with the CloudFormation service. Registering an extension makes it available for use in\n CloudFormation templates in your Amazon Web Services account, and includes:
\nValidating the extension schema.
\nDetermining which handlers, if any, have been specified for the extension.
\nMaking the extension available for use in your account.
\nFor more information about how to develop extensions and ready them for registration, see Creating Resource\n Providers in the CloudFormation CLI User Guide.
\nYou can have a maximum of 50 resource extension versions registered at a time. This maximum is per account and\n per Region. Use \n DeregisterType\n to deregister specific extension versions if necessary.
Once you have initiated a registration request using RegisterType, you can use DescribeTypeRegistration to monitor the progress of the registration request.
\nOnce you have registered a private extension in your account and Region, use \n SetTypeConfiguration\n \n to specify configuration properties for the extension. For more information, see Configuring extensions at\n the account level in the CloudFormation User Guide.
The resource type of the rollback trigger. Specify either \n AWS::CloudWatch::Alarm\n or \n AWS::CloudWatch::CompositeAlarm\n resource types.
The resource type of the rollback trigger. Specify either \n AWS::CloudWatch::Alarm\n or\n \n AWS::CloudWatch::CompositeAlarm\n resource types.
The configuration data for the extension, in this account and Region.
\nThe configuration data must be formatted as JSON, and validate against the schema returned in the\n ConfigurationSchema response element of \n DescribeType\n . For more information, see\n Defining\n account-level configuration data for an extension in the CloudFormation CLI User\n Guide.
The configuration data for the extension, in this account and Region.
\nThe configuration data must be formatted as JSON, and validate against the schema returned in the\n ConfigurationSchema response element of \n DescribeType\n . For more\n information, see Defining\n account-level configuration data for an extension in the CloudFormation CLI User\n Guide.
The status of the stack instance, in terms of its synchronization with its associated stack set.
\n\n INOPERABLE: A DeleteStackInstances operation has failed and left the stack in an\n unstable state. Stacks in this state are excluded from further UpdateStackSet operations. You might\n need to perform a DeleteStackInstances operation, with RetainStacks set to\n true, to delete the stack instance, and then delete the stack manually. INOPERABLE can be\n returned here when the cause is a failed import. If it's due to a failed import, the operation can be retried once\n the failures are fixed. To see if this is due to a failed import, look at the DetailedStatus member in\n the StackInstanceSummary member that is a peer to this Status\n member.
\n OUTDATED: The stack isn't currently up to date with the stack set because:
The associated stack failed during a CreateStackSet or UpdateStackSet\n operation.
The stack was part of a CreateStackSet or UpdateStackSet operation that failed or\n was stopped before the stack was created or updated.
\n CURRENT: The stack is currently up to date with the stack set.
The status of the stack instance, in terms of its synchronization with its associated stack set.
\n\n INOPERABLE: A DeleteStackInstances operation has failed and left the stack in an\n unstable state. Stacks in this state are excluded from further UpdateStackSet operations. You might\n need to perform a DeleteStackInstances operation, with RetainStacks set to\n true, to delete the stack instance, and then delete the stack\n manually. INOPERABLE can be\n returned here when the cause is a failed import. If it's due to a failed import, the operation can be retried once\n the failures are fixed. To see if this is due to a failed import, look at the DetailedStatus member in\n the StackInstanceSummary member that is a peer to this Status\n member.
\n OUTDATED: The stack isn't currently up to date with the stack set because:
The associated stack failed during a CreateStackSet or UpdateStackSet\n operation.
The stack was part of a CreateStackSet or UpdateStackSet operation that failed or\n was stopped before the stack was created or updated.
\n CURRENT: The stack is currently up to date with the stack set.
\n CANCELLED: The operation in the specified account and Region has been canceled. This is either\n because a user has stopped the stack set operation, or because the failure tolerance of the stack set operation has\n been exceeded.
\n FAILED: The operation in the specified account and Region failed. If the stack set operation\n fails in enough accounts within a Region, the failure tolerance for the stack set operation as a whole might be\n exceeded.
\n INOPERABLE: A DeleteStackInstances operation has failed and left the stack in an\n unstable state. Stacks in this state are excluded from further UpdateStackSet operations. You might\n need to perform a DeleteStackInstances operation, with RetainStacks set to\n true, to delete the stack instance, and then delete the stack manually.
\n PENDING: The operation in the specified account and Region has yet to start.
\n RUNNING: The operation in the specified account and Region is currently in progress.
\n SKIPPED_SUSPENDED_ACCOUNT: The operation in the specified account and Region has been skipped\n because the account was suspended at the time of the operation.
\n SUCCEEDED: The operation in the specified account and Region completed successfully.
\n CANCELLED: The operation in the specified account and Region has been canceled. This is either\n because a user has stopped the stack set operation, or because the failure tolerance of the stack set operation has\n been exceeded.
\n FAILED: The operation in the specified account and Region failed. If the stack set operation\n fails in enough accounts within a Region, the failure tolerance for the stack set operation as a whole might be\n exceeded.
\n FAILED_IMPORT: The import of the stack instance in the specified account and Region failed and\n left the stack in an unstable state. Once the issues causing the failure are fixed, the import operation can be\n retried. If enough stack set operations fail in enough accounts within a Region, the failure tolerance for the\n stack set operation as a whole might be exceeded.
\n INOPERABLE: A DeleteStackInstances operation has failed and left the stack in an\n unstable state. Stacks in this state are excluded from further UpdateStackSet operations. You might\n need to perform a DeleteStackInstances operation, with RetainStacks set to\n true, to delete the stack instance, and then delete the stack manually.
\n PENDING: The operation in the specified account and Region has yet to start.
\n RUNNING: The operation in the specified account and Region is currently in progress.
\n SKIPPED_SUSPENDED_ACCOUNT: The operation in the specified account and Region has been skipped\n because the account was suspended at the time of the operation.
\n SUCCEEDED: The operation in the specified account and Region completed successfully.
The status of the stack instance, in terms of its synchronization with its associated stack set.
\n\n INOPERABLE: A DeleteStackInstances operation has failed and left the stack in an\n unstable state. Stacks in this state are excluded from further UpdateStackSet operations. You might\n need to perform a DeleteStackInstances operation, with RetainStacks set to\n true, to delete the stack instance, and then delete the stack manually. INOPERABLE can be\n returned here when the cause is a failed import. If it's due to a failed import, the operation can be retried once\n the failures are fixed. To see if this is due to a failed import, call the DescribeStackInstance\n API operation, look at the DetailedStatus member returned in the StackInstanceSummary\n member.
\n OUTDATED: The stack isn't currently up to date with the stack set because:
The associated stack failed during a CreateStackSet or UpdateStackSet\n operation.
The stack was part of a CreateStackSet or UpdateStackSet operation that failed or\n was stopped before the stack was created or updated.
\n CURRENT: The stack is currently up to date with the stack set.
The status of the stack instance, in terms of its synchronization with its associated stack set.
\n\n INOPERABLE: A DeleteStackInstances operation has failed and left the stack in an\n unstable state. Stacks in this state are excluded from further UpdateStackSet operations. You might\n need to perform a DeleteStackInstances operation, with RetainStacks set to\n true, to delete the stack instance, and then delete the stack\n manually. INOPERABLE can be\n returned here when the cause is a failed import. If it's due to a failed import, the operation can be retried once\n the failures are fixed. To see if this is due to a failed import, call the DescribeStackInstance\n API operation, look at the DetailedStatus member returned in the StackInstanceSummary\n member.
\n OUTDATED: The stack isn't currently up to date with the stack set because:
The associated stack failed during a CreateStackSet or UpdateStackSet\n operation.
The stack was part of a CreateStackSet or UpdateStackSet operation that failed or\n was stopped before the stack was created or updated.
\n CURRENT: The stack is currently up to date with the stack set.
The organization root ID or organizational unit (OU) IDs where the stack set is targeted.
" + } + }, + "Regions": { + "target": "com.amazonaws.cloudformation#RegionList", + "traits": { + "smithy.api#documentation": "The list of Regions targeted for this organization or OU.
" + } + } + }, + "traits": { + "smithy.api#documentation": "One of the targets for the stack set. Returned by the \n ListStackSetAutoDeploymentTargets\n API operation.
Tests a registered extension to make sure it meets all necessary requirements for being published in the CloudFormation registry.
\nFor resource types, this includes passing all contracts tests defined for the type.
\nFor modules, this includes determining if the module's model meets all necessary requirements.
\nFor more information, see Testing your public\n extension prior to publishing in the CloudFormation CLI User Guide.
\nIf you don't specify a version, CloudFormation uses the default version of the extension in your account and Region\n for testing.
\nTo perform testing, CloudFormation assumes the execution role specified when the type was registered. For more\n information, see \n RegisterType\n .
Once you've initiated testing on an extension using TestType, you can pass the returned\n TypeVersionArn into \n DescribeType\n to monitor the current test\n status and test status description for the extension.
An extension must have a test status of PASSED before it can be published. For more information,\n see Publishing\n extensions to make them available for public use in the CloudFormation CLI User\n Guide.
Tests a registered extension to make sure it meets all necessary requirements for being published in the CloudFormation registry.
\nFor resource types, this includes passing all contracts tests defined for the type.
\nFor modules, this includes determining if the module's model meets all necessary requirements.
\nFor more information, see Testing your public\n extension prior to publishing in the CloudFormation CLI User Guide.
\nIf you don't specify a version, CloudFormation uses the default version of the extension in your account and Region\n for testing.
\nTo perform testing, CloudFormation assumes the execution role specified when the type was registered. For more\n information, see \n RegisterType\n .
Once you've initiated testing on an extension using TestType, you can pass the returned\n TypeVersionArn into \n DescribeType\n to monitor the\n current test status and test status description for the extension.
An extension must have a test status of PASSED before it can be published. For more information,\n see Publishing\n extensions to make them available for public use in the CloudFormation CLI User\n Guide.
A list of Parameter structures that specify input parameters for the stack. For more information,\n see the \n Parameter\n \n data type.
A list of Parameter structures that specify input parameters for the stack. For more information,\n see the \n Parameter\n data type.
In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order\n for CloudFormation to update the stack.
\n\n CAPABILITY_IAM and CAPABILITY_NAMED_IAM\n
Some stack templates might include resources that can affect permissions in your Amazon Web Services account;\n for example, by creating new Identity and Access Management (IAM) users. For those stacks, you must explicitly\n acknowledge this by specifying one of these capabilities.
\nThe following IAM resources require you to specify either the CAPABILITY_IAM or\n CAPABILITY_NAMED_IAM capability.
If you have IAM resources, you can specify either capability.
\nIf you have IAM resources with custom names, you must specify\n CAPABILITY_NAMED_IAM.
If you don't specify either of these capabilities, CloudFormation returns an\n InsufficientCapabilities error.
If your stack template contains these resources, we suggest that you review all permissions associated with\n them and edit their permissions if necessary.
\n\n \n AWS::IAM::AccessKey\n \n
\n \n AWS::IAM::Group\n \n
\n \n \n AWS::IAM::Policy\n \n
\n \n AWS::IAM::Role\n \n
\n \n AWS::IAM::User\n \n
For more information, see Acknowledging IAM Resources in\n CloudFormation Templates.
\n\n CAPABILITY_AUTO_EXPAND\n
Some template contain macros. Macros perform custom processing on templates; this can include simple actions\n like find-and-replace operations, all the way to extensive transformations of entire templates. Because of this,\n users typically create a change set from the processed template, so that they can review the changes resulting from\n the macros before actually updating the stack. If your stack template contains one or more macros, and you choose\n to update a stack directly from the processed template, without first reviewing the resulting changes in a change\n set, you must acknowledge this capability. This includes the \n AWS::Include\n and \n AWS::Serverless\n transforms, which\n are macros hosted by CloudFormation.
If you want to update a stack from a stack template that contains macros and nested\n stacks, you must update the stack directly from the template using this capability.
\nYou should only update stacks directly from a stack template that contains macros if you know what processing\n the macro performs.
\nEach macro relies on an underlying Lambda service function for processing stack templates. Be\n aware that the Lambda function owner can update the function operation without CloudFormation being\n notified.
\nFor more information, see Using CloudFormation Macros to Perform Custom Processing\n on Templates.
\nOnly one of the Capabilities and ResourceType parameters can be specified.
In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order\n for CloudFormation to update the stack.
\n\n CAPABILITY_IAM and CAPABILITY_NAMED_IAM\n
Some stack templates might include resources that can affect permissions in your Amazon Web Services account;\n for example, by creating new Identity and Access Management (IAM) users. For those stacks, you must explicitly\n acknowledge this by specifying one of these capabilities.
\nThe following IAM resources require you to specify either the CAPABILITY_IAM or\n CAPABILITY_NAMED_IAM capability.
If you have IAM resources, you can specify either capability.
\nIf you have IAM resources with custom names, you must specify\n CAPABILITY_NAMED_IAM.
If you don't specify either of these capabilities, CloudFormation returns an\n InsufficientCapabilities error.
If your stack template contains these resources, we suggest that you review all permissions associated with\n them and edit their permissions if necessary.
\n\n \n AWS::IAM::AccessKey\n \n
\n \n AWS::IAM::Group\n \n
\n \n \n AWS::IAM::Policy\n \n
\n \n AWS::IAM::Role\n \n
\n \n AWS::IAM::User\n \n
For more information, see Acknowledging IAM Resources in\n CloudFormation Templates.
\n\n CAPABILITY_AUTO_EXPAND\n
Some template contain macros. Macros perform custom processing on templates; this can include simple actions\n like find-and-replace operations, all the way to extensive transformations of entire templates. Because of this,\n users typically create a change set from the processed template, so that they can review the changes resulting from\n the macros before actually updating the stack. If your stack template contains one or more macros, and you choose\n to update a stack directly from the processed template, without first reviewing the resulting changes in a change\n set, you must acknowledge this capability. This includes the \n AWS::Include\n and \n AWS::Serverless\n \n transforms, which are macros hosted by CloudFormation.
If you want to update a stack from a stack template that contains macros and nested\n stacks, you must update the stack directly from the template using this capability.
\nYou should only update stacks directly from a stack template that contains macros if you know what processing\n the macro performs.
\nEach macro relies on an underlying Lambda service function for processing stack templates. Be\n aware that the Lambda function owner can update the function operation without CloudFormation being\n notified.
\nFor more information, see Using CloudFormation Macros to Perform Custom Processing\n on Templates.
\nOnly one of the Capabilities and ResourceType parameters can be specified.
Updates the parameter values for stack instances for the specified accounts, within the specified Amazon Web Services Regions. A stack instance refers to a stack in a specific account and Region.
\nYou can only update stack instances in Amazon Web Services Regions and accounts where they already exist; to\n create additional stack instances, use \n CreateStackInstances\n .
During stack set updates, any parameters overridden for a stack instance aren't updated, but retain their\n overridden value.
\nYou can only update the parameter values that are specified in the stack set; to add or\n delete a parameter itself, use \n UpdateStackSet\n to update the stack set\n template. If you add a parameter to a template, before you can override the parameter value specified in the stack\n set you must first use \n UpdateStackSet\n to update all stack\n instances with the updated template and parameter value specified in the stack set. Once a stack instance has been\n updated with the new parameter, you can then override the parameter value using\n UpdateStackInstances.
Updates the parameter values for stack instances for the specified accounts, within the specified Amazon Web Services Regions. A stack instance refers to a stack in a specific account and Region.
\nYou can only update stack instances in Amazon Web Services Regions and accounts where they already exist; to\n create additional stack instances, use \n CreateStackInstances\n .
During stack set updates, any parameters overridden for a stack instance aren't updated, but retain their\n overridden value.
\nYou can only update the parameter values that are specified in the stack set; to add or\n delete a parameter itself, use \n UpdateStackSet\n to update the\n stack set template. If you add a parameter to a template, before you can override the parameter value specified in\n the stack set you must first use \n UpdateStackSet\n to update all\n stack instances with the updated template and parameter value specified in the stack set. Once a stack instance has\n been updated with the new parameter, you can then override the parameter value using\n UpdateStackInstances.
A list of input parameters whose values you want to update for the specified stack instances.
\nAny overridden parameter values will be applied to all stack instances in the specified accounts and Amazon Web Services Regions. When specifying parameters and their values, be aware of how CloudFormation sets parameter values\n during stack instance update operations:
\nTo override the current value for a parameter, include the parameter and specify its value.
\nTo leave an overridden parameter set to its present value, include the parameter and specify\n UsePreviousValue as true. (You can't specify both a value and set\n UsePreviousValue to true.)
To set an overridden parameter back to the value specified in the stack set, specify a parameter list but\n don't include the parameter in the list.
\nTo leave all parameters set to their present values, don't specify this property at all.
\nDuring stack set updates, any parameter values overridden for a stack instance aren't updated, but retain their\n overridden value.
\nYou can only override the parameter values that are specified in the stack set; to add or\n delete a parameter itself, use UpdateStackSet to update the stack set template. If you add a parameter\n to a template, before you can override the parameter value specified in the stack set you must first use \n UpdateStackSet\n to\n update all stack instances with the updated template and parameter value specified in the stack set. Once a stack\n instance has been updated with the new parameter, you can then override the parameter value using\n UpdateStackInstances.
A list of input parameters whose values you want to update for the specified stack instances.
\nAny overridden parameter values will be applied to all stack instances in the specified accounts and Amazon Web Services Regions. When specifying parameters and their values, be aware of how CloudFormation sets parameter values\n during stack instance update operations:
\nTo override the current value for a parameter, include the parameter and specify its value.
\nTo leave an overridden parameter set to its present value, include the parameter and specify\n UsePreviousValue as true. (You can't specify both a value and set\n UsePreviousValue to true.)
To set an overridden parameter back to the value specified in the stack set, specify a parameter list but\n don't include the parameter in the list.
\nTo leave all parameters set to their present values, don't specify this property at all.
\nDuring stack set updates, any parameter values overridden for a stack instance aren't updated, but retain their\n overridden value.
\nYou can only override the parameter values that are specified in the stack set; to add or\n delete a parameter itself, use UpdateStackSet to update the stack set template. If you add a parameter\n to a template, before you can override the parameter value specified in the stack set you must first use \n UpdateStackSet\n to update all stack instances with the updated template and parameter value\n specified in the stack set. Once a stack instance has been updated with the new parameter, you can then override the\n parameter value using UpdateStackInstances.
In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order\n for CloudFormation to update the stack set and its associated stack instances.
\n\n CAPABILITY_IAM and CAPABILITY_NAMED_IAM\n
Some stack templates might include resources that can affect permissions in your Amazon Web Services account;\n for example, by creating new Identity and Access Management (IAM) users. For those stacks sets, you must explicitly\n acknowledge this by specifying one of these capabilities.
\nThe following IAM resources require you to specify either the CAPABILITY_IAM or\n CAPABILITY_NAMED_IAM capability.
If you have IAM resources, you can specify either capability.
\nIf you have IAM resources with custom names, you must specify\n CAPABILITY_NAMED_IAM.
If you don't specify either of these capabilities, CloudFormation returns an\n InsufficientCapabilities error.
If your stack template contains these resources, we recommend that you review all permissions associated with\n them and edit their permissions if necessary.
\n\n \n AWS::IAM::AccessKey\n \n
\n \n AWS::IAM::Group\n \n
\n \n AWS::IAM::Policy\n \n
\n \n AWS::IAM::Role\n \n
\n \n AWS::IAM::User\n \n
For more information, see Acknowledging IAM Resources in\n CloudFormation Templates.
\n\n CAPABILITY_AUTO_EXPAND\n
Some templates reference macros. If your stack set template references one or more macros, you must update the\n stack set directly from the processed template, without first reviewing the resulting changes in a change set. To\n update the stack set directly, you must acknowledge this capability. For more information, see Using CloudFormation Macros to\n Perform Custom Processing on Templates.
\nStack sets with service-managed permissions do not currently support the use of macros in templates. (This\n includes the \n AWS::Include\n and \n AWS::Serverless\n transforms, which\n are macros hosted by CloudFormation.) Even if you specify this capability for a stack set with service-managed permissions,\n if you reference a macro in your template the stack set operation will fail.
In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order\n for CloudFormation to update the stack set and its associated stack instances.
\n\n CAPABILITY_IAM and CAPABILITY_NAMED_IAM\n
Some stack templates might include resources that can affect permissions in your Amazon Web Services account;\n for example, by creating new Identity and Access Management (IAM) users. For those stacks sets, you must explicitly\n acknowledge this by specifying one of these capabilities.
\nThe following IAM resources require you to specify either the CAPABILITY_IAM or\n CAPABILITY_NAMED_IAM capability.
If you have IAM resources, you can specify either capability.
\nIf you have IAM resources with custom names, you must specify\n CAPABILITY_NAMED_IAM.
If you don't specify either of these capabilities, CloudFormation returns an\n InsufficientCapabilities error.
If your stack template contains these resources, we recommend that you review all permissions associated with\n them and edit their permissions if necessary.
\n\n \n AWS::IAM::AccessKey\n \n
\n \n AWS::IAM::Group\n \n
\n \n AWS::IAM::Policy\n \n
\n \n AWS::IAM::Role\n \n
\n \n AWS::IAM::User\n \n
For more information, see Acknowledging IAM Resources in\n CloudFormation Templates.
\n\n CAPABILITY_AUTO_EXPAND\n
Some templates reference macros. If your stack set template references one or more macros, you must update the\n stack set directly from the processed template, without first reviewing the resulting changes in a change set. To\n update the stack set directly, you must acknowledge this capability. For more information, see Using CloudFormation Macros to\n Perform Custom Processing on Templates.
\nStack sets with service-managed permissions do not currently support the use of macros in templates. (This\n includes the \n AWS::Include\n and \n AWS::Serverless\n \n transforms, which are macros hosted by CloudFormation.) Even if you specify this capability for a stack set with\n service-managed permissions, if you reference a macro in your template the stack set operation will fail.
Specifies the name of the key policy. The only valid name is default. To get\n the names of key policies, use ListKeyPolicies.
Specifies the name of the key policy. If no policy name is specified, the default value is default. The only valid name is default. To get\n the names of key policies, use ListKeyPolicies.
A key policy document in JSON format.
" } + }, + "PolicyName": { + "target": "com.amazonaws.kms#PolicyNameType", + "traits": { + "smithy.api#documentation": "The name of the key policy. The only valid value is default.
Imports or reimports key material into an existing KMS key that was created without key\n material. ImportKeyMaterial also sets the expiration model and expiration date of\n the imported key material.
By default, KMS keys are created with key material that KMS generates. This operation\n supports Importing key\n material, an advanced feature that lets you generate and import the cryptographic\n key material for a KMS key. For more information about importing key material into KMS, see\n Importing key\n material in the Key Management Service Developer Guide.
\nAfter you successfully import key material into a KMS key, you can reimport\n the same key material into that KMS key, but you cannot import different key\n material. You might reimport key material to replace key material that expired or key material\n that you deleted. You might also reimport key material to change the expiration model or\n expiration date of the key material. Before reimporting key material, if necessary, call DeleteImportedKeyMaterial to delete the current imported key material.
\nEach time you import key material into KMS, you can determine whether\n (ExpirationModel) and when (ValidTo) the key material expires. To\n change the expiration of your key material, you must import it again, either by calling\n ImportKeyMaterial or using the import features of the KMS console.
Before calling ImportKeyMaterial:
Create or identify a KMS key with no key material. The KMS key must have an\n Origin value of EXTERNAL, which indicates that the KMS key is\n designed for imported key material.
To create an new KMS key for imported key material, call the CreateKey operation with an Origin value of EXTERNAL. You can create a\n symmetric encryption KMS key, HMAC KMS key, asymmetric encryption KMS key, or asymmetric\n signing KMS key. You can also import key material into a multi-Region key of any\n supported type. However, you can't import key material into a KMS key in a custom key store.
Use the DescribeKey operation to verify that the\n KeyState of the KMS key is PendingImport, which indicates that\n the KMS key has no key material.
If you are reimporting the same key material into an existing KMS key, you might need\n to call the DeleteImportedKeyMaterial to delete its existing key\n material.
\nCall the GetParametersForImport operation to get a public key and\n import token set for importing key material.
\nUse the public key in the GetParametersForImport response to encrypt\n your key material.
\n Then, in an ImportKeyMaterial request, you submit your encrypted key\n material and import token. When calling this operation, you must specify the following\n values:
The key ID or key ARN of the KMS key to associate with the imported key material. Its\n Origin must be EXTERNAL and its KeyState must be\n PendingImport. You cannot perform this operation on a KMS key in a custom key store, or on a KMS\n key in a different Amazon Web Services account. To get the Origin and KeyState\n of a KMS key, call DescribeKey.
The encrypted key material.
\nThe import token that GetParametersForImport returned. You must use\n a public key and token from the same GetParametersForImport response.
Whether the key material expires (ExpirationModel) and, if so, when\n (ValidTo). For help with this choice, see Setting an expiration time in the Key Management Service Developer Guide.
If you set an expiration date, KMS deletes the key material from the KMS key on the\n specified date, making the KMS key unusable. To use the KMS key in cryptographic\n operations again, you must reimport the same key material. However, you can delete and\n reimport the key material at any time, including before the key material expires. Each\n time you reimport, you can eliminate or reset the expiration time.
\nWhen this operation is successful, the key state of the KMS key changes from\n PendingImport to Enabled, and you can use the KMS key in\n cryptographic operations.
If this operation fails, use the exception to help determine the problem. If the error is\n related to the key material, the import token, or wrapping key, use GetParametersForImport to get a new public key and import token for the KMS key\n and repeat the import procedure. For help, see How To Import Key\n Material in the Key Management Service Developer Guide.
\nThe KMS key that you use for this operation must be in a compatible key state. For\ndetails, see Key states of KMS keys in the Key Management Service Developer Guide.
\n\n Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
\n\n Required permissions: kms:ImportKeyMaterial (key policy)
\n\n Related operations:\n
\n\n Eventual consistency: The KMS API follows an eventual consistency model. \n For more information, see KMS eventual consistency.
", + "smithy.api#documentation": "Imports or reimports key material into an existing KMS key that was created without key\n material. ImportKeyMaterial also sets the expiration model and expiration date of\n the imported key material.
By default, KMS keys are created with key material that KMS generates. This operation\n supports Importing key\n material, an advanced feature that lets you generate and import the cryptographic\n key material for a KMS key. For more information about importing key material into KMS, see\n Importing key\n material in the Key Management Service Developer Guide.
\nAfter you successfully import key material into a KMS key, you can reimport\n the same key material into that KMS key, but you cannot import different key\n material. You might reimport key material to replace key material that expired or key material\n that you deleted. You might also reimport key material to change the expiration model or\n expiration date of the key material.
\nEach time you import key material into KMS, you can determine whether\n (ExpirationModel) and when (ValidTo) the key material expires. To\n change the expiration of your key material, you must import it again, either by calling\n ImportKeyMaterial or using the import features of the KMS console.
Before calling ImportKeyMaterial:
Create or identify a KMS key with no key material. The KMS key must have an\n Origin value of EXTERNAL, which indicates that the KMS key is\n designed for imported key material.
To create an new KMS key for imported key material, call the CreateKey operation with an Origin value of EXTERNAL. You can create a\n symmetric encryption KMS key, HMAC KMS key, asymmetric encryption KMS key, or asymmetric\n signing KMS key. You can also import key material into a multi-Region key of any\n supported type. However, you can't import key material into a KMS key in a custom key store.
Use the DescribeKey operation to verify that the\n KeyState of the KMS key is PendingImport, which indicates that\n the KMS key has no key material.
If you are reimporting the same key material into an existing KMS key, you might need\n to call the DeleteImportedKeyMaterial to delete its existing key\n material.
\nCall the GetParametersForImport operation to get a public key and\n import token set for importing key material.
\nUse the public key in the GetParametersForImport response to encrypt\n your key material.
\n Then, in an ImportKeyMaterial request, you submit your encrypted key\n material and import token. When calling this operation, you must specify the following\n values:
The key ID or key ARN of the KMS key to associate with the imported key material. Its\n Origin must be EXTERNAL and its KeyState must be\n PendingImport. You cannot perform this operation on a KMS key in a custom key store, or on a KMS\n key in a different Amazon Web Services account. To get the Origin and KeyState\n of a KMS key, call DescribeKey.
The encrypted key material.
\nThe import token that GetParametersForImport returned. You must use\n a public key and token from the same GetParametersForImport response.
Whether the key material expires (ExpirationModel) and, if so, when\n (ValidTo). For help with this choice, see Setting an expiration time in the Key Management Service Developer Guide.
If you set an expiration date, KMS deletes the key material from the KMS key on the\n specified date, making the KMS key unusable. To use the KMS key in cryptographic\n operations again, you must reimport the same key material. However, you can delete and\n reimport the key material at any time, including before the key material expires. Each\n time you reimport, you can eliminate or reset the expiration time.
\nWhen this operation is successful, the key state of the KMS key changes from\n PendingImport to Enabled, and you can use the KMS key in\n cryptographic operations.
If this operation fails, use the exception to help determine the problem. If the error is\n related to the key material, the import token, or wrapping key, use GetParametersForImport to get a new public key and import token for the KMS key\n and repeat the import procedure. For help, see How To Import Key\n Material in the Key Management Service Developer Guide.
\nThe KMS key that you use for this operation must be in a compatible key state. For\ndetails, see Key states of KMS keys in the Key Management Service Developer Guide.
\n\n Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
\n\n Required permissions: kms:ImportKeyMaterial (key policy)
\n\n Related operations:\n
\n\n Eventual consistency: The KMS API follows an eventual consistency model. \n For more information, see KMS eventual consistency.
", "smithy.api#examples": [ { "title": "To import key material into a KMS key", @@ -5735,8 +5740,7 @@ "PolicyName": { "target": "com.amazonaws.kms#PolicyNameType", "traits": { - "smithy.api#documentation": "The name of the key policy. The only valid value is default.
The name of the key policy. If no policy name is specified, the default value is default. The only valid value is default.
Deletes the specified grant. You revoke a grant to terminate the permissions that the\n grant allows. For more information, see Retiring and revoking grants in\n the \n Key Management Service Developer Guide\n .
\nWhen you create, retire, or revoke a grant, there might be a brief delay, usually less than five minutes, until the grant is available throughout KMS. This state is known as eventual consistency. For details, see Eventual consistency in\n the \n Key Management Service Developer Guide\n .
\nFor detailed information about grants, including grant terminology, see Grants in KMS in the\n \n Key Management Service Developer Guide\n . For examples of working with grants in several\n programming languages, see Programming grants.
\n\n Cross-account use: Yes. To perform this operation on a KMS key in a different Amazon Web Services account, specify the key\n ARN in the value of the KeyId parameter.
\n Required permissions: kms:RevokeGrant (key policy).
\n\n Related operations:\n
\n\n CreateGrant\n
\n\n ListGrants\n
\n\n ListRetirableGrants\n
\n\n RetireGrant\n
\n\n Eventual consistency: The KMS API follows an eventual consistency model. \n For more information, see KMS eventual consistency.
", + "smithy.api#documentation": "Deletes the specified grant. You revoke a grant to terminate the permissions that the\n grant allows. For more information, see Retiring and revoking grants in\n the \n Key Management Service Developer Guide\n .
\nWhen you create, retire, or revoke a grant, there might be a brief delay, usually less than five minutes, until the grant is available throughout KMS. This state is known as eventual consistency. For details, see Eventual consistency in\n the \n Key Management Service Developer Guide\n .
\nFor detailed information about grants, including grant terminology, see Grants in KMS in the\n \n Key Management Service Developer Guide\n . For examples of working with grants in several\n programming languages, see Programming grants.
\n\n Cross-account use: Yes. To perform this operation on a KMS key in a different Amazon Web Services account, specify the key\n ARN in the value of the KeyId parameter.
\n Required permissions: kms:RevokeGrant (key policy).
\n\n Related operations:\n
\n\n CreateGrant\n
\n\n ListGrants\n
\n\n ListRetirableGrants\n
\n\n RetireGrant\n
\n\n Eventual consistency: The KMS API follows an eventual consistency model. \n For more information, see KMS eventual consistency.
", "smithy.api#examples": [ { "title": "To revoke a grant", diff --git a/aws-models/mediatailor.json b/aws-models/mediatailor.json index 0645faf66ce9..3d47857a4c89 100644 --- a/aws-models/mediatailor.json +++ b/aws-models/mediatailor.json @@ -225,6 +225,79 @@ } } }, + "com.amazonaws.mediatailor#AlternateMedia": { + "type": "structure", + "members": { + "SourceLocationName": { + "target": "com.amazonaws.mediatailor#__string", + "traits": { + "smithy.api#documentation": "The name of the source location for alternateMedia.
" + } + }, + "LiveSourceName": { + "target": "com.amazonaws.mediatailor#__string", + "traits": { + "smithy.api#documentation": "The name of the live source for alternateMedia.
" + } + }, + "VodSourceName": { + "target": "com.amazonaws.mediatailor#__string", + "traits": { + "smithy.api#documentation": "The name of the VOD source for alternateMedia.
" + } + }, + "ClipRange": { + "target": "com.amazonaws.mediatailor#ClipRange" + }, + "ScheduledStartTimeMillis": { + "target": "com.amazonaws.mediatailor#__long", + "traits": { + "smithy.api#documentation": "The date and time that the alternateMedia is scheduled to start, in epoch milliseconds.
" + } + }, + "AdBreaks": { + "target": "com.amazonaws.mediatailor#__listOfAdBreak", + "traits": { + "smithy.api#documentation": "Ad break configuration parameters defined in AlternateMedia.
" + } + }, + "DurationMillis": { + "target": "com.amazonaws.mediatailor#__long", + "traits": { + "smithy.api#documentation": "The duration of the alternateMedia in milliseconds.
" + } + } + }, + "traits": { + "smithy.api#documentation": "A playlist of media (VOD and/or live) to be played instead of the default media on a particular program.
" + } + }, + "com.amazonaws.mediatailor#AudienceMedia": { + "type": "structure", + "members": { + "Audience": { + "target": "com.amazonaws.mediatailor#__string", + "traits": { + "smithy.api#documentation": "The Audience defined in AudienceMedia.
" + } + }, + "AlternateMedia": { + "target": "com.amazonaws.mediatailor#__listOfAlternateMedia", + "traits": { + "smithy.api#documentation": "The list of AlternateMedia defined in AudienceMedia.
" + } + } + }, + "traits": { + "smithy.api#documentation": "An AudienceMedia object contains an Audience and a list of AlternateMedia.
" + } + }, + "com.amazonaws.mediatailor#Audiences": { + "type": "list", + "member": { + "target": "smithy.api#String" + } + }, "com.amazonaws.mediatailor#AvailMatchingCriteria": { "type": "structure", "members": { @@ -402,6 +475,12 @@ "smithy.api#documentation": "The log configuration.
", "smithy.api#required": {} } + }, + "Audiences": { + "target": "com.amazonaws.mediatailor#Audiences", + "traits": { + "smithy.api#documentation": "The list of audiences defined in channel.
" + } } }, "traits": { @@ -520,8 +599,15 @@ "EndOffsetMillis": { "target": "com.amazonaws.mediatailor#__long", "traits": { - "smithy.api#documentation": "The end offset of the clip range, in milliseconds, starting from the beginning of the VOD source associated with the program.
", - "smithy.api#required": {} + "smithy.api#addedDefault": {}, + "smithy.api#default": 0, + "smithy.api#documentation": "The end offset of the clip range, in milliseconds, starting from the beginning of the VOD source associated with the program.
" + } + }, + "StartOffsetMillis": { + "target": "com.amazonaws.mediatailor#__long", + "traits": { + "smithy.api#documentation": "The start offset of the clip range, in milliseconds. This offset truncates the start at the number of milliseconds into the duration of the VOD source.
" } } }, @@ -745,6 +831,12 @@ "traits": { "smithy.api#documentation": "\n The time-shifted viewing configuration you want to associate to the channel.\n
" } + }, + "Audiences": { + "target": "com.amazonaws.mediatailor#Audiences", + "traits": { + "smithy.api#documentation": "The list of audiences defined in channel.
" + } } } }, @@ -823,6 +915,12 @@ "traits": { "smithy.api#documentation": "\n The time-shifted viewing configuration assigned to the channel.\n
" } + }, + "Audiences": { + "target": "com.amazonaws.mediatailor#Audiences", + "traits": { + "smithy.api#documentation": "The list of audiences defined in channel.
" + } } } }, @@ -1095,6 +1193,12 @@ "traits": { "smithy.api#documentation": "The name that's used to refer to a VOD source.
" } + }, + "AudienceMedia": { + "target": "com.amazonaws.mediatailor#__listOfAudienceMedia", + "traits": { + "smithy.api#documentation": "The list of AudienceMedia defined in program.
" + } } } }, @@ -1166,6 +1270,12 @@ "traits": { "smithy.api#documentation": "The duration of the live program in milliseconds.
" } + }, + "AudienceMedia": { + "target": "com.amazonaws.mediatailor#__listOfAudienceMedia", + "traits": { + "smithy.api#documentation": "The list of AudienceMedia defined in program.
" + } } } }, @@ -1910,6 +2020,12 @@ "traits": { "smithy.api#documentation": "\n The time-shifted viewing configuration for the channel.\n
" } + }, + "Audiences": { + "target": "com.amazonaws.mediatailor#Audiences", + "traits": { + "smithy.api#documentation": "The list of audiences defined in channel.
" + } } } }, @@ -2107,6 +2223,12 @@ "traits": { "smithy.api#documentation": "The duration of the live program in milliseconds.
" } + }, + "AudienceMedia": { + "target": "com.amazonaws.mediatailor#__listOfAudienceMedia", + "traits": { + "smithy.api#documentation": "The list of AudienceMedia defined in program.
" + } } } }, @@ -2408,6 +2530,13 @@ "smithy.api#documentation": "(Optional) If the playback configuration has more than MaxResults channel schedules, use NextToken to get the second and subsequent pages of results.
For the first GetChannelScheduleRequest request, omit this value.
For the second and subsequent requests, get the value of NextToken from the previous response and specify that value for NextToken in the request.
If the previous response didn't include a NextToken element, there are no more channel schedules to get.
The single audience for GetChannelScheduleRequest.
", + "smithy.api#httpQuery": "audience" + } } } }, @@ -5147,6 +5276,12 @@ "traits": { "smithy.api#documentation": "The name of the VOD source.
" } + }, + "Audiences": { + "target": "com.amazonaws.mediatailor#Audiences", + "traits": { + "smithy.api#documentation": "The list of audiences defined in ScheduleEntry.
" + } } }, "traits": { @@ -5167,6 +5302,12 @@ "traits": { "smithy.api#enumValue": "FILLER_SLATE" } + }, + "ALTERNATE_MEDIA": { + "target": "smithy.api#Unit", + "traits": { + "smithy.api#enumValue": "ALTERNATE_MEDIA" + } } } }, @@ -5741,6 +5882,12 @@ "traits": { "smithy.api#documentation": "\n The time-shifted viewing configuration you want to associate to the channel.\n
" } + }, + "Audiences": { + "target": "com.amazonaws.mediatailor#Audiences", + "traits": { + "smithy.api#documentation": "The list of audiences defined in channel.
" + } } } }, @@ -5819,6 +5966,12 @@ "traits": { "smithy.api#documentation": "\n The time-shifted viewing configuration for the channel.\n
" } + }, + "Audiences": { + "target": "com.amazonaws.mediatailor#Audiences", + "traits": { + "smithy.api#documentation": "The list of audiences defined in channel.
" + } } } }, @@ -5965,6 +6118,12 @@ "smithy.api#documentation": "The schedule configuration settings.
", "smithy.api#required": {} } + }, + "AudienceMedia": { + "target": "com.amazonaws.mediatailor#__listOfAudienceMedia", + "traits": { + "smithy.api#documentation": "The list of AudienceMedia defined in program.
" + } } } }, @@ -6036,6 +6195,12 @@ "traits": { "smithy.api#documentation": "The scheduled start time for this Program.
" } + }, + "AudienceMedia": { + "target": "com.amazonaws.mediatailor#__listOfAudienceMedia", + "traits": { + "smithy.api#documentation": "The list of AudienceMedia defined in program.
" + } } } }, @@ -6420,6 +6585,18 @@ "target": "com.amazonaws.mediatailor#Alert" } }, + "com.amazonaws.mediatailor#__listOfAlternateMedia": { + "type": "list", + "member": { + "target": "com.amazonaws.mediatailor#AlternateMedia" + } + }, + "com.amazonaws.mediatailor#__listOfAudienceMedia": { + "type": "list", + "member": { + "target": "com.amazonaws.mediatailor#AudienceMedia" + } + }, "com.amazonaws.mediatailor#__listOfAvailMatchingCriteria": { "type": "list", "member": { diff --git a/aws-models/rds.json b/aws-models/rds.json index ec551da9f5a8..b43b6ef28ad0 100644 --- a/aws-models/rds.json +++ b/aws-models/rds.json @@ -844,6 +844,9 @@ { "target": "com.amazonaws.rds#ModifyGlobalCluster" }, + { + "target": "com.amazonaws.rds#ModifyIntegration" + }, { "target": "com.amazonaws.rds#ModifyOptionGroup" }, @@ -6628,8 +6631,9 @@ "TargetArn": "arn:aws:redshift-serverless:us-east-1:123456789012:namespace/62c70612-0302-4db7-8414-b5e3e049f0d8" }, "output": { - "SourceArn": "arn:aws:rds:us-east-1:123456789012:cluster:my-cluster", "IntegrationName": "my-integration", + "IntegrationArn": "arn:aws:rds:us-east-1:123456789012:integration:5b9f3d79-7392-4a3e-896c-58eaa1b53231", + "SourceArn": "arn:aws:rds:us-east-1:123456789012:cluster:my-cluster", "TargetArn": "arn:aws:redshift-serverless:us-east-1:123456789012:namespace/62c70612-0302-4db7-8414-b5e3e049f0d8", "Tags": [], "CreateTime": "2023-12-28T17:20:20.629Z", @@ -6681,6 +6685,18 @@ }, "Tags": { "target": "com.amazonaws.rds#TagList" + }, + "DataFilter": { + "target": "com.amazonaws.rds#DataFilter", + "traits": { + "smithy.api#documentation": "Data filtering options for the integration. For more information, see \n Data filtering for Aurora zero-ETL integrations with Amazon Redshift.\n
\nValid for: Integrations with Aurora MySQL source DB clusters only
" + } + }, + "Description": { + "target": "com.amazonaws.rds#IntegrationDescription", + "traits": { + "smithy.api#documentation": "A description of the integration.
" + } } }, "traits": { @@ -11776,6 +11792,16 @@ "smithy.api#httpError": 400 } }, + "com.amazonaws.rds#DataFilter": { + "type": "string", + "traits": { + "smithy.api#length": { + "min": 1, + "max": 25600 + }, + "smithy.api#pattern": "^[a-zA-Z0-9_ \"\\\\\\-$,*.:?+\\/]*$" + } + }, "com.amazonaws.rds#DatabaseArn": { "type": "string", "traits": { @@ -12950,6 +12976,7 @@ "output": { "SourceArn": "arn:aws:rds:us-east-1:123456789012:cluster:my-cluster", "IntegrationName": "my-integration", + "IntegrationArn": "arn:aws:rds:us-east-1:123456789012:integration:5b9f3d79-7392-4a3e-896c-58eaa1b53231", "TargetArn": "arn:aws:redshift-serverless:us-east-1:123456789012:namespace/62c70612-0302-4db7-8414-b5e3e049f0d8", "Tags": [], "CreateTime": "2023-12-28T17:20:20.629Z", @@ -17004,6 +17031,7 @@ "Integrations": [ { "IntegrationName": "my-integration", + "IntegrationArn": "arn:aws:rds:us-east-1:123456789012:integration:5b9f3d79-7392-4a3e-896c-58eaa1b53231", "SourceArn": "arn:aws:rds:us-east-1:123456789012:cluster:my-cluster", "TargetArn": "arn:aws:redshift-serverless:us-east-1:123456789012:namespace/62c70612-0302-4db7-8414-b5e3e049f0d8", "Tags": [], @@ -19762,6 +19790,18 @@ "traits": { "smithy.api#documentation": "Any errors associated with the integration.
" } + }, + "DataFilter": { + "target": "com.amazonaws.rds#DataFilter", + "traits": { + "smithy.api#documentation": "Data filters for the integration. These filters determine which tables\n from the source database are sent to the target Amazon Redshift data warehouse. \n
" + } + }, + "Description": { + "target": "com.amazonaws.rds#IntegrationDescription", + "traits": { + "smithy.api#documentation": "A description of the integration.
" + } } }, "traits": { @@ -19792,7 +19832,7 @@ "min": 1, "max": 255 }, - "smithy.api#pattern": "^arn:aws[a-z\\-]*:rds(-[a-z]*)?:[a-z0-9\\-]*:[0-9]*:integration:[a-z][a-z0-9]*(-[a-zA-Z0-9]+)*\\/[a-zA-Z0-9_:\\-\\/]+$" + "smithy.api#pattern": "^arn:aws[a-z\\-]*:rds(-[a-z]*)?:[a-z0-9\\-]*:[0-9]*:integration:[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$" } }, "com.amazonaws.rds#IntegrationConflictOperationFault": { @@ -19812,6 +19852,16 @@ "smithy.api#httpError": 400 } }, + "com.amazonaws.rds#IntegrationDescription": { + "type": "string", + "traits": { + "smithy.api#length": { + "min": 0, + "max": 1000 + }, + "smithy.api#pattern": ".*" + } + }, "com.amazonaws.rds#IntegrationError": { "type": "structure", "members": { @@ -23308,6 +23358,84 @@ "smithy.api#output": {} } }, + "com.amazonaws.rds#ModifyIntegration": { + "type": "operation", + "input": { + "target": "com.amazonaws.rds#ModifyIntegrationMessage" + }, + "output": { + "target": "com.amazonaws.rds#Integration" + }, + "errors": [ + { + "target": "com.amazonaws.rds#IntegrationConflictOperationFault" + }, + { + "target": "com.amazonaws.rds#IntegrationNotFoundFault" + }, + { + "target": "com.amazonaws.rds#InvalidIntegrationStateFault" + } + ], + "traits": { + "smithy.api#documentation": "Modifies a zero-ETL integration with Amazon Redshift.
\nCurrently, you can only modify integrations that have Aurora MySQL source DB clusters. Integrations with Aurora PostgreSQL and RDS sources currently don't support modifying the integration.
\nThe unique identifier of the integration to modify.
", + "smithy.api#required": {} + } + }, + "IntegrationName": { + "target": "com.amazonaws.rds#IntegrationName", + "traits": { + "smithy.api#documentation": "A new name for the integration.
" + } + }, + "DataFilter": { + "target": "com.amazonaws.rds#DataFilter", + "traits": { + "smithy.api#documentation": "A new data filter for the integration. For more information, see \n Data filtering for Aurora zero-ETL integrations with Amazon Redshift.
" + } + }, + "Description": { + "target": "com.amazonaws.rds#IntegrationDescription", + "traits": { + "smithy.api#documentation": "A new description for the integration.
" + } + } + }, + "traits": { + "smithy.api#input": {} + } + }, "com.amazonaws.rds#ModifyOptionGroup": { "type": "operation", "input": { diff --git a/aws-models/s3.json b/aws-models/s3.json index 1d8505b2f50e..0148e679b0f6 100644 --- a/aws-models/s3.json +++ b/aws-models/s3.json @@ -19219,6 +19219,16 @@ "traits": { "smithy.api#documentation": "This action creates an Amazon S3 bucket. To create an Amazon S3 on Outposts bucket, see \n CreateBucket\n .
Creates a new S3 bucket. To create a bucket, you must set up Amazon S3 and have a\n valid Amazon Web Services Access Key ID to authenticate requests. Anonymous requests are never allowed to\n create buckets. By creating the bucket, you become the bucket owner.
\nThere are two types of buckets: general purpose buckets and directory buckets. For more\n information about these bucket types, see Creating, configuring, and\n working with Amazon S3 buckets in the Amazon S3 User Guide.
\n\n General purpose buckets - If you send your CreateBucket request to the s3.amazonaws.com global endpoint,\n the request goes to the us-east-1 Region. So the signature\n calculations in Signature Version 4 must use us-east-1 as the Region, even\n if the location constraint in the request specifies another Region where the bucket is\n to be created. If you create a bucket in a Region other than US East (N. Virginia), your\n application must be able to handle 307 redirect. For more information, see Virtual hosting of\n buckets in the Amazon S3 User Guide.
\n Directory buckets - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the format https://s3express-control.region_code.amazonaws.com/bucket-name\n . Virtual-hosted-style requests aren't supported. \nFor more information, see Regional and Zonal endpoints in the\n Amazon S3 User Guide.
\n General purpose bucket permissions - In addition to the s3:CreateBucket permission, the following permissions are\n required in a policy when your CreateBucket request includes specific\n headers:
\n Access control lists (ACLs) - In your CreateBucket request, if you specify an access control list (ACL) \n and set it to public-read, public-read-write,\n authenticated-read, or if you explicitly specify any other custom ACLs, both s3:CreateBucket and\n s3:PutBucketAcl permissions are required. In your CreateBucket request, if you set the ACL to private, \n or if you don't specify any ACLs, only the s3:CreateBucket permission is required.\n
\n Object Lock - In your\n CreateBucket request, if you set \n x-amz-bucket-object-lock-enabled to true, the \n s3:PutBucketObjectLockConfiguration and\n s3:PutBucketVersioning permissions are required.
\n S3 Object Ownership - If your\n CreateBucket request includes the\n x-amz-object-ownership header, then the\n s3:PutBucketOwnershipControls permission is required.
To set an ACL on a bucket as part of a\n CreateBucket request, you must explicitly set S3\n Object Ownership for the bucket to a different value than the\n default, BucketOwnerEnforced. Additionally, if your\n desired bucket ACL grants public access, you must first create the\n bucket (without the bucket ACL) and then explicitly disable Block\n Public Access on the bucket before using PutBucketAcl\n to set the ACL. If you try to create a bucket with a public ACL,\n the request will fail.
For the majority of modern use cases in S3, we recommend\n that you keep all Block Public Access settings enabled and keep\n ACLs disabled. If you would like to share data with users outside\n of your account, you can use bucket policies as needed. For more\n information, see Controlling ownership of objects and disabling ACLs for your\n bucket and Blocking public access to your Amazon S3 storage in\n the Amazon S3 User Guide.
\n\n S3 Block Public Access - If your\n specific use case requires granting public access to your S3 resources, you\n can disable Block Public Access. Specifically, you can create a new bucket with Block\n Public Access enabled, then separately call the \n DeletePublicAccessBlock\n API. To use this operation, you must have the\n s3:PutBucketPublicAccessBlock permission. For more information about S3 Block Public\n Access, see Blocking\n public access to your Amazon S3 storage in the\n Amazon S3 User Guide.
\n Directory bucket permissions - You must have the s3express:CreateBucket permission in an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource. For more information about directory bucket policies and permissions, see Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone in the Amazon S3 User Guide.
The permissions for ACLs, Object Lock, S3 Object Ownership, and S3 Block Public Access are not supported for directory buckets. \n For directory buckets, all Block Public Access settings are enabled at the bucket level and S3 \n Object Ownership is set to Bucket owner enforced (ACLs disabled). These settings can't be modified.\n
\nFor more information about permissions for creating and working with \n directory buckets, see Directory buckets in the Amazon S3 User Guide. \n For more information about supported S3 features for directory buckets, see Features of S3 Express One Zone in the Amazon S3 User Guide.
\n\n Directory buckets - The HTTP Host header syntax is s3express-control.region.amazonaws.com.
The following operations are related to CreateBucket:
\n PutObject\n
\n\n DeleteBucket\n
\nRemoves an object from a bucket. The behavior depends on the bucket's versioning state:
\nIf bucket versioning is not enabled, the operation permanently deletes the object.
\nIf bucket versioning is enabled, the operation inserts a delete marker, which becomes the current version of the object. To permanently delete an object in a versioned bucket, you must include the object’s versionId in the request. For more information about versioning-enabled buckets, see Deleting object versions from a versioning-enabled bucket.
If bucket versioning is suspended, the operation removes the object that has a null versionId, if there is one, and inserts a delete marker that becomes the current version of the object. If there isn't an object with a null versionId, and all versions of the object have a versionId, Amazon S3 does not remove the object and only inserts a delete marker. To permanently delete an object that has a versionId, you must include the object’s versionId in the request. For more information about versioning-suspended buckets, see Deleting objects from versioning-suspended buckets.
\n Directory buckets - S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the null value of the version ID is supported by directory buckets. You can only specify null \n to the versionId query parameter in the request.
\n Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://bucket_name.s3express-az_id.region.amazonaws.com/key-name\n . Path-style requests are not supported. For more information, see Regional and Zonal endpoints in the\n Amazon S3 User Guide.
To remove a specific version, you must use the versionId query parameter. Using this\n query parameter permanently deletes the version. If the object deleted is a delete marker, Amazon S3\n sets the response header x-amz-delete-marker to true.
If the object you want to delete is in a bucket where the bucket versioning\n configuration is MFA Delete enabled, you must include the x-amz-mfa request\n header in the DELETE versionId request. Requests that include\n x-amz-mfa must use HTTPS. For more information about MFA Delete, see Using MFA Delete in the Amazon S3\n User Guide. To see sample\n requests that use versioning, see Sample\n Request.
\n Directory buckets - MFA delete is not supported by directory buckets.
\nYou can delete objects by explicitly calling DELETE Object or calling \n (PutBucketLifecycle) to enable Amazon S3 to remove them for you. If you want to block\n users or accounts from removing or deleting objects from your bucket, you must deny them\n the s3:DeleteObject, s3:DeleteObjectVersion, and\n s3:PutLifeCycleConfiguration actions.
\n Directory buckets - S3 Lifecycle is not supported by directory buckets.
\n\n General purpose bucket permissions - The following permissions are required in your policies when your \n DeleteObjects request includes specific headers.
\n \n s3:DeleteObject\n - To delete an object from a bucket, you must always have the s3:DeleteObject permission.
\n \n s3:DeleteObjectVersion\n - To delete a specific version of an object from a versioning-enabled bucket, you must have the s3:DeleteObjectVersion permission.
\n Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the \n CreateSession\n API operation for session-based authorization. Specifically, you grant the s3express:CreateSession permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the CreateSession API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another CreateSession API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see \n CreateSession\n .
\n Directory buckets - The HTTP Host header syntax is \n Bucket_name.s3express-az_id.region.amazonaws.com.
The following action is related to DeleteObject:
\n PutObject\n
\nThe current legal hold status for the specified object.
", - "smithy.api#httpPayload": {} + "smithy.api#httpPayload": {}, + "smithy.api#xmlName": "LegalHold" } } }, @@ -24144,7 +24145,8 @@ "target": "com.amazonaws.s3#ObjectLockRetention", "traits": { "smithy.api#documentation": "The container element for an object's retention settings.
", - "smithy.api#httpPayload": {} + "smithy.api#httpPayload": {}, + "smithy.api#xmlName": "Retention" } } }, @@ -24211,40 +24213,40 @@ "smithy.api#documentation": "This operation is not supported by directory buckets.
\nReturns the tag-set of an object. You send the GET request against the tagging\n subresource associated with the object.
\nTo use this operation, you must have permission to perform the\n s3:GetObjectTagging action. By default, the GET action returns information\n about current version of an object. For a versioned bucket, you can have multiple versions\n of an object in your bucket. To retrieve tags of any other version, use the versionId query\n parameter. You also need permission for the s3:GetObjectVersionTagging\n action.
By default, the bucket owner has this permission and can grant this permission to\n others.
\nFor information about the Amazon S3 object tagging feature, see Object Tagging.
\nThe following actions are related to GetObjectTagging:
\n DeleteObjectTagging\n
\n\n GetObjectAttributes\n
\n\n PutObjectTagging\n
\nThis operation is not supported by directory buckets.
\nReturns metadata about all versions of the objects in a bucket. You can also use request\n parameters as selection criteria to return metadata about a subset of all the object\n versions.
\n To use this operation, you must have permission to perform the\n s3:ListBucketVersions action. Be aware of the name difference.
A 200 OK response can contain valid or invalid XML. Make sure to design\n your application to parse the contents of the response and handle it\n appropriately.
To use this operation, you must have READ access to the bucket.
\nThe following operations are related to ListObjectVersions:
\n ListObjectsV2\n
\n\n GetObject\n
\n\n PutObject\n
\n\n DeleteObject\n
\nAdds an object to a bucket.
\nAmazon S3 never adds partial objects; if you receive a success response, Amazon S3 added the\n entire object to the bucket. You cannot use PutObject to only update a\n single piece of metadata for an existing object. You must put the entire object with\n updated metadata if you want to update some values.
If your bucket uses the bucket owner enforced setting for Object Ownership, ACLs are disabled and no longer affect permissions. All\n objects written to the bucket by any account will be owned by the bucket owner.
\n\n Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format https://bucket_name.s3express-az_id.region.amazonaws.com/key-name\n . Path-style requests are not supported. For more information, see Regional and Zonal endpoints in the\n Amazon S3 User Guide.
Amazon S3 is a distributed system. If it receives multiple write requests for the same object\n simultaneously, it overwrites all but the last object written. However, Amazon S3 provides features that can modify this behavior:
\n\n S3 Object Lock - To prevent objects from\n being deleted or overwritten, you can use Amazon S3 Object\n Lock in the Amazon S3 User Guide.
\nThis functionality is not supported for directory buckets.
\n\n S3 Versioning - When you enable\n versioning for a bucket, if Amazon S3 receives multiple write requests for the same object\n simultaneously, it stores all versions of the objects. For each write request that is made to the same object, Amazon S3 automatically generates a unique version ID\n of that object being stored in Amazon S3. \n You can retrieve, replace, or delete any version of the object. For more information about versioning, see\n Adding Objects to\n Versioning-Enabled Buckets in the Amazon S3\n User Guide. For information about returning the versioning state\n of a bucket, see GetBucketVersioning.
\nThis functionality is not supported for directory buckets.
\n\n General purpose bucket permissions - The following permissions are required in your policies when your \n PutObject request includes specific headers.
\n \n s3:PutObject\n - To successfully complete the PutObject request, you must always have the s3:PutObject permission on a bucket to add an object\n to it.
\n \n s3:PutObjectAcl\n - To successfully change the objects ACL of your PutObject request, you must have the s3:PutObjectAcl.
\n \n s3:PutObjectTagging\n - To successfully set the tag-set with your PutObject request, you\n must have the s3:PutObjectTagging.
\n Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the \n CreateSession\n API operation for session-based authorization. Specifically, you grant the s3express:CreateSession permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the CreateSession API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another CreateSession API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see \n CreateSession\n .
\n General purpose bucket - To ensure that data is not corrupted traversing the network, use the\n Content-MD5 header. When you use this header, Amazon S3 checks the object\n against the provided MD5 value and, if they do not match, Amazon S3 returns an error. Alternatively, when the object's ETag is its MD5 digest, \n you can calculate the MD5 while putting the object to Amazon S3 and compare the returned ETag to\n the calculated MD5 value.
\n Directory bucket - This functionality is not supported for directory buckets.
\n\n Directory buckets - The HTTP Host header syntax is \n Bucket_name.s3express-az_id.region.amazonaws.com.
For more information about related Amazon S3 APIs, see the following:
\n\n CopyObject\n
\n\n DeleteObject\n
\nThe query string to run. Parameter\n names can be specified in the query string @ character followed by an\n identifier. The named Parameter @scheduled_runtime is reserved and can be used in the query to get the time at which the query is scheduled to run.
The timestamp calculated according to the ScheduleConfiguration parameter, will be the value of @scheduled_runtime paramater for each query run. \n For example, consider an instance of a scheduled query executing on 2021-12-01 00:00:00. For this instance, the @scheduled_runtime parameter is \n initialized to the timestamp 2021-12-01 00:00:00 when invoking the query.
The query string to run. Parameter names can be specified in the query string\n @ character followed by an identifier. The named Parameter\n @scheduled_runtime is reserved and can be used in the query to get the\n time at which the query is scheduled to run.
The timestamp calculated according to the ScheduleConfiguration parameter, will be the\n value of @scheduled_runtime paramater for each query run. For example,\n consider an instance of a scheduled query executing on 2021-12-01 00:00:00. For this\n instance, the @scheduled_runtime parameter is initialized to the timestamp\n 2021-12-01 00:00:00 when invoking the query.
Notification configuration for the scheduled query. A notification is sent by\n Timestream when a query run finishes, when the state is updated or when you delete it.
", + "smithy.api#documentation": "Notification configuration for the scheduled query. A notification is sent by\n Timestream when a query run finishes, when the state is updated or when you delete it.\n
", "smithy.api#required": {} } }, @@ -256,14 +256,14 @@ "ClientToken": { "target": "com.amazonaws.timestreamquery#ClientToken", "traits": { - "smithy.api#documentation": "Using a ClientToken makes the call to CreateScheduledQuery idempotent, in other words, making the same request repeatedly will produce the same result. Making \n multiple identical CreateScheduledQuery requests has the same effect as making a single request.\n\n
\n If CreateScheduledQuery is called without a ClientToken, the\n Query SDK generates a ClientToken on your behalf.
After 8 hours, any request with the same ClientToken is treated\n as a new request.
Using a ClientToken makes the call to CreateScheduledQuery idempotent, in other words,\n making the same request repeatedly will produce the same result. Making multiple\n identical CreateScheduledQuery requests has the same effect as making a single request.
\n If CreateScheduledQuery is called without a ClientToken, the\n Query SDK generates a ClientToken on your behalf.
After 8 hours, any request with the same ClientToken is treated\n as a new request.
The ARN for the IAM role that Timestream will assume when running the scheduled query.
", + "smithy.api#documentation": "The ARN for the IAM role that Timestream will assume when running the scheduled query.\n
", "smithy.api#required": {} } }, @@ -276,13 +276,13 @@ "KmsKeyId": { "target": "com.amazonaws.timestreamquery#StringValue2048", "traits": { - "smithy.api#documentation": "The Amazon KMS key used to encrypt the scheduled query resource, at-rest. If the Amazon KMS\n key is not specified, the scheduled query resource will be encrypted with a Timestream\n owned Amazon KMS key. To specify a KMS key, use the key ID, key ARN, alias name, or alias\n ARN. When using an alias name, prefix the name with alias/\n
\nIf ErrorReportConfiguration uses SSE_KMS as encryption type, the same KmsKeyId is used to encrypt the error report at rest.
The Amazon KMS key used to encrypt the scheduled query resource, at-rest. If the\n Amazon KMS key is not specified, the scheduled query resource will be encrypted with a\n Timestream owned Amazon KMS key. To specify a KMS key, use the key ID, key ARN, alias\n name, or alias ARN. When using an alias name, prefix the name with\n alias/\n
\nIf ErrorReportConfiguration uses SSE_KMS as encryption type, the same\n KmsKeyId is used to encrypt the error report at rest.
Configuration for error reporting. Error reports will be generated when a problem is encountered when writing the query results.
", + "smithy.api#documentation": "Configuration for error reporting. Error reports will be generated when a problem is\n encountered when writing the query results.
", "smithy.api#required": {} } } @@ -666,7 +666,7 @@ "InvocationTime": { "target": "com.amazonaws.timestreamquery#Time", "traits": { - "smithy.api#documentation": "The timestamp in UTC. Query will be run as if it was invoked at this timestamp.
", + "smithy.api#documentation": "The timestamp in UTC. Query will be run as if it was invoked at this timestamp.\n
", "smithy.api#required": {} } }, @@ -689,7 +689,7 @@ "target": "com.amazonaws.timestreamquery#Long", "traits": { "smithy.api#default": 0, - "smithy.api#documentation": "Total time, measured in milliseconds, that was needed for the scheduled query run to complete.
" + "smithy.api#documentation": "Total time, measured in milliseconds, that was needed for the scheduled query run to\n complete.
" } }, "DataWrites": { @@ -780,7 +780,7 @@ "aws.api#clientDiscoveredEndpoint": { "required": true }, - "smithy.api#documentation": "Gets a list of all scheduled queries in the caller's Amazon account and Region. ListScheduledQueries is eventually consistent.
Gets a list of all scheduled queries in the caller's Amazon account and Region.\n ListScheduledQueries is eventually consistent.
Notification configuration for a scheduled query. A notification is sent by\n Timestream when a scheduled query is created, its state is updated or when it is deleted.
" + "smithy.api#documentation": "Notification configuration for a scheduled query. A notification is sent by Timestream\n when a scheduled query is created, its state is updated or when it is deleted.
" } }, "com.amazonaws.timestreamquery#NullableBoolean": { @@ -1180,7 +1180,7 @@ "aws.api#clientDiscoveredEndpoint": { "required": true }, - "smithy.api#documentation": "A synchronous operation that allows you to submit a query with parameters to be stored\n by Timestream for later running. Timestream only supports using this operation with the\n PrepareQueryRequest$ValidateOnly set to true.
A synchronous operation that allows you to submit a query with parameters to be stored\n by Timestream for later running. Timestream only supports using this operation with\n ValidateOnly set to true.
InvocationTime for this run. This is the time at which the query is scheduled to run.\n Parameter @scheduled_runtime can be used in the query to get the value.
InvocationTime for this run. This is the time at which the query is scheduled to run.\n Parameter @scheduled_runtime can be used in the query to get the value.\n
Name of Timestream table that the query result will be written to. The table should\n be within the same database that is provided in Timestream configuration.
", + "smithy.api#documentation": "Name of Timestream table that the query result will be written to. The table should be\n within the same database that is provided in Timestream configuration.
", "smithy.api#required": {} } }, @@ -3020,7 +3020,7 @@ "ScalarType": { "target": "com.amazonaws.timestreamquery#ScalarType", "traits": { - "smithy.api#documentation": "Indicates if the column is of type string, integer, Boolean, double, timestamp, date,\n time.
" + "smithy.api#documentation": "Indicates if the column is of type string, integer, Boolean, double, timestamp, date,\n time. For more information, see Supported data\n types.
" } }, "ArrayColumnInfo": { diff --git a/examples/cross_service/detect_faces/Cargo.toml b/examples/cross_service/detect_faces/Cargo.toml index 0ecde7d29244..957a62278770 100644 --- a/examples/cross_service/detect_faces/Cargo.toml +++ b/examples/cross_service/detect_faces/Cargo.toml @@ -8,7 +8,7 @@ publish = false [dependencies] aws-config= { version = "1.1.8", path = "../../../sdk/aws-config" } aws-sdk-rekognition= { version = "1.18.0", path = "../../../sdk/rekognition" } -aws-sdk-s3= { version = "1.19.1", path = "../../../sdk/s3" } +aws-sdk-s3= { version = "1.20.0", path = "../../../sdk/s3" } aws-smithy-types= { version = "1.1.8", path = "../../../sdk/aws-smithy-types", features = ["rt-tokio"] } [dependencies.tokio] diff --git a/examples/cross_service/detect_labels/Cargo.toml b/examples/cross_service/detect_labels/Cargo.toml index be88f50c3153..9cb119906211 100644 --- a/examples/cross_service/detect_labels/Cargo.toml +++ b/examples/cross_service/detect_labels/Cargo.toml @@ -10,7 +10,7 @@ kamadak-exif = "0.5.4" aws-config= { version = "1.1.8", path = "../../../sdk/aws-config" } aws-sdk-dynamodb= { version = "1.18.0", path = "../../../sdk/dynamodb" } aws-sdk-rekognition= { version = "1.18.0", path = "../../../sdk/rekognition" } -aws-sdk-s3= { version = "1.19.1", path = "../../../sdk/s3" } +aws-sdk-s3= { version = "1.20.0", path = "../../../sdk/s3" } aws-smithy-types= { version = "1.1.8", path = "../../../sdk/aws-smithy-types", features = ["rt-tokio"] } aws-types= { version = "1.1.8", path = "../../../sdk/aws-types" } diff --git a/examples/cross_service/photo_asset_management/Cargo.toml b/examples/cross_service/photo_asset_management/Cargo.toml index 0a47bd78181c..404877530293 100644 --- a/examples/cross_service/photo_asset_management/Cargo.toml +++ b/examples/cross_service/photo_asset_management/Cargo.toml @@ -33,7 +33,7 @@ tracing = "0.1.37" aws-config= { version = "1.1.8", path = "../../../sdk/aws-config" } aws-sdk-dynamodb= { version = "1.18.0", path = "../../../sdk/dynamodb" } aws-sdk-rekognition= { version = "1.18.0", path = "../../../sdk/rekognition" } -aws-sdk-s3= { version = "1.19.1", path = "../../../sdk/s3" } +aws-sdk-s3= { version = "1.20.0", path = "../../../sdk/s3" } aws-sdk-sns= { version = "1.18.0", path = "../../../sdk/sns" } aws-smithy-runtime= { version = "1.1.8", path = "../../../sdk/aws-smithy-runtime" } aws-smithy-types-convert= { version = "0.60.8", path = "../../../sdk/aws-smithy-types-convert", features = ["convert-chrono"] } diff --git a/examples/cross_service/telephone/Cargo.toml b/examples/cross_service/telephone/Cargo.toml index 7144d162ecd7..b8c1355ba4ad 100644 --- a/examples/cross_service/telephone/Cargo.toml +++ b/examples/cross_service/telephone/Cargo.toml @@ -13,7 +13,7 @@ reqwest = "0.11.4" serde_json = "1.0" aws-config= { version = "1.1.8", path = "../../../sdk/aws-config" } aws-sdk-polly= { version = "1.18.0", path = "../../../sdk/polly" } -aws-sdk-s3= { version = "1.19.1", path = "../../../sdk/s3" } +aws-sdk-s3= { version = "1.20.0", path = "../../../sdk/s3" } aws-sdk-transcribe= { version = "1.17.0", path = "../../../sdk/transcribe" } aws-smithy-types= { version = "1.1.8", path = "../../../sdk/aws-smithy-types", features = ["rt-tokio"] } diff --git a/examples/examples/aurora/Cargo.toml b/examples/examples/aurora/Cargo.toml index 2d58ddfff76a..6851099d799d 100644 --- a/examples/examples/aurora/Cargo.toml +++ b/examples/examples/aurora/Cargo.toml @@ -16,7 +16,7 @@ tracing = "0.1.37" aws-config= { version = "1.1.8", path = "../../../sdk/aws-config", features = ["behavior-version-latest"] } aws-smithy-types= { version = "1.1.8", path = "../../../sdk/aws-smithy-types" } aws-smithy-runtime-api= { version = "1.2.0", path = "../../../sdk/aws-smithy-runtime-api" } -aws-sdk-rds= { version = "1.23.0", path = "../../../sdk/rds" } +aws-sdk-rds= { version = "1.24.0", path = "../../../sdk/rds" } [dependencies.phf] version = "0.11.2" diff --git a/examples/examples/cloudformation/Cargo.toml b/examples/examples/cloudformation/Cargo.toml index 85b01c194647..fa7880539939 100644 --- a/examples/examples/cloudformation/Cargo.toml +++ b/examples/examples/cloudformation/Cargo.toml @@ -8,7 +8,7 @@ publish = false [dependencies] aws-config= { version = "1.1.8", path = "../../../sdk/aws-config", features = ["behavior-version-latest"] } -aws-sdk-cloudformation= { version = "1.20.0", path = "../../../sdk/cloudformation" } +aws-sdk-cloudformation= { version = "1.21.0", path = "../../../sdk/cloudformation" } [dependencies.tokio] version = "1.20.1" diff --git a/examples/examples/concurrency/Cargo.toml b/examples/examples/concurrency/Cargo.toml index a76cf952eba5..16cc70e043de 100644 --- a/examples/examples/concurrency/Cargo.toml +++ b/examples/examples/concurrency/Cargo.toml @@ -26,5 +26,5 @@ features = ["env-filter"] [dev-dependencies] fastrand = "1.8.0" aws-config= { version = "1.1.8", path = "../../../sdk/aws-config" } -aws-sdk-s3= { version = "1.19.1", path = "../../../sdk/s3" } +aws-sdk-s3= { version = "1.20.0", path = "../../../sdk/s3" } aws-sdk-sqs= { version = "1.17.0", path = "../../../sdk/sqs" } diff --git a/examples/examples/custom-root-certificates/Cargo.toml b/examples/examples/custom-root-certificates/Cargo.toml index f8b0fae1b494..c21a3afaf310 100644 --- a/examples/examples/custom-root-certificates/Cargo.toml +++ b/examples/examples/custom-root-certificates/Cargo.toml @@ -10,7 +10,7 @@ publish = false [dependencies] rustls = "0.21.9" aws-config= { version = "1.1.8", path = "../../../sdk/aws-config", features = ["behavior-version-latest"] } -aws-sdk-s3= { version = "1.19.1", path = "../../../sdk/s3", default-features = false } +aws-sdk-s3= { version = "1.20.0", path = "../../../sdk/s3", default-features = false } aws-smithy-runtime= { version = "1.1.8", path = "../../../sdk/aws-smithy-runtime", features = ["tls-rustls"] } [dependencies.tokio] diff --git a/examples/examples/glue/Cargo.toml b/examples/examples/glue/Cargo.toml index ceadf45880ed..38f07d4d38e1 100644 --- a/examples/examples/glue/Cargo.toml +++ b/examples/examples/glue/Cargo.toml @@ -20,7 +20,7 @@ futures = "0.3.25" tracing-bunyan-formatter = "0.3.4" aws-config= { version = "1.1.8", path = "../../../sdk/aws-config", features = ["behavior-version-latest"] } aws-sdk-glue= { version = "1.21.0", path = "../../../sdk/glue" } -aws-sdk-s3= { version = "1.19.1", path = "../../../sdk/s3" } +aws-sdk-s3= { version = "1.20.0", path = "../../../sdk/s3" } aws-http= { version = "0.60.5", path = "../../../sdk/aws-http" } aws-smithy-types= { version = "1.1.8", path = "../../../sdk/aws-smithy-types" } aws-types= { version = "1.1.8", path = "../../../sdk/aws-types" } diff --git a/examples/examples/iam/Cargo.toml b/examples/examples/iam/Cargo.toml index 13a00deb913f..688a77528afb 100644 --- a/examples/examples/iam/Cargo.toml +++ b/examples/examples/iam/Cargo.toml @@ -24,7 +24,7 @@ lazy_static = "1.4.0" aws-config= { version = "1.1.8", path = "../../../sdk/aws-config", features = ["behavior-version-latest"] } aws-credential-types= { version = "1.1.8", path = "../../../sdk/aws-credential-types", features = ["hardcoded-credentials"] } aws-sdk-iam= { version = "1.17.0", path = "../../../sdk/iam" } -aws-sdk-s3= { version = "1.19.1", path = "../../../sdk/s3" } +aws-sdk-s3= { version = "1.20.0", path = "../../../sdk/s3" } aws-sdk-sts= { version = "1.17.0", path = "../../../sdk/sts" } [dependencies.sdk-examples-test-utils] diff --git a/examples/examples/kms/Cargo.toml b/examples/examples/kms/Cargo.toml index b32210e837fb..34474da8fd0f 100644 --- a/examples/examples/kms/Cargo.toml +++ b/examples/examples/kms/Cargo.toml @@ -10,7 +10,7 @@ publish = false [dependencies] base64 = "0.13.0" aws-config= { version = "1.1.8", path = "../../../sdk/aws-config", features = ["behavior-version-latest"] } -aws-sdk-kms= { version = "1.17.0", path = "../../../sdk/kms" } +aws-sdk-kms= { version = "1.18.0", path = "../../../sdk/kms" } [dependencies.tokio] version = "1.20.1" diff --git a/examples/examples/lambda/Cargo.toml b/examples/examples/lambda/Cargo.toml index 1ab312fdb977..b10675dcb3ba 100644 --- a/examples/examples/lambda/Cargo.toml +++ b/examples/examples/lambda/Cargo.toml @@ -15,7 +15,7 @@ aws-config= { version = "1.1.8", path = "../../../sdk/aws-config", features = [" aws-sdk-ec2= { version = "1.26.0", path = "../../../sdk/ec2" } aws-sdk-iam= { version = "1.17.0", path = "../../../sdk/iam" } aws-sdk-lambda= { version = "1.17.0", path = "../../../sdk/lambda" } -aws-sdk-s3= { version = "1.19.1", path = "../../../sdk/s3" } +aws-sdk-s3= { version = "1.20.0", path = "../../../sdk/s3" } aws-smithy-types= { version = "1.1.8", path = "../../../sdk/aws-smithy-types" } aws-types= { version = "1.1.8", path = "../../../sdk/aws-types" } diff --git a/examples/examples/localstack/Cargo.toml b/examples/examples/localstack/Cargo.toml index 968b86057bbb..1512e9c24656 100644 --- a/examples/examples/localstack/Cargo.toml +++ b/examples/examples/localstack/Cargo.toml @@ -9,7 +9,7 @@ publish = false [dependencies] http = "0.2" aws-config= { version = "1.1.8", path = "../../../sdk/aws-config", features = ["behavior-version-latest"] } -aws-sdk-s3= { version = "1.19.1", path = "../../../sdk/s3" } +aws-sdk-s3= { version = "1.20.0", path = "../../../sdk/s3" } aws-sdk-sqs= { version = "1.17.0", path = "../../../sdk/sqs" } [dependencies.tokio] diff --git a/examples/examples/rds/Cargo.toml b/examples/examples/rds/Cargo.toml index b4ff83f90d47..578f1e6af036 100644 --- a/examples/examples/rds/Cargo.toml +++ b/examples/examples/rds/Cargo.toml @@ -16,7 +16,7 @@ secrecy = "0.8.0" tracing = "0.1.37" aws-config= { version = "1.1.8", path = "../../../sdk/aws-config", features = ["behavior-version-latest"] } aws-smithy-runtime-api= { version = "1.2.0", path = "../../../sdk/aws-smithy-runtime-api" } -aws-sdk-rds= { version = "1.23.0", path = "../../../sdk/rds" } +aws-sdk-rds= { version = "1.24.0", path = "../../../sdk/rds" } [dependencies.clap] version = "~4.4" diff --git a/examples/examples/s3/Cargo.toml b/examples/examples/s3/Cargo.toml index af04b5194194..19224371f486 100644 --- a/examples/examples/s3/Cargo.toml +++ b/examples/examples/s3/Cargo.toml @@ -31,7 +31,7 @@ tokio-stream = "0.1.8" tracing = "0.1.37" serde_json = "1" aws-config= { version = "1.1.8", path = "../../../sdk/aws-config", features = ["behavior-version-latest"] } -aws-sdk-s3= { version = "1.19.1", path = "../../../sdk/s3", features = ["rt-tokio"] } +aws-sdk-s3= { version = "1.20.0", path = "../../../sdk/s3", features = ["rt-tokio"] } aws-smithy-runtime= { version = "1.1.8", path = "../../../sdk/aws-smithy-runtime" } aws-smithy-runtime-api= { version = "1.2.0", path = "../../../sdk/aws-smithy-runtime-api", features = ["client"] } aws-smithy-types= { version = "1.1.8", path = "../../../sdk/aws-smithy-types", features = ["http-body-0-4-x"] } diff --git a/examples/examples/sdk-config/Cargo.toml b/examples/examples/sdk-config/Cargo.toml index 1df51864f3ac..1d637b39abd0 100644 --- a/examples/examples/sdk-config/Cargo.toml +++ b/examples/examples/sdk-config/Cargo.toml @@ -12,7 +12,7 @@ async_once = "0.2.6" tracing = "0.1.37" aws-config= { version = "1.1.8", path = "../../../sdk/aws-config", features = ["behavior-version-latest"] } aws-credential-types= { version = "1.1.8", path = "../../../sdk/aws-credential-types" } -aws-sdk-s3= { version = "1.19.1", path = "../../../sdk/s3" } +aws-sdk-s3= { version = "1.20.0", path = "../../../sdk/s3" } [dependencies.tokio] version = "1.20.1" diff --git a/examples/examples/sending-presigned-requests/Cargo.toml b/examples/examples/sending-presigned-requests/Cargo.toml index 8efa24d8a22a..eee195108c5d 100644 --- a/examples/examples/sending-presigned-requests/Cargo.toml +++ b/examples/examples/sending-presigned-requests/Cargo.toml @@ -12,7 +12,7 @@ hyper = "0.14" reqwest = "0.11" hyper-tls = "0.5.0" aws-config= { version = "1.1.8", path = "../../../sdk/aws-config", features = ["behavior-version-latest"] } -aws-sdk-s3= { version = "1.19.1", path = "../../../sdk/s3" } +aws-sdk-s3= { version = "1.20.0", path = "../../../sdk/s3" } [dependencies.clap] version = "~4.4" diff --git a/examples/examples/testing/Cargo.toml b/examples/examples/testing/Cargo.toml index ec84491aaccd..313295023b1a 100644 --- a/examples/examples/testing/Cargo.toml +++ b/examples/examples/testing/Cargo.toml @@ -17,7 +17,7 @@ mockall = "0.11.4" serde_json = "1" aws-config= { version = "1.1.8", path = "../../../sdk/aws-config", features = ["behavior-version-latest"] } aws-credential-types= { version = "1.1.8", path = "../../../sdk/aws-credential-types", features = ["hardcoded-credentials"] } -aws-sdk-s3= { version = "1.19.1", path = "../../../sdk/s3" } +aws-sdk-s3= { version = "1.20.0", path = "../../../sdk/s3" } aws-smithy-types= { version = "1.1.8", path = "../../../sdk/aws-smithy-types" } aws-smithy-runtime= { version = "1.1.8", path = "../../../sdk/aws-smithy-runtime", features = ["test-util"] } aws-smithy-runtime-api= { version = "1.2.0", path = "../../../sdk/aws-smithy-runtime-api", features = ["test-util"] } diff --git a/examples/examples/tls/Cargo.toml b/examples/examples/tls/Cargo.toml index f3c2c773b9b6..cc5f81ffa6e0 100644 --- a/examples/examples/tls/Cargo.toml +++ b/examples/examples/tls/Cargo.toml @@ -18,7 +18,7 @@ webpki-roots = "0.22.4" rustls = "0.20.6" aws-config= { version = "1.1.8", path = "../../../sdk/aws-config", features = ["behavior-version-latest"] } aws-smithy-runtime= { version = "1.1.8", path = "../../../sdk/aws-smithy-runtime" } -aws-sdk-kms= { version = "1.17.0", path = "../../../sdk/kms", default-features = false } +aws-sdk-kms= { version = "1.18.0", path = "../../../sdk/kms", default-features = false } [dependencies.tokio] version = "1.20.1" diff --git a/examples/lambda/calculator/Cargo.toml b/examples/lambda/calculator/Cargo.toml index 773fcb2ed723..1113daf114ff 100644 --- a/examples/lambda/calculator/Cargo.toml +++ b/examples/lambda/calculator/Cargo.toml @@ -16,7 +16,7 @@ serde = "1.0.164" aws-config= { version = "1.1.8", path = "../../../sdk/aws-config" } aws-sdk-ec2= { version = "1.26.0", path = "../../../sdk/ec2" } aws-sdk-lambda= { version = "1.17.0", path = "../../../sdk/lambda" } -aws-sdk-s3= { version = "1.19.1", path = "../../../sdk/s3" } +aws-sdk-s3= { version = "1.20.0", path = "../../../sdk/s3" } [dependencies.clap] version = "~4.4" diff --git a/index.md b/index.md index b6417fea3226..65b8b6d2faa0 100644 --- a/index.md +++ b/index.md @@ -88,7 +88,6 @@ The AWS SDK for Rust contains one crate for each AWS service, as well as [aws-co | AWS IoT FleetWise | [aws-sdk-iotfleetwise](https://crates.io/crates/aws-sdk-iotfleetwise) ([docs](https://docs.rs/aws-sdk-iotfleetwise)) | | AWS IoT Greengrass V2 | [aws-sdk-greengrassv2](https://crates.io/crates/aws-sdk-greengrassv2) ([docs](https://docs.rs/aws-sdk-greengrassv2)) | | AWS IoT Jobs Data Plane | [aws-sdk-iotjobsdataplane](https://crates.io/crates/aws-sdk-iotjobsdataplane) ([docs](https://docs.rs/aws-sdk-iotjobsdataplane)) | -| AWS IoT RoboRunner | [aws-sdk-iotroborunner](https://crates.io/crates/aws-sdk-iotroborunner) ([docs](https://docs.rs/aws-sdk-iotroborunner)) | | AWS IoT Secure Tunneling | [aws-sdk-iotsecuretunneling](https://crates.io/crates/aws-sdk-iotsecuretunneling) ([docs](https://docs.rs/aws-sdk-iotsecuretunneling)) | | AWS IoT SiteWise | [aws-sdk-iotsitewise](https://crates.io/crates/aws-sdk-iotsitewise) ([docs](https://docs.rs/aws-sdk-iotsitewise)) | | AWS IoT Things Graph | [aws-sdk-iotthingsgraph](https://crates.io/crates/aws-sdk-iotthingsgraph) ([docs](https://docs.rs/aws-sdk-iotthingsgraph)) | diff --git a/sdk/cloudformation/Cargo.toml b/sdk/cloudformation/Cargo.toml index 697e2ff5935c..78935b823f40 100644 --- a/sdk/cloudformation/Cargo.toml +++ b/sdk/cloudformation/Cargo.toml @@ -1,7 +1,7 @@ # Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT. [package] name = "aws-sdk-cloudformation" -version = "1.20.0" +version = "1.21.0" authors = ["AWS Rust SDK TeamThe rollback triggers for CloudFormation to monitor during stack creation and updating operations, and for the specified monitoring period afterwards.
The amount of time that can pass before the stack status becomes CREATE_FAILED; if DisableRollback is not set or is set to false, the stack will be rolled back.
The Amazon Simple Notification Service (Amazon SNS) topic ARNs to publish stack related events. You can find your Amazon SNS topic ARNs using the Amazon SNS console or your Command Line Interface (CLI).
In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order for CloudFormation to create the stack.
CAPABILITY_IAM and CAPABILITY_NAMED_IAM
Some stack templates might include resources that can affect permissions in your Amazon Web Services account; for example, by creating new Identity and Access Management (IAM) users. For those stacks, you must explicitly acknowledge this by specifying one of these capabilities.
The following IAM resources require you to specify either the CAPABILITY_IAM or CAPABILITY_NAMED_IAM capability.
If you have IAM resources, you can specify either capability.
If you have IAM resources with custom names, you must specify CAPABILITY_NAMED_IAM.
If you don't specify either of these capabilities, CloudFormation returns an InsufficientCapabilities error.
If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
For more information, see Acknowledging IAM Resources in CloudFormation Templates.
CAPABILITY_AUTO_EXPAND
Some template contain macros. Macros perform custom processing on templates; this can include simple actions like find-and-replace operations, all the way to extensive transformations of entire templates. Because of this, users typically create a change set from the processed template, so that they can review the changes resulting from the macros before actually creating the stack. If your stack template contains one or more macros, and you choose to create a stack directly from the processed template, without first reviewing the resulting changes in a change set, you must acknowledge this capability. This includes the AWS::Include and AWS::Serverless transforms, which are macros hosted by CloudFormation.
If you want to create a stack from a stack template that contains macros and nested stacks, you must create the stack directly from the template using this capability.
You should only create stacks directly from a stack template that contains macros if you know what processing the macro performs.
Each macro relies on an underlying Lambda service function for processing stack templates. Be aware that the Lambda function owner can update the function operation without CloudFormation being notified.
For more information, see Using CloudFormation macros to perform custom processing on templates.
Only one of the Capabilities and ResourceType parameters can be specified.
In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order for CloudFormation to create the stack.
CAPABILITY_IAM and CAPABILITY_NAMED_IAM
Some stack templates might include resources that can affect permissions in your Amazon Web Services account; for example, by creating new Identity and Access Management (IAM) users. For those stacks, you must explicitly acknowledge this by specifying one of these capabilities.
The following IAM resources require you to specify either the CAPABILITY_IAM or CAPABILITY_NAMED_IAM capability.
If you have IAM resources, you can specify either capability.
If you have IAM resources with custom names, you must specify CAPABILITY_NAMED_IAM.
If you don't specify either of these capabilities, CloudFormation returns an InsufficientCapabilities error.
If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
For more information, see Acknowledging IAM Resources in CloudFormation Templates.
CAPABILITY_AUTO_EXPAND
Some template contain macros. Macros perform custom processing on templates; this can include simple actions like find-and-replace operations, all the way to extensive transformations of entire templates. Because of this, users typically create a change set from the processed template, so that they can review the changes resulting from the macros before actually creating the stack. If your stack template contains one or more macros, and you choose to create a stack directly from the processed template, without first reviewing the resulting changes in a change set, you must acknowledge this capability. This includes the AWS::Include and AWS::Serverless transforms, which are macros hosted by CloudFormation.
If you want to create a stack from a stack template that contains macros and nested stacks, you must create the stack directly from the template using this capability.
You should only create stacks directly from a stack template that contains macros if you know what processing the macro performs.
Each macro relies on an underlying Lambda service function for processing stack templates. Be aware that the Lambda function owner can update the function operation without CloudFormation being notified.
For more information, see Using CloudFormation macros to perform custom processing on templates.
Only one of the Capabilities and ResourceType parameters can be specified.
The template resource types that you have permissions to work with for this create stack action, such as AWS::EC2::Instance, AWS::EC2::*, or Custom::MyCustomInstance. Use the following syntax to describe template resource types: AWS::* (for all Amazon Web Services resources), Custom::* (for all custom resources), Custom::logical_ID (for a specific custom resource), AWS::service_name::* (for all resources of a particular Amazon Web Services service), and AWS::service_name::resource_logical_ID (for a specific Amazon Web Services resource).
If the list of resource types doesn't include a resource that you're creating, the stack creation fails. By default, CloudFormation grants permissions to all resource types. Identity and Access Management (IAM) uses this parameter for CloudFormation-specific condition keys in IAM policies. For more information, see Controlling Access with Identity and Access Management.
Only one of the Capabilities and ResourceType parameters can be specified.
The Amazon Resource Name (ARN) of an Identity and Access Management (IAM) role that CloudFormation assumes to create the stack. CloudFormation uses the role's credentials to make calls on your behalf. CloudFormation always uses this role for all future operations on the stack. Provided that users have permission to operate on the stack, CloudFormation uses this role even if the users don't have permission to pass it. Ensure that the role grants least privilege.
If you don't specify a value, CloudFormation uses the role that was previously associated with the stack. If no role is available, CloudFormation uses a temporary session that's generated from your user credentials.
Determines what action will be taken if stack creation fails. This must be one of: DO_NOTHING, ROLLBACK, or DELETE. You can specify either OnFailure or DisableRollback, but not both.
Default: ROLLBACK
The name or unique ID of the stack set that you want to get automatic deployment targets for.
A string that identifies the next page of stack set deployment targets that you want to retrieve.
The maximum number of results to be returned with a single call. If the number of available results exceeds this maximum, the response includes a NextToken value that you can assign to the NextToken request parameter to get the next set of results.
Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF is specified. Use SELF for StackSets with self-managed permissions.
If you are signed in to the management account, specify SELF.
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
An array of summaries of the deployment targets for the stack set.
+ /// - [`next_token(OptionIf the request doesn't return all the remaining results, NextToken is set to a token. To retrieve the next set of results, call ListStackSetAutoDeploymentTargets again and use that value for the NextToken parameter. If the request returns all results, NextToken is set to an empty string.
If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
///If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
///If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
///If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
///If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
///If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
///If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
///If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
///The specified stack set doesn't exist.
+ StackSetNotFoundException(crate::types::error::StackSetNotFoundException), /// An unexpected error occurred (e.g., invalid JSON returned by the service or an unknown error code). #[deprecated(note = "Matching `Unhandled` directly is not forwards compatible. Instead, match using a \ variable wildcard pattern and check `.code()`: \ `err if err.code() == Some(\"SpecificExceptionCode\") => { /* handle the error */ }` \ - See [`ProvideErrorMetadata`](#impl-ProvideErrorMetadata-for-UpdateSiteError) for what information is available for the error.")] + See [`ProvideErrorMetadata`](#impl-ProvideErrorMetadata-for-ListStackSetAutoDeploymentTargetsError) for what information is available for the error.")] Unhandled(crate::error::sealed_unhandled::Unhandled), } -impl UpdateSiteError { - /// Creates the `UpdateSiteError::Unhandled` variant from any error type. +impl ListStackSetAutoDeploymentTargetsError { + /// Creates the `ListStackSetAutoDeploymentTargetsError::Unhandled` variant from any error type. pub fn unhandled( err: impl ::std::convert::Into<::std::boxed::BoxThe name or unique ID of the stack set that you want to get automatic deployment targets for.
+ pub stack_set_name: ::std::option::Option<::std::string::String>, + ///A string that identifies the next page of stack set deployment targets that you want to retrieve.
+ pub next_token: ::std::option::Option<::std::string::String>, + ///The maximum number of results to be returned with a single call. If the number of available results exceeds this maximum, the response includes a NextToken value that you can assign to the NextToken request parameter to get the next set of results.
Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
+ ///By default, SELF is specified. Use SELF for StackSets with self-managed permissions.
If you are signed in to the management account, specify SELF.
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
The name or unique ID of the stack set that you want to get automatic deployment targets for.
+ pub fn stack_set_name(&self) -> ::std::option::Option<&str> { + self.stack_set_name.as_deref() + } + ///A string that identifies the next page of stack set deployment targets that you want to retrieve.
+ pub fn next_token(&self) -> ::std::option::Option<&str> { + self.next_token.as_deref() + } + ///The maximum number of results to be returned with a single call. If the number of available results exceeds this maximum, the response includes a NextToken value that you can assign to the NextToken request parameter to get the next set of results.
Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
+ ///By default, SELF is specified. Use SELF for StackSets with self-managed permissions.
If you are signed in to the management account, specify SELF.
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
The name or unique ID of the stack set that you want to get automatic deployment targets for.
+ /// This field is required. + pub fn stack_set_name(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self { + self.stack_set_name = ::std::option::Option::Some(input.into()); + self + } + ///The name or unique ID of the stack set that you want to get automatic deployment targets for.
+ pub fn set_stack_set_name(mut self, input: ::std::option::Option<::std::string::String>) -> Self { + self.stack_set_name = input; + self + } + ///The name or unique ID of the stack set that you want to get automatic deployment targets for.
+ pub fn get_stack_set_name(&self) -> &::std::option::Option<::std::string::String> { + &self.stack_set_name + } + ///A string that identifies the next page of stack set deployment targets that you want to retrieve.
+ pub fn next_token(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self { + self.next_token = ::std::option::Option::Some(input.into()); + self + } + ///A string that identifies the next page of stack set deployment targets that you want to retrieve.
+ pub fn set_next_token(mut self, input: ::std::option::Option<::std::string::String>) -> Self { + self.next_token = input; + self + } + ///A string that identifies the next page of stack set deployment targets that you want to retrieve.
+ pub fn get_next_token(&self) -> &::std::option::Option<::std::string::String> { + &self.next_token + } + ///The maximum number of results to be returned with a single call. If the number of available results exceeds this maximum, the response includes a NextToken value that you can assign to the NextToken request parameter to get the next set of results.
The maximum number of results to be returned with a single call. If the number of available results exceeds this maximum, the response includes a NextToken value that you can assign to the NextToken request parameter to get the next set of results.
The maximum number of results to be returned with a single call. If the number of available results exceeds this maximum, the response includes a NextToken value that you can assign to the NextToken request parameter to get the next set of results.
Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
+ ///By default, SELF is specified. Use SELF for StackSets with self-managed permissions.
If you are signed in to the management account, specify SELF.
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
+ ///By default, SELF is specified. Use SELF for StackSets with self-managed permissions.
If you are signed in to the management account, specify SELF.
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
+ ///By default, SELF is specified. Use SELF for StackSets with self-managed permissions.
If you are signed in to the management account, specify SELF.
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
An array of summaries of the deployment targets for the stack set.
+ pub summaries: ::std::option::Option<::std::vec::VecIf the request doesn't return all the remaining results, NextToken is set to a token. To retrieve the next set of results, call ListStackSetAutoDeploymentTargets again and use that value for the NextToken parameter. If the request returns all results, NextToken is set to an empty string.
An array of summaries of the deployment targets for the stack set.
+ /// + /// If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use `.summaries.is_none()`. + pub fn summaries(&self) -> &[crate::types::StackSetAutoDeploymentTargetSummary] { + self.summaries.as_deref().unwrap_or_default() + } + ///If the request doesn't return all the remaining results, NextToken is set to a token. To retrieve the next set of results, call ListStackSetAutoDeploymentTargets again and use that value for the NextToken parameter. If the request returns all results, NextToken is set to an empty string.
An array of summaries of the deployment targets for the stack set.
+ pub fn summaries(mut self, input: crate::types::StackSetAutoDeploymentTargetSummary) -> Self { + let mut v = self.summaries.unwrap_or_default(); + v.push(input); + self.summaries = ::std::option::Option::Some(v); + self + } + ///An array of summaries of the deployment targets for the stack set.
+ pub fn set_summaries(mut self, input: ::std::option::Option<::std::vec::VecAn array of summaries of the deployment targets for the stack set.
+ pub fn get_summaries(&self) -> &::std::option::Option<::std::vec::VecIf the request doesn't return all the remaining results, NextToken is set to a token. To retrieve the next set of results, call ListStackSetAutoDeploymentTargets again and use that value for the NextToken parameter. If the request returns all results, NextToken is set to an empty string.
If the request doesn't return all the remaining results, NextToken is set to a token. To retrieve the next set of results, call ListStackSetAutoDeploymentTargets again and use that value for the NextToken parameter. If the request returns all results, NextToken is set to an empty string.
If the request doesn't return all the remaining results, NextToken is set to a token. To retrieve the next set of results, call ListStackSetAutoDeploymentTargets again and use that value for the NextToken parameter. If the request returns all results, NextToken is set to an empty string.
Returns summary information about deployment targets for a stack set.
+#[derive(::std::clone::Clone, ::std::fmt::Debug)] +pub struct ListStackSetAutoDeploymentTargetsFluentBuilder { + handle: ::std::sync::ArcThe name or unique ID of the stack set that you want to get automatic deployment targets for.
+ pub fn stack_set_name(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self { + self.inner = self.inner.stack_set_name(input.into()); + self + } + ///The name or unique ID of the stack set that you want to get automatic deployment targets for.
+ pub fn set_stack_set_name(mut self, input: ::std::option::Option<::std::string::String>) -> Self { + self.inner = self.inner.set_stack_set_name(input); + self + } + ///The name or unique ID of the stack set that you want to get automatic deployment targets for.
+ pub fn get_stack_set_name(&self) -> &::std::option::Option<::std::string::String> { + self.inner.get_stack_set_name() + } + ///A string that identifies the next page of stack set deployment targets that you want to retrieve.
+ pub fn next_token(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self { + self.inner = self.inner.next_token(input.into()); + self + } + ///A string that identifies the next page of stack set deployment targets that you want to retrieve.
+ pub fn set_next_token(mut self, input: ::std::option::Option<::std::string::String>) -> Self { + self.inner = self.inner.set_next_token(input); + self + } + ///A string that identifies the next page of stack set deployment targets that you want to retrieve.
+ pub fn get_next_token(&self) -> &::std::option::Option<::std::string::String> { + self.inner.get_next_token() + } + ///The maximum number of results to be returned with a single call. If the number of available results exceeds this maximum, the response includes a NextToken value that you can assign to the NextToken request parameter to get the next set of results.
The maximum number of results to be returned with a single call. If the number of available results exceeds this maximum, the response includes a NextToken value that you can assign to the NextToken request parameter to get the next set of results.
The maximum number of results to be returned with a single call. If the number of available results exceeds this maximum, the response includes a NextToken value that you can assign to the NextToken request parameter to get the next set of results.
Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
+ ///By default, SELF is specified. Use SELF for StackSets with self-managed permissions.
If you are signed in to the management account, specify SELF.
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
+ ///By default, SELF is specified. Use SELF for StackSets with self-managed permissions.
If you are signed in to the management account, specify SELF.
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
+ ///By default, SELF is specified. Use SELF for StackSets with self-managed permissions.
If you are signed in to the management account, specify SELF.
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
FAILED: The operation in the specified account and Region failed. If the stack set operation fails in enough accounts within a Region, the failure tolerance for the stack set operation as a whole might be exceeded.
FAILED_IMPORT: The import of the stack instance in the specified account and Region failed and left the stack in an unstable state. Once the issues causing the failure are fixed, the import operation can be retried. If enough stack set operations fail in enough accounts within a Region, the failure tolerance for the stack set operation as a whole might be exceeded.
INOPERABLE: A DeleteStackInstances operation has failed and left the stack in an unstable state. Stacks in this state are excluded from further UpdateStackSet operations. You might need to perform a DeleteStackInstances operation, with RetainStacks set to true, to delete the stack instance, and then delete the stack manually.
PENDING: The operation in the specified account and Region has yet to start.
FAILED: The operation in the specified account and Region failed. If the stack set operation fails in enough accounts within a Region, the failure tolerance for the stack set operation as a whole might be exceeded.
FAILED_IMPORT: The import of the stack instance in the specified account and Region failed and left the stack in an unstable state. Once the issues causing the failure are fixed, the import operation can be retried. If enough stack set operations fail in enough accounts within a Region, the failure tolerance for the stack set operation as a whole might be exceeded.
INOPERABLE: A DeleteStackInstances operation has failed and left the stack in an unstable state. Stacks in this state are excluded from further UpdateStackSet operations. You might need to perform a DeleteStackInstances operation, with RetainStacks set to true, to delete the stack instance, and then delete the stack manually.
PENDING: The operation in the specified account and Region has yet to start.
FAILED: The operation in the specified account and Region failed. If the stack set operation fails in enough accounts within a Region, the failure tolerance for the stack set operation as a whole might be exceeded.
FAILED_IMPORT: The import of the stack instance in the specified account and Region failed and left the stack in an unstable state. Once the issues causing the failure are fixed, the import operation can be retried. If enough stack set operations fail in enough accounts within a Region, the failure tolerance for the stack set operation as a whole might be exceeded.
INOPERABLE: A DeleteStackInstances operation has failed and left the stack in an unstable state. Stacks in this state are excluded from further UpdateStackSet operations. You might need to perform a DeleteStackInstances operation, with RetainStacks set to true, to delete the stack instance, and then delete the stack manually.
PENDING: The operation in the specified account and Region has yet to start.
FAILED: The operation in the specified account and Region failed. If the stack set operation fails in enough accounts within a Region, the failure tolerance for the stack set operation as a whole might be exceeded.
FAILED_IMPORT: The import of the stack instance in the specified account and Region failed and left the stack in an unstable state. Once the issues causing the failure are fixed, the import operation can be retried. If enough stack set operations fail in enough accounts within a Region, the failure tolerance for the stack set operation as a whole might be exceeded.
INOPERABLE: A DeleteStackInstances operation has failed and left the stack in an unstable state. Stacks in this state are excluded from further UpdateStackSet operations. You might need to perform a DeleteStackInstances operation, with RetainStacks set to true, to delete the stack instance, and then delete the stack manually.
PENDING: The operation in the specified account and Region has yet to start.
FAILED: The operation in the specified account and Region failed. If the stack set operation fails in enough accounts within a Region, the failure tolerance for the stack set operation as a whole might be exceeded.
FAILED_IMPORT: The import of the stack instance in the specified account and Region failed and left the stack in an unstable state. Once the issues causing the failure are fixed, the import operation can be retried. If enough stack set operations fail in enough accounts within a Region, the failure tolerance for the stack set operation as a whole might be exceeded.
INOPERABLE: A DeleteStackInstances operation has failed and left the stack in an unstable state. Stacks in this state are excluded from further UpdateStackSet operations. You might need to perform a DeleteStackInstances operation, with RetainStacks set to true, to delete the stack instance, and then delete the stack manually.
PENDING: The operation in the specified account and Region has yet to start.
One of the targets for the stack set. Returned by the ListStackSetAutoDeploymentTargets API operation.
The organization root ID or organizational unit (OU) IDs where the stack set is targeted.
+ pub organizational_unit_id: ::std::option::Option<::std::string::String>, + ///The list of Regions targeted for this organization or OU.
+ pub regions: ::std::option::Option<::std::vec::Vec<::std::string::String>>, +} +impl StackSetAutoDeploymentTargetSummary { + ///The organization root ID or organizational unit (OU) IDs where the stack set is targeted.
+ pub fn organizational_unit_id(&self) -> ::std::option::Option<&str> { + self.organizational_unit_id.as_deref() + } + ///The list of Regions targeted for this organization or OU.
+ /// + /// If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use `.regions.is_none()`. + pub fn regions(&self) -> &[::std::string::String] { + self.regions.as_deref().unwrap_or_default() + } +} +impl StackSetAutoDeploymentTargetSummary { + /// Creates a new builder-style object to manufacture [`StackSetAutoDeploymentTargetSummary`](crate::types::StackSetAutoDeploymentTargetSummary). + pub fn builder() -> crate::types::builders::StackSetAutoDeploymentTargetSummaryBuilder { + crate::types::builders::StackSetAutoDeploymentTargetSummaryBuilder::default() + } +} + +/// A builder for [`StackSetAutoDeploymentTargetSummary`](crate::types::StackSetAutoDeploymentTargetSummary). +#[non_exhaustive] +#[derive(::std::clone::Clone, ::std::cmp::PartialEq, ::std::default::Default, ::std::fmt::Debug)] +pub struct StackSetAutoDeploymentTargetSummaryBuilder { + pub(crate) organizational_unit_id: ::std::option::Option<::std::string::String>, + pub(crate) regions: ::std::option::Option<::std::vec::Vec<::std::string::String>>, +} +impl StackSetAutoDeploymentTargetSummaryBuilder { + ///The organization root ID or organizational unit (OU) IDs where the stack set is targeted.
+ pub fn organizational_unit_id(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self { + self.organizational_unit_id = ::std::option::Option::Some(input.into()); + self + } + ///The organization root ID or organizational unit (OU) IDs where the stack set is targeted.
+ pub fn set_organizational_unit_id(mut self, input: ::std::option::Option<::std::string::String>) -> Self { + self.organizational_unit_id = input; + self + } + ///The organization root ID or organizational unit (OU) IDs where the stack set is targeted.
+ pub fn get_organizational_unit_id(&self) -> &::std::option::Option<::std::string::String> { + &self.organizational_unit_id + } + /// Appends an item to `regions`. + /// + /// To override the contents of this collection use [`set_regions`](Self::set_regions). + /// + ///The list of Regions targeted for this organization or OU.
+ pub fn regions(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self { + let mut v = self.regions.unwrap_or_default(); + v.push(input.into()); + self.regions = ::std::option::Option::Some(v); + self + } + ///The list of Regions targeted for this organization or OU.
+ pub fn set_regions(mut self, input: ::std::option::Option<::std::vec::Vec<::std::string::String>>) -> Self { + self.regions = input; + self + } + ///The list of Regions targeted for this organization or OU.
+ pub fn get_regions(&self) -> &::std::option::Option<::std::vec::Vec<::std::string::String>> { + &self.regions + } + /// Consumes the builder and constructs a [`StackSetAutoDeploymentTargetSummary`](crate::types::StackSetAutoDeploymentTargetSummary). + pub fn build(self) -> crate::types::StackSetAutoDeploymentTargetSummary { + crate::types::StackSetAutoDeploymentTargetSummary { + organizational_unit_id: self.organizational_unit_id, + regions: self.regions, + } + } +} diff --git a/sdk/cloudformation/src/types/builders.rs b/sdk/cloudformation/src/types/builders.rs index f2a79fdb1977..9727354b557a 100644 --- a/sdk/cloudformation/src/types/builders.rs +++ b/sdk/cloudformation/src/types/builders.rs @@ -41,6 +41,8 @@ pub use crate::types::_account_gate_result::AccountGateResultBuilder; pub use crate::types::_operation_result_filter::OperationResultFilterBuilder; +pub use crate::types::_stack_set_auto_deployment_target_summary::StackSetAutoDeploymentTargetSummaryBuilder; + pub use crate::types::_stack_summary::StackSummaryBuilder; pub use crate::types::_stack_drift_information_summary::StackDriftInformationSummaryBuilder; diff --git a/sdk/iotroborunner/Cargo.toml b/sdk/iotroborunner/Cargo.toml deleted file mode 100644 index 4af9186387ac..000000000000 --- a/sdk/iotroborunner/Cargo.toml +++ /dev/null @@ -1,89 +0,0 @@ -# Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT. -[package] -name = "aws-sdk-iotroborunner" -version = "1.17.0" -authors = ["AWS Rust SDK Team