diff --git a/src/services/appintegrations.jl b/src/services/appintegrations.jl index a20437eb5d..b073428030 100644 --- a/src/services/appintegrations.jl +++ b/src/services/appintegrations.jl @@ -5,38 +5,58 @@ using AWS.Compat using AWS.UUIDs """ - create_data_integration(name) - create_data_integration(name, params::Dict{String,<:Any}) + create_data_integration(kms_key, name, schedule_config, source_uri) + create_data_integration(kms_key, name, schedule_config, source_uri, params::Dict{String,<:Any}) Creates and persists a DataIntegration resource. You cannot create a DataIntegration association for a DataIntegration that has been previously associated. Use a different DataIntegration, or recreate the DataIntegration using the CreateDataIntegration API. # Arguments +- `kms_key`: The KMS key for the DataIntegration. - `name`: The name of the DataIntegration. +- `schedule_config`: The name of the data and how often it should be pulled from the source. +- `source_uri`: The URI of the data source. # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: - `"ClientToken"`: A unique, case-sensitive identifier that you provide to ensure the - idempotency of the request. + idempotency of the request. If not provided, the Amazon Web Services SDK populates this + field. For more information about idempotency, see Making retries safe with idempotent APIs. - `"Description"`: A description of the DataIntegration. -- `"KmsKey"`: The KMS key for the DataIntegration. -- `"ScheduleConfig"`: The name of the data and how often it should be pulled from the - source. -- `"SourceURI"`: The URI of the data source. -- `"Tags"`: One or more tags. +- `"FileConfiguration"`: The configuration for what files should be pulled from the source. +- `"ObjectConfiguration"`: The configuration for what data should be pulled from the source. +- `"Tags"`: The tags used to organize, track, or control access for this resource. For + example, { \"tags\": {\"key1\":\"value1\", \"key2\":\"value2\"} }. """ -function create_data_integration(Name; aws_config::AbstractAWSConfig=global_aws_config()) +function create_data_integration( + KmsKey, + Name, + ScheduleConfig, + SourceURI; + aws_config::AbstractAWSConfig=global_aws_config(), +) return appintegrations( "POST", "/dataIntegrations", - Dict{String,Any}("Name" => Name, "ClientToken" => string(uuid4())); + Dict{String,Any}( + "KmsKey" => KmsKey, + "Name" => Name, + "ScheduleConfig" => ScheduleConfig, + "SourceURI" => SourceURI, + "ClientToken" => string(uuid4()), + ); aws_config=aws_config, feature_set=SERVICE_FEATURE_SET, ) end function create_data_integration( - Name, params::AbstractDict{String}; aws_config::AbstractAWSConfig=global_aws_config() + KmsKey, + Name, + ScheduleConfig, + SourceURI, + params::AbstractDict{String}; + aws_config::AbstractAWSConfig=global_aws_config(), ) return appintegrations( "POST", @@ -44,7 +64,13 @@ function create_data_integration( Dict{String,Any}( mergewith( _merge, - Dict{String,Any}("Name" => Name, "ClientToken" => string(uuid4())), + Dict{String,Any}( + "KmsKey" => KmsKey, + "Name" => Name, + "ScheduleConfig" => ScheduleConfig, + "SourceURI" => SourceURI, + "ClientToken" => string(uuid4()), + ), params, ), ); @@ -70,9 +96,11 @@ the EventIntegration control plane. # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: - `"ClientToken"`: A unique, case-sensitive identifier that you provide to ensure the - idempotency of the request. + idempotency of the request. If not provided, the Amazon Web Services SDK populates this + field. For more information about idempotency, see Making retries safe with idempotent APIs. - `"Description"`: The description of the event integration. -- `"Tags"`: One or more tags. +- `"Tags"`: The tags used to organize, track, or control access for this resource. For + example, { \"tags\": {\"key1\":\"value1\", \"key2\":\"value2\"} }. """ function create_event_integration( EventBridgeBus, EventFilter, Name; aws_config::AbstractAWSConfig=global_aws_config() @@ -433,7 +461,8 @@ Adds the specified tags to the specified resource. # Arguments - `resource_arn`: The Amazon Resource Name (ARN) of the resource. -- `tags`: One or more tags. +- `tags`: The tags used to organize, track, or control access for this resource. For + example, { \"tags\": {\"key1\":\"value1\", \"key2\":\"value2\"} }. """ function tag_resource(resourceArn, tags; aws_config::AbstractAWSConfig=global_aws_config()) diff --git a/src/services/application_auto_scaling.jl b/src/services/application_auto_scaling.jl index 9457d14dc0..f3d037a043 100644 --- a/src/services/application_auto_scaling.jl +++ b/src/services/application_auto_scaling.jl @@ -843,6 +843,45 @@ function describe_scheduled_actions( ) end +""" + list_tags_for_resource(resource_arn) + list_tags_for_resource(resource_arn, params::Dict{String,<:Any}) + +Returns all the tags on the specified Application Auto Scaling scalable target. For general +information about tags, including the format and syntax, see Tagging Amazon Web Services +resources in the Amazon Web Services General Reference. + +# Arguments +- `resource_arn`: Specify the ARN of the scalable target. For example: + arn:aws:application-autoscaling:us-east-1:123456789012:scalable-target/1234abcd56ab78cd901ef + 1234567890ab123 To get the ARN for a scalable target, use DescribeScalableTargets. + +""" +function list_tags_for_resource( + ResourceARN; aws_config::AbstractAWSConfig=global_aws_config() +) + return application_auto_scaling( + "ListTagsForResource", + Dict{String,Any}("ResourceARN" => ResourceARN); + aws_config=aws_config, + feature_set=SERVICE_FEATURE_SET, + ) +end +function list_tags_for_resource( + ResourceARN, + params::AbstractDict{String}; + aws_config::AbstractAWSConfig=global_aws_config(), +) + return application_auto_scaling( + "ListTagsForResource", + Dict{String,Any}( + mergewith(_merge, Dict{String,Any}("ResourceARN" => ResourceARN), params) + ); + aws_config=aws_config, + feature_set=SERVICE_FEATURE_SET, + ) +end + """ put_scaling_policy(policy_name, resource_id, scalable_dimension, service_namespace) put_scaling_policy(policy_name, resource_id, scalable_dimension, service_namespace, params::Dict{String,<:Any}) @@ -866,7 +905,7 @@ tracking policy is ready to scale in, the scale-in activity will not be blocked. scale-in activity completes, the target tracking policy could instruct the scalable target to scale out again. For more information, see Target tracking scaling policies and Step scaling policies in the Application Auto Scaling User Guide. If a scalable target is -deregistered, the scalable target is no longer available to execute scaling policies. Any +deregistered, the scalable target is no longer available to use scaling policies. Any scaling policies that were specified for the scalable target are deleted. # Arguments @@ -1009,7 +1048,7 @@ Creates or updates a scheduled action for an Application Auto Scaling scalable t Each scalable target is identified by a service namespace, resource ID, and scalable dimension. A scheduled action applies to the scalable target identified by those three attributes. You cannot create a scheduled action until you have registered the resource as -a scalable target. When start and end times are specified with a recurring schedule using a +a scalable target. When you specify start and end times with a recurring schedule using a cron expression or rates, they form the boundaries for when the recurring action starts and stops. To update a scheduled action, specify the parameters that you want to change. If you don't specify start and end times, the old values are deleted. For more information, see @@ -1161,13 +1200,13 @@ end register_scalable_target(resource_id, scalable_dimension, service_namespace) register_scalable_target(resource_id, scalable_dimension, service_namespace, params::Dict{String,<:Any}) -Registers or updates a scalable target, the resource that you want to scale. Scalable -targets are uniquely identified by the combination of resource ID, scalable dimension, and -namespace, which represents some capacity dimension of the underlying service. When you -register a new scalable target, you must specify values for the minimum and maximum -capacity. If the specified resource is not active in the target service, this operation -does not change the resource's current capacity. Otherwise, it changes the resource's -current capacity to a value that is inside of this range. If you choose to add a scaling +Registers or updates a scalable target, which is the resource that you want to scale. +Scalable targets are uniquely identified by the combination of resource ID, scalable +dimension, and namespace, which represents some capacity dimension of the underlying +service. When you register a new scalable target, you must specify values for the minimum +and maximum capacity. If the specified resource is not active in the target service, this +operation does not change the resource's current capacity. Otherwise, it changes the +resource's current capacity to a value that is inside of this range. If you add a scaling policy, current capacity is adjustable within the specified range when scaling starts. Application Auto Scaling scaling policies will not scale capacity to values that are outside of the minimum and maximum range. After you register a scalable target, you do not @@ -1178,11 +1217,15 @@ scalable target, you can deregister it by using DeregisterScalableTarget. To upd scalable target, specify the parameters that you want to change. Include the parameters that identify the scalable target: resource ID, scalable dimension, and namespace. Any parameters that you don't specify are not changed by this update request. If you call the -RegisterScalableTarget API to update an existing scalable target, Application Auto Scaling -retrieves the current capacity of the resource. If it is below the minimum capacity or -above the maximum capacity, Application Auto Scaling adjusts the capacity of the scalable -target to place it within these bounds, even if you don't include the MinCapacity or -MaxCapacity request parameters. +RegisterScalableTarget API operation to create a scalable target, there might be a brief +delay until the operation achieves eventual consistency. You might become aware of this +brief delay if you get unexpected errors when performing sequential operations. The typical +strategy is to retry the request, and some Amazon Web Services SDKs include automatic +backoff and retry logic. If you call the RegisterScalableTarget API operation to update an +existing scalable target, Application Auto Scaling retrieves the current capacity of the +resource. If it's below the minimum capacity or above the maximum capacity, Application +Auto Scaling adjusts the capacity of the scalable target to place it within these bounds, +even if you don't include the MinCapacity or MaxCapacity request parameters. # Arguments - `resource_id`: The identifier of the resource that is associated with the scalable @@ -1260,7 +1303,7 @@ Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys is in effect, Application Auto Scaling can scale out (expand) as needed to the maximum capacity limit in response to changing demand. This property is required when registering a new scalable target. Although you can specify a large maximum capacity, note that service - quotas may impose lower limits. Each service has its own default quotas for the maximum + quotas might impose lower limits. Each service has its own default quotas for the maximum capacity of the resource. If you want to specify a higher limit, you can request an increase. For more information, consult the documentation for that service. For information about the default quotas for each service, see Service endpoints and quotas in the Amazon @@ -1293,6 +1336,12 @@ Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys ScheduledScalingSuspended, while a suspension is in effect, all scaling activities that involve scheduled actions are suspended. For more information, see Suspending and resuming scaling in the Application Auto Scaling User Guide. +- `"Tags"`: Assigns one or more tags to the scalable target. Use this parameter to tag the + scalable target when it is created. To tag an existing scalable target, use the TagResource + operation. Each tag consists of a tag key and a tag value. Both the tag key and the tag + value are required. You cannot have more than one tag on a scalable target with the same + tag key. Use tags to control access to a scalable target. For more information, see Tagging + support for Application Auto Scaling in the Application Auto Scaling User Guide. """ function register_scalable_target( ResourceId, @@ -1335,3 +1384,105 @@ function register_scalable_target( feature_set=SERVICE_FEATURE_SET, ) end + +""" + tag_resource(resource_arn, tags) + tag_resource(resource_arn, tags, params::Dict{String,<:Any}) + +Adds or edits tags on an Application Auto Scaling scalable target. Each tag consists of a +tag key and a tag value, which are both case-sensitive strings. To add a tag, specify a new +tag key and a tag value. To edit a tag, specify an existing tag key and a new tag value. +You can use this operation to tag an Application Auto Scaling scalable target, but you +cannot tag a scaling policy or scheduled action. You can also add tags to an Application +Auto Scaling scalable target while creating it (RegisterScalableTarget). For general +information about tags, including the format and syntax, see Tagging Amazon Web Services +resources in the Amazon Web Services General Reference. Use tags to control access to a +scalable target. For more information, see Tagging support for Application Auto Scaling in +the Application Auto Scaling User Guide. + +# Arguments +- `resource_arn`: Identifies the Application Auto Scaling scalable target that you want to + apply tags to. For example: + arn:aws:application-autoscaling:us-east-1:123456789012:scalable-target/1234abcd56ab78cd901ef + 1234567890ab123 To get the ARN for a scalable target, use DescribeScalableTargets. +- `tags`: The tags assigned to the resource. A tag is a label that you assign to an AWS + resource. Each tag consists of a tag key and a tag value. You cannot have more than one tag + on an Application Auto Scaling scalable target with the same tag key. If you specify an + existing tag key with a different tag value, Application Auto Scaling replaces the current + tag value with the specified one. For information about the rules that apply to tag keys + and tag values, see User-defined tag restrictions in the Amazon Web Services Billing and + Cost Management User Guide. + +""" +function tag_resource(ResourceARN, Tags; aws_config::AbstractAWSConfig=global_aws_config()) + return application_auto_scaling( + "TagResource", + Dict{String,Any}("ResourceARN" => ResourceARN, "Tags" => Tags); + aws_config=aws_config, + feature_set=SERVICE_FEATURE_SET, + ) +end +function tag_resource( + ResourceARN, + Tags, + params::AbstractDict{String}; + aws_config::AbstractAWSConfig=global_aws_config(), +) + return application_auto_scaling( + "TagResource", + Dict{String,Any}( + mergewith( + _merge, + Dict{String,Any}("ResourceARN" => ResourceARN, "Tags" => Tags), + params, + ), + ); + aws_config=aws_config, + feature_set=SERVICE_FEATURE_SET, + ) +end + +""" + untag_resource(resource_arn, tag_keys) + untag_resource(resource_arn, tag_keys, params::Dict{String,<:Any}) + +Deletes tags from an Application Auto Scaling scalable target. To delete a tag, specify the +tag key and the Application Auto Scaling scalable target. + +# Arguments +- `resource_arn`: Identifies the Application Auto Scaling scalable target from which to + remove tags. For example: + arn:aws:application-autoscaling:us-east-1:123456789012:scalable-target/1234abcd56ab78cd901ef + 1234567890ab123 To get the ARN for a scalable target, use DescribeScalableTargets. +- `tag_keys`: One or more tag keys. Specify only the tag keys, not the tag values. + +""" +function untag_resource( + ResourceARN, TagKeys; aws_config::AbstractAWSConfig=global_aws_config() +) + return application_auto_scaling( + "UntagResource", + Dict{String,Any}("ResourceARN" => ResourceARN, "TagKeys" => TagKeys); + aws_config=aws_config, + feature_set=SERVICE_FEATURE_SET, + ) +end +function untag_resource( + ResourceARN, + TagKeys, + params::AbstractDict{String}; + aws_config::AbstractAWSConfig=global_aws_config(), +) + return application_auto_scaling( + "UntagResource", + Dict{String,Any}( + mergewith( + _merge, + Dict{String,Any}("ResourceARN" => ResourceARN, "TagKeys" => TagKeys), + params, + ), + ); + aws_config=aws_config, + feature_set=SERVICE_FEATURE_SET, + ) +end diff --git a/src/services/config_service.jl b/src/services/config_service.jl index a5c50dbd7b..f4b60da560 100644 --- a/src/services/config_service.jl +++ b/src/services/config_service.jl @@ -955,8 +955,7 @@ results. This can occur if the resources were deleted or removed from the rule's # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: -- `"ComplianceTypes"`: Filters the results by compliance. The allowed values are COMPLIANT - and NON_COMPLIANT. +- `"ComplianceTypes"`: Filters the results by compliance. - `"ConfigRuleNames"`: Specify one or more Config rule names to filter the results by rule. - `"NextToken"`: The nextToken string returned on a previous page that you use to get the next page of results in a paginated response. @@ -1002,8 +1001,7 @@ the resources were deleted or removed from the rule's scope. # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: -- `"ComplianceTypes"`: Filters the results by compliance. The allowed values are COMPLIANT, - NON_COMPLIANT, and INSUFFICIENT_DATA. +- `"ComplianceTypes"`: Filters the results by compliance. - `"Limit"`: The maximum number of evaluation results returned on each page. The default is 10. You cannot specify a number greater than 100. If you specify 0, Config uses the default. - `"NextToken"`: The nextToken string returned on a previous page that you use to get the @@ -1085,8 +1083,9 @@ Returns details about your Config rules. Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: - `"ConfigRuleNames"`: The names of the Config rules for which you want details. If you do not specify any names, Config returns details for all your rules. -- `"Filters"`: Returns a list of Detecive or Proactive Config rules. By default, this API - returns an unfiltered list. +- `"Filters"`: Returns a list of Detective or Proactive Config rules. By default, this API + returns an unfiltered list. For more information on Detective or Proactive Config rules, + see Evaluation Mode in the Config Developer Guide. - `"NextToken"`: The nextToken string returned on a previous page that you use to get the next page of results in a paginated response. """ @@ -1199,10 +1198,12 @@ end describe_configuration_recorder_status() describe_configuration_recorder_status(params::Dict{String,<:Any}) -Returns the current status of the specified configuration recorder. If a configuration -recorder is not specified, this action returns the status of all configuration recorders -associated with the account. Currently, you can specify only one configuration recorder -per region in your account. +Returns the current status of the specified configuration recorder as well as the status of +the last recording event for the recorder. If a configuration recorder is not specified, +this action returns the status of all configuration recorders associated with the account. +Currently, you can specify only one configuration recorder per region in your account. For +a detailed status of recording events over time, add your Config events to Amazon +CloudWatch metrics and use CloudWatch metrics. # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: @@ -2116,8 +2117,9 @@ evaluated, and whether each resource complies with the rule. # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: -- `"ComplianceTypes"`: Filters the results by compliance. The allowed values are COMPLIANT, - NON_COMPLIANT, and NOT_APPLICABLE. +- `"ComplianceTypes"`: Filters the results by compliance. INSUFFICIENT_DATA is a valid + ComplianceType that is returned when an Config rule cannot be evaluated. However, + INSUFFICIENT_DATA cannot be used as a ComplianceType for filtering results. - `"Limit"`: The maximum number of evaluation results returned on each page. The default is 10. You cannot specify a number greater than 100. If you specify 0, Config uses the default. - `"NextToken"`: The nextToken string returned on a previous page that you use to get the @@ -2158,8 +2160,9 @@ invoked, and whether the resource complies with each rule. # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: -- `"ComplianceTypes"`: Filters the results by compliance. The allowed values are COMPLIANT, - NON_COMPLIANT, and NOT_APPLICABLE. +- `"ComplianceTypes"`: Filters the results by compliance. INSUFFICIENT_DATA is a valid + ComplianceType that is returned when an Config rule cannot be evaluated. However, + INSUFFICIENT_DATA cannot be used as a ComplianceType for filtering results. - `"NextToken"`: The nextToken string returned on a previous page that you use to get the next page of results in a paginated response. - `"ResourceEvaluationId"`: The unique ID of Amazon Web Services resource execution for @@ -2644,6 +2647,9 @@ Returns a summary of resource evaluation for the specified resource evaluation I proactive rules that were run. The results indicate which evaluation context was used to evaluate the rules, which resource details were evaluated, the evaluation mode that was run, and whether the resource details comply with the configuration of the proactive rules. + To see additional information about the evaluation result, such as which rule flagged a +resource as NON_COMPLIANT, use the GetComplianceDetailsByResource API. For more +information, see the Examples section. # Arguments - `resource_evaluation_id`: The unique ResourceEvaluationId of Amazon Web Services resource @@ -2792,7 +2798,7 @@ Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys - `"Filters"`: Filters the results based on the ConformancePackComplianceScoresFilters. - `"Limit"`: The maximum number of conformance pack compliance scores returned on each page. - `"NextToken"`: The nextToken string in a prior request that you can use to get the - paginated response for next set of conformance pack compliance scores. + paginated response for the next set of conformance pack compliance scores. - `"SortBy"`: Sorts your conformance pack compliance scores in either ascending or descending order, depending on SortOrder. By default, conformance pack compliance scores are sorted in alphabetical order by name of the conformance pack. Enter SCORE, to sort @@ -2855,7 +2861,8 @@ Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys next page of results in a paginated response. - `"resourceIds"`: The IDs of only those resources that you want Config to list in the response. If you do not specify this parameter, Config lists all resources of the specified - type that it has discovered. + type that it has discovered. You can list a minimum of 1 resourceID and a maximum of 20 + resourceIds. - `"resourceName"`: The custom name of only those resources that you want Config to list in the response. If you do not specify this parameter, Config lists all resources of the specified type that it has discovered. @@ -2989,7 +2996,11 @@ end put_aggregation_authorization(authorized_account_id, authorized_aws_region, params::Dict{String,<:Any}) Authorizes the aggregator account and region to collect data from the source account and -region. +region. PutAggregationAuthorization is an idempotent API. Subsequent requests won’t +create a duplicate resource if one was already created. If a following request has +different tags values, Config will ignore these differences and treat it as an idempotent +request of the previous. In this case, tags will not be updated, even if they are +different. # Arguments - `authorized_account_id`: The 12-digit account ID of the account authorized to aggregate @@ -3045,25 +3056,30 @@ end Adds or updates an Config rule to evaluate if your Amazon Web Services resources comply with your desired configurations. For information on how many Config rules you can have per account, see Service Limits in the Config Developer Guide. There are two types of rules: -Config Custom Rules and Config Managed Rules. You can use PutConfigRule to create both -Config custom rules and Config managed rules. Custom rules are rules that you can create -using either Guard or Lambda functions. Guard (Guard GitHub Repository) is a policy-as-code -language that allows you to write policies that are enforced by Config Custom Policy rules. -Lambda uses custom code that you upload to evaluate a custom rule. If you are adding a new -Custom Lambda rule, you first need to create an Lambda function that the rule invokes to -evaluate your resources. When you use PutConfigRule to add a Custom Lambda rule to Config, -you must specify the Amazon Resource Name (ARN) that Lambda assigns to the function. You -specify the ARN in the SourceIdentifier key. This key is part of the Source object, which -is part of the ConfigRule object. Managed rules are predefined, customizable rules created -by Config. For a list of managed rules, see List of Config Managed Rules. If you are adding -an Config managed rule, you must specify the rule's identifier for the SourceIdentifier -key. For any new rule that you add, specify the ConfigRuleName in the ConfigRule object. Do -not specify the ConfigRuleArn or the ConfigRuleId. These values are generated by Config for -new rules. If you are updating a rule that you added previously, you can specify the rule -by ConfigRuleName, ConfigRuleId, or ConfigRuleArn in the ConfigRule data type that you use -in this request. For more information about developing and using Config rules, see -Evaluating Amazon Web Services resource Configurations with Config in the Config Developer -Guide. +Config Managed Rules and Config Custom Rules. You can use PutConfigRule to create both +Config Managed Rules and Config Custom Rules. Config Managed Rules are predefined, +customizable rules created by Config. For a list of managed rules, see List of Config +Managed Rules. If you are adding an Config managed rule, you must specify the rule's +identifier for the SourceIdentifier key. Config Custom Rules are rules that you create from +scratch. There are two ways to create Config custom rules: with Lambda functions ( Lambda +Developer Guide) and with Guard (Guard GitHub Repository), a policy-as-code language. +Config custom rules created with Lambda are called Config Custom Lambda Rules and Config +custom rules created with Guard are called Config Custom Policy Rules. If you are adding a +new Config Custom Lambda rule, you first need to create an Lambda function that the rule +invokes to evaluate your resources. When you use PutConfigRule to add a Custom Lambda rule +to Config, you must specify the Amazon Resource Name (ARN) that Lambda assigns to the +function. You specify the ARN in the SourceIdentifier key. This key is part of the Source +object, which is part of the ConfigRule object. For any new Config rule that you add, +specify the ConfigRuleName in the ConfigRule object. Do not specify the ConfigRuleArn or +the ConfigRuleId. These values are generated by Config for new rules. If you are updating a +rule that you added previously, you can specify the rule by ConfigRuleName, ConfigRuleId, +or ConfigRuleArn in the ConfigRule data type that you use in this request. For more +information about developing and using Config rules, see Evaluating Resources with Config +Rules in the Config Developer Guide. PutConfigRule is an idempotent API. Subsequent +requests won’t create a duplicate resource if one was already created. If a following +request has different tags values, Config will ignore these differences and treat it as an +idempotent request of the previous. In this case, tags will not be updated, even if they +are different. # Arguments - `config_rule`: The rule that you want to add to your account. @@ -3111,7 +3127,11 @@ EnableAwsServiceAccess API to enable integration between Config and Organization caller is a registered delegated administrator, Config calls ListDelegatedAdministrators API to verify whether the caller is a valid delegated administrator. To register a delegated administrator, see Register a Delegated Administrator in the Config developer -guide. +guide. PutConfigurationAggregator is an idempotent API. Subsequent requests won’t +create a duplicate resource if one was already created. If a following request has +different tags values, Config will ignore these differences and treat it as an idempotent +request of the previous. In this case, tags will not be updated, even if they are +different. # Arguments - `configuration_aggregator_name`: The name of the configuration aggregator. @@ -3416,22 +3436,23 @@ account of your organization. The service-linked role is created only when the r not exist in the caller account. Config verifies the existence of role with GetRole action. To use this API with delegated administrator, register a delegated administrator by calling Amazon Web Services Organization register-delegated-administrator for -config-multiaccountsetup.amazonaws.com. There are two types of rules: Config Custom Rules -and Config Managed Rules. You can use PutOrganizationConfigRule to create both Config -custom rules and Config managed rules. Custom rules are rules that you can create using -either Guard or Lambda functions. Guard (Guard GitHub Repository) is a policy-as-code -language that allows you to write policies that are enforced by Config Custom Policy rules. -Lambda uses custom code that you upload to evaluate a custom rule. If you are adding a new -Custom Lambda rule, you first need to create an Lambda function in the management account -or a delegated administrator that the rule invokes to evaluate your resources. You also -need to create an IAM role in the managed account that can be assumed by the Lambda -function. When you use PutOrganizationConfigRule to add a Custom Lambda rule to Config, you -must specify the Amazon Resource Name (ARN) that Lambda assigns to the function. Managed -rules are predefined, customizable rules created by Config. For a list of managed rules, -see List of Config Managed Rules. If you are adding an Config managed rule, you must -specify the rule's identifier for the RuleIdentifier key. Prerequisite: Ensure you call -EnableAllFeatures API to enable all features in an organization. Make sure to specify one -of either OrganizationCustomPolicyRuleMetadata for Custom Policy rules, +config-multiaccountsetup.amazonaws.com. There are two types of rules: Config Managed Rules +and Config Custom Rules. You can use PutOrganizationConfigRule to create both Config +Managed Rules and Config Custom Rules. Config Managed Rules are predefined, customizable +rules created by Config. For a list of managed rules, see List of Config Managed Rules. If +you are adding an Config managed rule, you must specify the rule's identifier for the +RuleIdentifier key. Config Custom Rules are rules that you create from scratch. There are +two ways to create Config custom rules: with Lambda functions ( Lambda Developer Guide) and +with Guard (Guard GitHub Repository), a policy-as-code language. Config custom rules +created with Lambda are called Config Custom Lambda Rules and Config custom rules created +with Guard are called Config Custom Policy Rules. If you are adding a new Config Custom +Lambda rule, you first need to create an Lambda function in the management account or a +delegated administrator that the rule invokes to evaluate your resources. You also need to +create an IAM role in the managed account that can be assumed by the Lambda function. When +you use PutOrganizationConfigRule to add a Custom Lambda rule to Config, you must specify +the Amazon Resource Name (ARN) that Lambda assigns to the function. Prerequisite: Ensure +you call EnableAllFeatures API to enable all features in an organization. Make sure to +specify one of either OrganizationCustomPolicyRuleMetadata for Custom Policy rules, OrganizationCustomRuleMetadata for Custom Lambda rules, or OrganizationManagedRuleMetadata for managed rules. @@ -3622,12 +3643,21 @@ end put_remediation_exceptions(config_rule_name, resource_keys) put_remediation_exceptions(config_rule_name, resource_keys, params::Dict{String,<:Any}) -A remediation exception is when a specific resource is no longer considered for +A remediation exception is when a specified resource is no longer considered for auto-remediation. This API adds a new exception or updates an existing exception for a -specific resource with a specific Config rule. Config generates a remediation exception -when a problem occurs executing a remediation action to a specific resource. Remediation -exceptions blocks auto-remediation until the exception is cleared. To place an exception -on an Amazon Web Services resource, ensure remediation is set as manual remediation. +specified resource with a specified Config rule. Config generates a remediation exception +when a problem occurs running a remediation action for a specified resource. Remediation +exceptions blocks auto-remediation until the exception is cleared. When placing an +exception on an Amazon Web Services resource, it is recommended that remediation is set as +manual remediation until the given Config rule for the specified resource evaluates the +resource as NON_COMPLIANT. Once the resource has been evaluated as NON_COMPLIANT, you can +add remediation exceptions and change the remediation type back from Manual to Auto if you +want to use auto-remediation. Otherwise, using auto-remediation before a NON_COMPLIANT +evaluation result can delete resources before the exception is applied. Placing an +exception can only be performed on resources that are NON_COMPLIANT. If you use this API +for COMPLIANT resources or resources that are NOT_APPLICABLE, a remediation exception will +not be generated. For more information on the conditions that initiate the possible Config +evaluation results, see Concepts | Config Rules in the Config Developer Guide. # Arguments - `config_rule_name`: The name of the Config rule for which you want to create remediation @@ -3806,7 +3836,10 @@ end Saves a new query or updates an existing saved query. The QueryName must be unique for a single Amazon Web Services account and a single Amazon Web Services Region. You can create upto 300 queries in a single Amazon Web Services account and a single Amazon Web Services -Region. +Region. PutStoredQuery is an idempotent API. Subsequent requests won’t create a +duplicate resource if one was already created. If a following request has different tags +values, Config will ignore these differences and treat it as an idempotent request of the +previous. In this case, tags will not be updated, even if they are different. # Arguments - `stored_query`: A list of StoredQuery objects. The mandatory fields are QueryName and @@ -4093,10 +4126,16 @@ details will comply with configured Config rules. You can also use it for evalua purposes. Config recommends using an evaluation context. It runs an execution against the resource details with all of the Config rules in your account that match with the specified proactive mode and resource type. Ensure you have the cloudformation:DescribeType role -setup to validate the resource type schema. +setup to validate the resource type schema. You can find the Resource type schema in +\"Amazon Web Services public extensions\" within the CloudFormation registry or with the +following CLI commmand: aws cloudformation describe-type --type-name \"AWS::S3::Bucket\" +--type RESOURCE. For more information, see Managing extensions through the CloudFormation +registry and Amazon Web Services resource and property types reference in the +CloudFormation User Guide. # Arguments -- `evaluation_mode`: The mode of an evaluation. The valid value for this API is Proactive. +- `evaluation_mode`: The mode of an evaluation. The valid values for this API are DETECTIVE + and PROACTIVE. - `resource_details`: Returns a ResourceDetails object. # Optional Parameters @@ -4193,8 +4232,9 @@ end tag_resource(resource_arn, tags, params::Dict{String,<:Any}) Associates the specified tags to a resource with the specified resourceArn. If existing -tags on a resource are not specified in the request parameters, they are not changed. When -a resource is deleted, the tags associated with that resource are deleted as well. +tags on a resource are not specified in the request parameters, they are not changed. If +existing tags are specified, however, then their values will be updated. When a resource is +deleted, the tags associated with that resource are deleted as well. # Arguments - `resource_arn`: The Amazon Resource Name (ARN) that identifies the resource for which to diff --git a/src/services/direct_connect.jl b/src/services/direct_connect.jl index 78daab0e65..6ec1470b55 100644 --- a/src/services/direct_connect.jl +++ b/src/services/direct_connect.jl @@ -819,9 +819,14 @@ that also use that address family. If logical redundancy is not supported by the connection, interconnect, or LAG, the BGP peer cannot be in the same address family as an existing BGP peer on the virtual interface. When creating a IPv6 BGP peer, omit the Amazon address and customer address. IPv6 addresses are automatically assigned from the Amazon -pool of IPv6 addresses; you cannot specify custom IPv6 addresses. For a public virtual -interface, the Autonomous System Number (ASN) must be private or already on the allow list -for the virtual interface. +pool of IPv6 addresses; you cannot specify custom IPv6 addresses. If you let Amazon Web +Services auto-assign IPv4 addresses, a /30 CIDR will be allocated from 169.254.0.0/16. +Amazon Web Services does not recommend this option if you intend to use the customer router +peer IP address as the source and destination for traffic. Instead you should use RFC 1918 +or other addressing, and specify the address yourself. For more information about RFC 1918 +see Address Allocation for Private Internets. For a public virtual interface, the +Autonomous System Number (ASN) must be private or already on the allow list for the virtual +interface. # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: @@ -1352,13 +1357,14 @@ interface enables the connection of multiple VPCs attached to a transit gateway Connect gateway. If you associate your transit gateway with one or more Direct Connect gateways, the Autonomous System Number (ASN) used by the transit gateway and the Direct Connect gateway must be different. For example, if you use the default ASN 64512 for both -your the transit gateway and Direct Connect gateway, the association request fails. -Setting the MTU of a virtual interface to 8500 (jumbo frames) can cause an update to the -underlying physical connection if it wasn't updated to support jumbo frames. Updating the -connection disrupts network connectivity for all virtual interfaces associated with the -connection for up to 30 seconds. To check whether your connection supports jumbo frames, -call DescribeConnections. To check whether your virtual interface supports jumbo frames, -call DescribeVirtualInterfaces. +your the transit gateway and Direct Connect gateway, the association request fails. A +jumbo MTU value must be either 1500 or 8500. No other values will be accepted. Setting the +MTU of a virtual interface to 8500 (jumbo frames) can cause an update to the underlying +physical connection if it wasn't updated to support jumbo frames. Updating the connection +disrupts network connectivity for all virtual interfaces associated with the connection for +up to 30 seconds. To check whether your connection supports jumbo frames, call +DescribeConnections. To check whether your virtual interface supports jumbo frames, call +DescribeVirtualInterfaces. # Arguments - `connection_id`: The ID of the connection. @@ -2446,7 +2452,7 @@ completes, use StopBgpFailoverTest. Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: - `"bgpPeers"`: The BGP peers to place in the DOWN state. - `"testDurationInMinutes"`: The time in minutes that the virtual interface failover test - will last. Maximum value: 180 minutes (3 hours). Default: 180 minutes (3 hours). + will last. Maximum value: 4,320 minutes (72 hours). Default: 180 minutes (3 hours). """ function start_bgp_failover_test( virtualInterfaceId; aws_config::AbstractAWSConfig=global_aws_config() diff --git a/src/services/guardduty.jl b/src/services/guardduty.jl index 2c38d0b6e7..a97da8757c 100644 --- a/src/services/guardduty.jl +++ b/src/services/guardduty.jl @@ -169,6 +169,7 @@ Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys might be regional differences because some data sources might not be available in all the Amazon Web Services Regions where GuardDuty is presently supported. For more information, see Regions and endpoints. +- `"features"`: A list of features that will be configured for the detector. - `"findingPublishingFrequency"`: A value that specifies how frequently updated findings are exported. - `"tags"`: The tags to be added to a new detector resource. @@ -204,7 +205,9 @@ end create_filter(detector_id, finding_criteria, name) create_filter(detector_id, finding_criteria, name, params::Dict{String,<:Any}) -Creates a filter using the specified finding criteria. +Creates a filter using the specified finding criteria. The maximum number of saved filters +per Amazon Web Services account per Region is 100. For more information, see Quotas for +GuardDuty. # Arguments - `detector_id`: The ID of the detector belonging to the GuardDuty account that you want to @@ -258,8 +261,9 @@ Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys filter. - `"clientToken"`: The idempotency token for the create request. - `"description"`: The description of the filter. Valid characters include alphanumeric - characters, and special characters such as -, ., :, { }, [ ], ( ), /, t, n, x0B, f, r, _, - and whitespace. + characters, and special characters such as hyphen, period, colon, underscore, parentheses + ({ }, [ ], and ( )), forward slash, horizontal tab, vertical tab, newline, form feed, + return, and whitespace. - `"rank"`: Specifies the position of the filter in the list of current filters. Also specifies the order in which this filter is applied to the findings. - `"tags"`: The tags to be added to a new filter resource. @@ -964,6 +968,14 @@ For more information, see Regions and endpoints. - `detector_id`: The ID of the detector to retrieve information about the delegated administrator from. +# Optional Parameters +Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: +- `"maxResults"`: You can use this parameter to indicate the maximum number of items that + you want in the response. +- `"nextToken"`: You can use this parameter when paginating results. Set the value of this + parameter to null on your first call to the list action. For subsequent calls to the + action, fill nextToken in the request with the value of NextToken from the previous + response to continue listing data. """ function describe_organization_configuration( detectorId; aws_config::AbstractAWSConfig=global_aws_config() @@ -2438,6 +2450,7 @@ Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys Regions where GuardDuty is presently supported. For more information, see Regions and endpoints. - `"enable"`: Specifies whether the detector is enabled or not enabled. +- `"features"`: Provides the features that will be updated for the detector. - `"findingPublishingFrequency"`: An enum value that specifies how frequently findings are exported, such as to CloudWatch Events. """ @@ -2660,6 +2673,7 @@ where GuardDuty is presently supported. For more information, see Regions and en # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: - `"dataSources"`: Describes which data sources will be updated. +- `"features"`: A list of features that will be updated for the specified member accounts. """ function update_member_detectors( accountIds, detectorId; aws_config::AbstractAWSConfig=global_aws_config() @@ -2706,6 +2720,7 @@ and endpoints. # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: - `"dataSources"`: Describes which data sources will be updated. +- `"features"`: A list of features that will be configured for the organization. """ function update_organization_configuration( autoEnable, detectorId; aws_config::AbstractAWSConfig=global_aws_config() diff --git a/src/services/iam.jl b/src/services/iam.jl index 91ee1af129..066a53d2a7 100644 --- a/src/services/iam.jl +++ b/src/services/iam.jl @@ -622,16 +622,17 @@ provider. To learn more, see Creating a role for web identity or OpenID connect in the IAM User Guide. When you create the IAM OIDC provider, you specify the following: The URL of the OIDC identity provider (IdP) to trust A list of client IDs (also known as audiences) that identify the application or applications allowed to authenticate using the -OIDC provider A list of thumbprints of one or more server certificates that the IdP uses - You get all of this information from the OIDC IdP you want to use to access Amazon Web -Services. Amazon Web Services secures communication with some OIDC identity providers -(IdPs) through our library of trusted certificate authorities (CAs) instead of using a -certificate thumbprint to verify your IdP server certificate. These OIDC IdPs include -Google, Auth0, and those that use an Amazon S3 bucket to host a JSON Web Key Set (JWKS) -endpoint. In these cases, your legacy thumbprint remains in your configuration, but is no -longer used for validation. The trust for the OIDC provider is derived from the IAM -provider that this operation creates. Therefore, it is best to limit access to the -CreateOpenIDConnectProvider operation to highly privileged users. +OIDC provider A list of tags that are attached to the specified IAM OIDC provider A +list of thumbprints of one or more server certificates that the IdP uses You get all of +this information from the OIDC IdP you want to use to access Amazon Web Services. Amazon +Web Services secures communication with some OIDC identity providers (IdPs) through our +library of trusted certificate authorities (CAs) instead of using a certificate thumbprint +to verify your IdP server certificate. These OIDC IdPs include Google, Auth0, and those +that use an Amazon S3 bucket to host a JSON Web Key Set (JWKS) endpoint. In these cases, +your legacy thumbprint remains in your configuration, but is no longer used for validation. + The trust for the OIDC provider is derived from the IAM provider that this operation +creates. Therefore, it is best to limit access to the CreateOpenIDConnectProvider operation +to highly privileged users. # Arguments - `thumbprint_list`: A list of server certificate thumbprints for the OpenID Connect (OIDC) @@ -645,7 +646,7 @@ CreateOpenIDConnectProvider operation to highly privileged users. stores its keys at https://keys.server.example.com/openid-connect. In that case, the thumbprint string would be the hex-encoded SHA-1 hash value of the certificate used by https://keys.server.example.com. For more information about obtaining the OIDC provider - thumbprint, see Obtaining the thumbprint for an OpenID Connect provider in the IAM User + thumbprint, see Obtaining the thumbprint for an OpenID Connect provider in the IAM user Guide. - `url`: The URL of the identity provider. The URL must begin with https:// and should correspond to the iss claim in the provider's OpenID Connect ID tokens. Per the OIDC @@ -872,7 +873,10 @@ create, see IAM and STS quotas in the IAM User Guide. Upon success, the response includes the same trust policy in JSON format. - `role_name`: The name of the role to create. IAM user, group, role, and policy names must be unique within the account. Names are not distinguished by case. For example, you cannot - create resources named both \"MyResource\" and \"myresource\". + create resources named both \"MyResource\" and \"myresource\". This parameter allows + (through its regex pattern) a string of characters consisting of upper and lowercase + alphanumeric characters with no spaces. You can also include any of the following + characters: _+=,.@- # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: @@ -1196,10 +1200,10 @@ Services access keys or your passwords. After you provision your virtual device, ensure that the information is destroyed following secure procedures. # Arguments -- `virtual_mfadevice_name`: The name of the virtual MFA device. Use with path to uniquely - identify a virtual MFA device. This parameter allows (through its regex pattern) a string - of characters consisting of upper and lowercase alphanumeric characters with no spaces. You - can also include any of the following characters: _+=,.@- +- `virtual_mfadevice_name`: The name of the virtual MFA device, which must be unique. Use + with path to uniquely identify a virtual MFA device. This parameter allows (through its + regex pattern) a string of characters consisting of upper and lowercase alphanumeric + characters with no spaces. You can also include any of the following characters: _+=,.@- # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: @@ -3269,7 +3273,7 @@ information. For details, see GenerateOrganizationsAccessReport. To call this op you must be signed in to the management account in your organization. SCPs must be enabled for your organization root. You must have permissions to perform this operation. For more information, see Refining permissions using service last accessed data in the IAM User -Guide. For each service that principals in an account (root users, IAM users, or IAM roles) +Guide. For each service that principals in an account (root user, IAM users, or IAM roles) could access using SCPs, the operation returns details about the most recent access attempt. If there was no attempt, the service is listed without details about the most recent attempt to access the service. If the operation fails, it returns the reason that it @@ -6779,15 +6783,15 @@ consists of a key name and an associated value. By assigning tags to your resour can do the following: Administrative grouping and discovery - Attach tags to resources to aid in organization and search. For example, you could search for all resources with the key name Project and the value MyImportantProject. Or search for all resources with the key -name Cost Center and the value 41200. Access control - Include tags in IAM user-based -and resource-based policies. You can use tags to restrict access to only an OIDC provider -that has a specified tag attached. For examples of policies that show how to use tags to -control access, see Control access using IAM tags in the IAM User Guide. If any one of -the tags is invalid or if you exceed the allowed maximum number of tags, then the entire -request fails and the resource is not created. For more information about tagging, see -Tagging IAM resources in the IAM User Guide. Amazon Web Services always interprets the -tag Value as a single string. If you need to store an array, you can store comma-separated -values in the string. However, you must interpret the value in your code. +name Cost Center and the value 41200. Access control - Include tags in IAM +identity-based and resource-based policies. You can use tags to restrict access to only an +OIDC provider that has a specified tag attached. For examples of policies that show how to +use tags to control access, see Control access using IAM tags in the IAM User Guide. +If any one of the tags is invalid or if you exceed the allowed maximum number of tags, then +the entire request fails and the resource is not created. For more information about +tagging, see Tagging IAM resources in the IAM User Guide. Amazon Web Services always +interprets the tag Value as a single string. If you need to store an array, you can store +comma-separated values in the string. However, you must interpret the value in your code. # Arguments - `open_idconnect_provider_arn`: The ARN of the OIDC identity provider in IAM to which you @@ -7082,8 +7086,8 @@ value. By assigning tags to your resources, you can do the following: Adminis grouping and discovery - Attach tags to resources to aid in organization and search. For example, you could search for all resources with the key name Project and the value MyImportantProject. Or search for all resources with the key name Cost Center and the value -41200. Access control - Include tags in IAM user-based and resource-based policies. You -can use tags to restrict access to only an IAM requesting user that has a specified tag +41200. Access control - Include tags in IAM identity-based and resource-based policies. +You can use tags to restrict access to only an IAM requesting user that has a specified tag attached. You can also restrict access to only those resources that have a certain tag attached. For examples of policies that show how to use tags to control access, see Control access using IAM tags in the IAM User Guide. Cost allocation - Use tags to help track diff --git a/src/services/keyspaces.jl b/src/services/keyspaces.jl index b4960c0654..c4e51defc9 100644 --- a/src/services/keyspaces.jl +++ b/src/services/keyspaces.jl @@ -60,47 +60,51 @@ Creating tables in the Amazon Keyspaces Developer Guide. # Arguments - `keyspace_name`: The name of the keyspace that the table is going to be created in. - `schema_definition`: The schemaDefinition consists of the following parameters. For each - column to be created: • name - The name of the column. • type - An Amazon Keyspaces - data type. For more information, see Data types in the Amazon Keyspaces Developer Guide. - The primary key of the table consists of the following columns: • partitionKeys - The + column to be created: name - The name of the column. type - An Amazon Keyspaces data + type. For more information, see Data types in the Amazon Keyspaces Developer Guide. The + primary key of the table consists of the following columns: partitionKeys - The partition key can be a single column, or it can be a compound value composed of two or more columns. The partition key portion of the primary key is required and determines how Amazon - Keyspaces stores your data. • name - The name of each partition key column. • + Keyspaces stores your data. name - The name of each partition key column. clusteringKeys - The optional clustering column portion of your primary key determines how - the data is clustered and sorted within each partition. • name - The name of the - clustering column. • orderBy - Sets the ascendant (ASC) or descendant (DESC) order + the data is clustered and sorted within each partition. name - The name of the + clustering column. orderBy - Sets the ascendant (ASC) or descendant (DESC) order modifier. To define a column as static use staticColumns - Static columns store values that - are shared by all rows in the same partition: • name - The name of the column. • type - + are shared by all rows in the same partition: name - The name of the column. type - An Amazon Keyspaces data type. - `table_name`: The name of the table. # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: - `"capacitySpecification"`: Specifies the read/write throughput capacity mode for the - table. The options are: • throughputMode:PAY_PER_REQUEST and • + table. The options are: throughputMode:PAY_PER_REQUEST and throughputMode:PROVISIONED - Provisioned capacity mode requires readCapacityUnits and - writeCapacityUnits as input. The default is throughput_mode:PAY_PER_REQUEST. For more + writeCapacityUnits as input. The default is throughput_mode:PAY_PER_REQUEST. For more information, see Read/write capacity modes in the Amazon Keyspaces Developer Guide. +- `"clientSideTimestamps"`: Enables client-side timestamps for the table. By default, the + setting is disabled. You can enable client-side timestamps with the following option: + status: \"enabled\" Once client-side timestamps are enabled for a table, this setting + cannot be disabled. - `"comment"`: This parameter allows to enter a description of the table. - `"defaultTimeToLive"`: The default Time to Live setting in seconds for the table. For more information, see Setting the default TTL value for a table in the Amazon Keyspaces Developer Guide. - `"encryptionSpecification"`: Specifies how the encryption key for encryption at rest is - managed for the table. You can choose one of the following KMS key (KMS key): • - type:AWS_OWNED_KMS_KEY - This key is owned by Amazon Keyspaces. • + managed for the table. You can choose one of the following KMS key (KMS key): + type:AWS_OWNED_KMS_KEY - This key is owned by Amazon Keyspaces. type:CUSTOMER_MANAGED_KMS_KEY - This key is stored in your account and is created, owned, and managed by you. This option requires the kms_key_identifier of the KMS key in Amazon - Resource Name (ARN) format as input. The default is type:AWS_OWNED_KMS_KEY. For more + Resource Name (ARN) format as input. The default is type:AWS_OWNED_KMS_KEY. For more information, see Encryption at rest in the Amazon Keyspaces Developer Guide. - `"pointInTimeRecovery"`: Specifies if pointInTimeRecovery is enabled or disabled for the - table. The options are: • ENABLED • DISABLED If it's not specified, the default is - DISABLED. For more information, see Point-in-time recovery in the Amazon Keyspaces - Developer Guide. + table. The options are: status=ENABLED status=DISABLED If it's not specified, the + default is status=DISABLED. For more information, see Point-in-time recovery in the Amazon + Keyspaces Developer Guide. - `"tags"`: A list of key-value pair tags to be attached to the resource. For more information, see Adding tags and labels to Amazon Keyspaces resources in the Amazon Keyspaces Developer Guide. -- `"ttl"`: Enables Time to Live custom settings for the table. The options are: • - status:enabled • status:disabled The default is status:disabled. After ttl is enabled, +- `"ttl"`: Enables Time to Live custom settings for the table. The options are: + status:enabled status:disabled The default is status:disabled. After ttl is enabled, you can't disable it for the table. For more information, see Expiring data by using Amazon Keyspaces Time to Live (TTL) in the Amazon Keyspaces Developer Guide. """ @@ -422,21 +426,21 @@ end Restores the specified table to the specified point in time within the earliest_restorable_timestamp and the current time. For more information about restore points, see Time window for PITR continuous backups in the Amazon Keyspaces Developer -Guide. Any number of users can execute up to 4 concurrent restores (any type of restore) -in a given account. When you restore using point in time recovery, Amazon Keyspaces -restores your source table's schema and data to the state based on the selected timestamp +Guide. Any number of users can execute up to 4 concurrent restores (any type of restore) in +a given account. When you restore using point in time recovery, Amazon Keyspaces restores +your source table's schema and data to the state based on the selected timestamp (day:hour:minute:second) to a new table. The Time to Live (TTL) settings are also restored to the state based on the selected timestamp. In addition to the table's schema, data, and TTL settings, RestoreTable restores the capacity mode, encryption, and point-in-time recovery settings from the source table. Unlike the table's schema data and TTL settings, which are restored based on the selected timestamp, these settings are always restored based on the table's settings as of the current time or when the table was deleted. You can -also overwrite these settings during restore: • Read/write capacity mode • Provisioned -throughput capacity settings • Point-in-time (PITR) settings • Tags For more -information, see PITR restore settings in the Amazon Keyspaces Developer Guide. Note that -the following settings are not restored, and you must configure them manually for the new -table: • Automatic scaling policies (for tables that use provisioned capacity mode) • -Identity and Access Management (IAM) policies • Amazon CloudWatch metrics and alarms +also overwrite these settings during restore: Read/write capacity mode Provisioned +throughput capacity settings Point-in-time (PITR) settings Tags For more information, +see PITR restore settings in the Amazon Keyspaces Developer Guide. Note that the following +settings are not restored, and you must configure them manually for the new table: +Automatic scaling policies (for tables that use provisioned capacity mode) Identity and +Access Management (IAM) policies Amazon CloudWatch metrics and alarms # Arguments - `source_keyspace_name`: The keyspace name of the source table. @@ -447,21 +451,21 @@ Identity and Access Management (IAM) policies • Amazon CloudWatch metrics and # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: - `"capacitySpecificationOverride"`: Specifies the read/write throughput capacity mode for - the target table. The options are: • throughputMode:PAY_PER_REQUEST • + the target table. The options are: throughputMode:PAY_PER_REQUEST throughputMode:PROVISIONED - Provisioned capacity mode requires readCapacityUnits and - writeCapacityUnits as input. The default is throughput_mode:PAY_PER_REQUEST. For more + writeCapacityUnits as input. The default is throughput_mode:PAY_PER_REQUEST. For more information, see Read/write capacity modes in the Amazon Keyspaces Developer Guide. - `"encryptionSpecificationOverride"`: Specifies the encryption settings for the target - table. You can choose one of the following KMS key (KMS key): • type:AWS_OWNED_KMS_KEY - - This key is owned by Amazon Keyspaces. • type:CUSTOMER_MANAGED_KMS_KEY - This key is + table. You can choose one of the following KMS key (KMS key): type:AWS_OWNED_KMS_KEY - + This key is owned by Amazon Keyspaces. type:CUSTOMER_MANAGED_KMS_KEY - This key is stored in your account and is created, owned, and managed by you. This option requires the - kms_key_identifier of the KMS key in Amazon Resource Name (ARN) format as input. The + kms_key_identifier of the KMS key in Amazon Resource Name (ARN) format as input. The default is type:AWS_OWNED_KMS_KEY. For more information, see Encryption at rest in the Amazon Keyspaces Developer Guide. - `"pointInTimeRecoveryOverride"`: Specifies the pointInTimeRecovery settings for the - target table. The options are: • ENABLED • DISABLED If it's not specified, the - default is DISABLED. For more information, see Point-in-time recovery in the Amazon - Keyspaces Developer Guide. + target table. The options are: status=ENABLED status=DISABLED If it's not + specified, the default is status=DISABLED. For more information, see Point-in-time recovery + in the Amazon Keyspaces Developer Guide. - `"restoreTimestamp"`: The restore timestamp in ISO 8601 format. - `"tagsOverride"`: A list of key-value pair tags to be attached to the restored table. For more information, see Adding tags and labels to Amazon Keyspaces resources in the @@ -614,29 +618,34 @@ one specific table setting per update operation. # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: -- `"addColumns"`: For each column to be added to the specified table: • name - The name - of the column. • type - An Amazon Keyspaces data type. For more information, see Data - types in the Amazon Keyspaces Developer Guide. +- `"addColumns"`: For each column to be added to the specified table: name - The name of + the column. type - An Amazon Keyspaces data type. For more information, see Data types + in the Amazon Keyspaces Developer Guide. - `"capacitySpecification"`: Modifies the read/write throughput capacity mode for the - table. The options are: • throughputMode:PAY_PER_REQUEST and • + table. The options are: throughputMode:PAY_PER_REQUEST and throughputMode:PROVISIONED - Provisioned capacity mode requires readCapacityUnits and - writeCapacityUnits as input. The default is throughput_mode:PAY_PER_REQUEST. For more + writeCapacityUnits as input. The default is throughput_mode:PAY_PER_REQUEST. For more information, see Read/write capacity modes in the Amazon Keyspaces Developer Guide. +- `"clientSideTimestamps"`: Enables client-side timestamps for the table. By default, the + setting is disabled. You can enable client-side timestamps with the following option: + status: \"enabled\" Once client-side timestamps are enabled for a table, this setting + cannot be disabled. - `"defaultTimeToLive"`: The default Time to Live setting in seconds for the table. For more information, see Setting the default TTL value for a table in the Amazon Keyspaces Developer Guide. - `"encryptionSpecification"`: Modifies the encryption settings of the table. You can - choose one of the following KMS key (KMS key): • type:AWS_OWNED_KMS_KEY - This key is - owned by Amazon Keyspaces. • type:CUSTOMER_MANAGED_KMS_KEY - This key is stored in your + choose one of the following KMS key (KMS key): type:AWS_OWNED_KMS_KEY - This key is + owned by Amazon Keyspaces. type:CUSTOMER_MANAGED_KMS_KEY - This key is stored in your account and is created, owned, and managed by you. This option requires the - kms_key_identifier of the KMS key in Amazon Resource Name (ARN) format as input. The + kms_key_identifier of the KMS key in Amazon Resource Name (ARN) format as input. The default is AWS_OWNED_KMS_KEY. For more information, see Encryption at rest in the Amazon Keyspaces Developer Guide. - `"pointInTimeRecovery"`: Modifies the pointInTimeRecovery settings of the table. The - options are: • ENABLED • DISABLED If it's not specified, the default is DISABLED. For - more information, see Point-in-time recovery in the Amazon Keyspaces Developer Guide. -- `"ttl"`: Modifies Time to Live custom settings for the table. The options are: • - status:enabled • status:disabled The default is status:disabled. After ttl is enabled, + options are: status=ENABLED status=DISABLED If it's not specified, the default is + status=DISABLED. For more information, see Point-in-time recovery in the Amazon Keyspaces + Developer Guide. +- `"ttl"`: Modifies Time to Live custom settings for the table. The options are: + status:enabled status:disabled The default is status:disabled. After ttl is enabled, you can't disable it for the table. For more information, see Expiring data by using Amazon Keyspaces Time to Live (TTL) in the Amazon Keyspaces Developer Guide. """ diff --git a/src/services/neptune.jl b/src/services/neptune.jl index 09ace251dc..2220e44e5d 100644 --- a/src/services/neptune.jl +++ b/src/services/neptune.jl @@ -753,12 +753,14 @@ function create_dbcluster_snapshot( end """ - create_dbinstance(dbinstance_class, dbinstance_identifier, engine) - create_dbinstance(dbinstance_class, dbinstance_identifier, engine, params::Dict{String,<:Any}) + create_dbinstance(dbcluster_identifier, dbinstance_class, dbinstance_identifier, engine) + create_dbinstance(dbcluster_identifier, dbinstance_class, dbinstance_identifier, engine, params::Dict{String,<:Any}) Creates a new DB instance. # Arguments +- `dbcluster_identifier`: The identifier of the DB cluster that the instance will belong + to. For information on creating a DB cluster, see CreateDBCluster. Type: String - `dbinstance_class`: The compute and memory capacity of the DB instance, for example, db.m4.large. Not all DB instance classes are available in all Amazon Regions. - `dbinstance_identifier`: The DB instance identifier. This parameter is stored as a @@ -785,8 +787,6 @@ Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys - `"CharacterSetName"`: (Not supported by Neptune) - `"CopyTagsToSnapshot"`: True to copy all tags from the DB instance to snapshots of the DB instance, and otherwise false. The default is false. -- `"DBClusterIdentifier"`: The identifier of the DB cluster that the instance will belong - to. For information on creating a DB cluster, see CreateDBCluster. Type: String - `"DBName"`: Not supported. - `"DBParameterGroupName"`: The name of the DB parameter group to associate with this DB instance. If this argument is omitted, the default DBParameterGroup for the specified @@ -868,6 +868,7 @@ Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys security group for the DB subnet group's VPC. """ function create_dbinstance( + DBClusterIdentifier, DBInstanceClass, DBInstanceIdentifier, Engine; @@ -876,6 +877,7 @@ function create_dbinstance( return neptune( "CreateDBInstance", Dict{String,Any}( + "DBClusterIdentifier" => DBClusterIdentifier, "DBInstanceClass" => DBInstanceClass, "DBInstanceIdentifier" => DBInstanceIdentifier, "Engine" => Engine, @@ -885,6 +887,7 @@ function create_dbinstance( ) end function create_dbinstance( + DBClusterIdentifier, DBInstanceClass, DBInstanceIdentifier, Engine, @@ -897,6 +900,7 @@ function create_dbinstance( mergewith( _merge, Dict{String,Any}( + "DBClusterIdentifier" => DBClusterIdentifier, "DBInstanceClass" => DBInstanceClass, "DBInstanceIdentifier" => DBInstanceIdentifier, "Engine" => Engine, diff --git a/src/services/s3_control.jl b/src/services/s3_control.jl index 6564bf98b7..06497ce9b0 100644 --- a/src/services/s3_control.jl +++ b/src/services/s3_control.jl @@ -27,7 +27,7 @@ GetAccessPoint DeleteAccessPoint ListAccessPoints the Amazon Web Services SDK and CLI, you must specify the ARN of the bucket accessed in the format arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/bucket/< - ;my-bucket-name>. For example, to access the bucket reports through outpost my-outpost + ;my-bucket-name>. For example, to access the bucket reports through Outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/bucket/reports. The value must be URL encoded. @@ -380,7 +380,7 @@ CreateAccessPoint GetAccessPoint ListAccessPoints CLI, you must specify the ARN of the access point accessed in the format arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/accesspoint /<my-accesspoint-name>. For example, to access the access point reports-ap through - outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding + Outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/accesspoint/reports-ap. The value must be URL encoded. - `x-amz-account-id`: The Amazon Web Services account ID for the account that owns the @@ -492,7 +492,7 @@ related to DeleteAccessPointPolicy: PutAccessPointPolicy GetAccessPointPo Services SDK and CLI, you must specify the ARN of the access point accessed in the format arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/accesspoint /<my-accesspoint-name>. For example, to access the access point reports-ap through - outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding + Outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/accesspoint/reports-ap. The value must be URL encoded. - `x-amz-account-id`: The account ID for the account that owns the specified access point. @@ -606,7 +606,7 @@ DeleteObject using this parameter with S3 on Outposts with the Amazon Web Services SDK and CLI, you must specify the ARN of the bucket accessed in the format arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/bucket/< - ;my-bucket-name>. For example, to access the bucket reports through outpost my-outpost + ;my-bucket-name>. For example, to access the bucket reports through Outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/bucket/reports. The value must be URL encoded. @@ -677,7 +677,7 @@ actions include: PutBucketLifecycleConfiguration GetBucketLifecycleConfig parameter with S3 on Outposts with the Amazon Web Services SDK and CLI, you must specify the ARN of the bucket accessed in the format arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/bucket/< - ;my-bucket-name>. For example, to access the bucket reports through outpost my-outpost + ;my-bucket-name>. For example, to access the bucket reports through Outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/bucket/reports. The value must be URL encoded. @@ -752,7 +752,7 @@ following actions are related to DeleteBucketPolicy: GetBucketPolicy PutB parameter with S3 on Outposts with the Amazon Web Services SDK and CLI, you must specify the ARN of the bucket accessed in the format arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/bucket/< - ;my-bucket-name>. For example, to access the bucket reports through outpost my-outpost + ;my-bucket-name>. For example, to access the bucket reports through Outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/bucket/reports. The value must be URL encoded. @@ -795,6 +795,82 @@ function delete_bucket_policy( ) end +""" + delete_bucket_replication(name, x-amz-account-id) + delete_bucket_replication(name, x-amz-account-id, params::Dict{String,<:Any}) + + This operation deletes an Amazon S3 on Outposts bucket's replication configuration. To +delete an S3 bucket's replication configuration, see DeleteBucketReplication in the Amazon +S3 API Reference. Deletes the replication configuration from the specified S3 on Outposts +bucket. To use this operation, you must have permissions to perform the +s3-outposts:PutReplicationConfiguration action. The Outposts bucket owner has this +permission by default and can grant it to others. For more information about permissions, +see Setting up IAM with S3 on Outposts and Managing access to S3 on Outposts buckets in the +Amazon S3 User Guide. It can take a while to propagate PUT or DELETE requests for a +replication configuration to all S3 on Outposts systems. Therefore, the replication +configuration that's returned by a GET request soon after a PUT or DELETE request might +return a more recent result than what's on the Outpost. If an Outpost is offline, the delay +in updating the replication configuration on that Outpost can be significant. All Amazon +S3 on Outposts REST API requests for this action require an additional parameter of +x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts +endpoint hostname prefix instead of s3-control. For an example of the request syntax for +Amazon S3 on Outposts that uses the S3 on Outposts endpoint hostname prefix and the +x-amz-outpost-id derived by using the access point ARN, see the Examples section. For +information about S3 replication on Outposts configuration, see Replicating objects for S3 +on Outposts in the Amazon S3 User Guide. The following operations are related to +DeleteBucketReplication: PutBucketReplication GetBucketReplication + +# Arguments +- `name`: Specifies the S3 on Outposts bucket to delete the replication configuration for. + For using this parameter with Amazon S3 on Outposts with the REST API, you must specify the + name and the x-amz-outpost-id as well. For using this parameter with S3 on Outposts with + the Amazon Web Services SDK and CLI, you must specify the ARN of the bucket accessed in the + format + arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/bucket/< + ;my-bucket-name>. For example, to access the bucket reports through Outpost my-outpost + owned by account 123456789012 in Region us-west-2, use the URL encoding of + arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/bucket/reports. The value + must be URL encoded. +- `x-amz-account-id`: The Amazon Web Services account ID of the Outposts bucket to delete + the replication configuration for. + +""" +function delete_bucket_replication( + name, x_amz_account_id; aws_config::AbstractAWSConfig=global_aws_config() +) + return s3_control( + "DELETE", + "/v20180820/bucket/$(name)/replication", + Dict{String,Any}( + "headers" => Dict{String,Any}("x-amz-account-id" => x_amz_account_id) + ); + aws_config=aws_config, + feature_set=SERVICE_FEATURE_SET, + ) +end +function delete_bucket_replication( + name, + x_amz_account_id, + params::AbstractDict{String}; + aws_config::AbstractAWSConfig=global_aws_config(), +) + return s3_control( + "DELETE", + "/v20180820/bucket/$(name)/replication", + Dict{String,Any}( + mergewith( + _merge, + Dict{String,Any}( + "headers" => Dict{String,Any}("x-amz-account-id" => x_amz_account_id) + ), + params, + ), + ); + aws_config=aws_config, + feature_set=SERVICE_FEATURE_SET, + ) +end + """ delete_bucket_tagging(name, x-amz-account-id) delete_bucket_tagging(name, x-amz-account-id, params::Dict{String,<:Any}) @@ -818,7 +894,7 @@ PutBucketTagging as well. For using this parameter with S3 on Outposts with the Amazon Web Services SDK and CLI, you must specify the ARN of the bucket accessed in the format arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/bucket/< - ;my-bucket-name>. For example, to access the bucket reports through outpost my-outpost + ;my-bucket-name>. For example, to access the bucket reports through Outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/bucket/reports. The value must be URL encoded. @@ -866,10 +942,11 @@ end delete_job_tagging(id, x-amz-account-id) delete_job_tagging(id, x-amz-account-id, params::Dict{String,<:Any}) -Removes the entire tag set from the specified S3 Batch Operations job. To use this -operation, you must have permission to perform the s3:DeleteJobTagging action. For more -information, see Controlling access and labeling jobs using tags in the Amazon S3 User -Guide. Related actions include: CreateJob GetJobTagging PutJobTagging +Removes the entire tag set from the specified S3 Batch Operations job. To use the +DeleteJobTagging operation, you must have permission to perform the s3:DeleteJobTagging +action. For more information, see Controlling access and labeling jobs using tags in the +Amazon S3 User Guide. Related actions include: CreateJob GetJobTagging +PutJobTagging # Arguments - `id`: The ID for the S3 Batch Operations job whose tags you want to delete. @@ -1257,7 +1334,7 @@ following actions are related to GetAccessPoint: CreateAccessPoint Delete point accessed in the format arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/accesspoint /<my-accesspoint-name>. For example, to access the access point reports-ap through - outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding + Outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/accesspoint/reports-ap. The value must be URL encoded. - `x-amz-account-id`: The Amazon Web Services account ID for the account that owns the @@ -1417,7 +1494,7 @@ DeleteAccessPointPolicy Services SDK and CLI, you must specify the ARN of the access point accessed in the format arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/accesspoint /<my-accesspoint-name>. For example, to access the access point reports-ap through - outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding + Outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/accesspoint/reports-ap. The value must be URL encoded. - `x-amz-account-id`: The account ID for the account that owns the specified access point. @@ -1632,7 +1709,7 @@ PutObject CreateBucket DeleteBucket parameter with S3 on Outposts with the Amazon Web Services SDK and CLI, you must specify the ARN of the bucket accessed in the format arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/bucket/< - ;my-bucket-name>. For example, to access the bucket reports through outpost my-outpost + ;my-bucket-name>. For example, to access the bucket reports through Outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/bucket/reports. The value must be URL encoded. @@ -1705,7 +1782,7 @@ actions are related to GetBucketLifecycleConfiguration: PutBucketLifecycleCon as well. For using this parameter with S3 on Outposts with the Amazon Web Services SDK and CLI, you must specify the ARN of the bucket accessed in the format arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/bucket/< - ;my-bucket-name>. For example, to access the bucket reports through outpost my-outpost + ;my-bucket-name>. For example, to access the bucket reports through Outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/bucket/reports. The value must be URL encoded. @@ -1779,7 +1856,7 @@ PutBucketPolicy DeleteBucketPolicy parameter with S3 on Outposts with the Amazon Web Services SDK and CLI, you must specify the ARN of the bucket accessed in the format arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/bucket/< - ;my-bucket-name>. For example, to access the bucket reports through outpost my-outpost + ;my-bucket-name>. For example, to access the bucket reports through Outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/bucket/reports. The value must be URL encoded. @@ -1822,6 +1899,85 @@ function get_bucket_policy( ) end +""" + get_bucket_replication(name, x-amz-account-id) + get_bucket_replication(name, x-amz-account-id, params::Dict{String,<:Any}) + + This operation gets an Amazon S3 on Outposts bucket's replication configuration. To get an +S3 bucket's replication configuration, see GetBucketReplication in the Amazon S3 API +Reference. Returns the replication configuration of an S3 on Outposts bucket. For more +information about S3 on Outposts, see Using Amazon S3 on Outposts in the Amazon S3 User +Guide. For information about S3 replication on Outposts configuration, see Replicating +objects for S3 on Outposts in the Amazon S3 User Guide. It can take a while to propagate +PUT or DELETE requests for a replication configuration to all S3 on Outposts systems. +Therefore, the replication configuration that's returned by a GET request soon after a PUT +or DELETE request might return a more recent result than what's on the Outpost. If an +Outpost is offline, the delay in updating the replication configuration on that Outpost can +be significant. This action requires permissions for the +s3-outposts:GetReplicationConfiguration action. The Outposts bucket owner has this +permission by default and can grant it to others. For more information about permissions, +see Setting up IAM with S3 on Outposts and Managing access to S3 on Outposts bucket in the +Amazon S3 User Guide. All Amazon S3 on Outposts REST API requests for this action require +an additional parameter of x-amz-outpost-id to be passed with the request. In addition, you +must use an S3 on Outposts endpoint hostname prefix instead of s3-control. For an example +of the request syntax for Amazon S3 on Outposts that uses the S3 on Outposts endpoint +hostname prefix and the x-amz-outpost-id derived by using the access point ARN, see the +Examples section. If you include the Filter element in a replication configuration, you +must also include the DeleteMarkerReplication, Status, and Priority elements. The response +also returns those elements. For information about S3 on Outposts replication failure +reasons, see Replication failure reasons in the Amazon S3 User Guide. The following +operations are related to GetBucketReplication: PutBucketReplication +DeleteBucketReplication + +# Arguments +- `name`: Specifies the bucket to get the replication information for. For using this + parameter with Amazon S3 on Outposts with the REST API, you must specify the name and the + x-amz-outpost-id as well. For using this parameter with S3 on Outposts with the Amazon Web + Services SDK and CLI, you must specify the ARN of the bucket accessed in the format + arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/bucket/< + ;my-bucket-name>. For example, to access the bucket reports through Outpost my-outpost + owned by account 123456789012 in Region us-west-2, use the URL encoding of + arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/bucket/reports. The value + must be URL encoded. +- `x-amz-account-id`: The Amazon Web Services account ID of the Outposts bucket. + +""" +function get_bucket_replication( + name, x_amz_account_id; aws_config::AbstractAWSConfig=global_aws_config() +) + return s3_control( + "GET", + "/v20180820/bucket/$(name)/replication", + Dict{String,Any}( + "headers" => Dict{String,Any}("x-amz-account-id" => x_amz_account_id) + ); + aws_config=aws_config, + feature_set=SERVICE_FEATURE_SET, + ) +end +function get_bucket_replication( + name, + x_amz_account_id, + params::AbstractDict{String}; + aws_config::AbstractAWSConfig=global_aws_config(), +) + return s3_control( + "GET", + "/v20180820/bucket/$(name)/replication", + Dict{String,Any}( + mergewith( + _merge, + Dict{String,Any}( + "headers" => Dict{String,Any}("x-amz-account-id" => x_amz_account_id) + ), + params, + ), + ); + aws_config=aws_config, + feature_set=SERVICE_FEATURE_SET, + ) +end + """ get_bucket_tagging(name, x-amz-account-id) get_bucket_tagging(name, x-amz-account-id, params::Dict{String,<:Any}) @@ -1847,7 +2003,7 @@ DeleteBucketTagging parameter with S3 on Outposts with the Amazon Web Services SDK and CLI, you must specify the ARN of the bucket accessed in the format arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/bucket/< - ;my-bucket-name>. For example, to access the bucket reports through outpost my-outpost + ;my-bucket-name>. For example, to access the bucket reports through Outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/bucket/reports. The value must be URL encoded. @@ -1894,10 +2050,10 @@ end get_bucket_versioning(name, x-amz-account-id) get_bucket_versioning(name, x-amz-account-id, params::Dict{String,<:Any}) - This operation returns the versioning state only for S3 on Outposts buckets. To return the + This operation returns the versioning state for S3 on Outposts buckets only. To return the versioning state for an S3 bucket, see GetBucketVersioning in the Amazon S3 API Reference. - Returns the versioning state for an S3 on Outposts bucket. With versioning, you can save -multiple distinct copies of your data and recover from unintended user actions and + Returns the versioning state for an S3 on Outposts bucket. With S3 Versioning, you can +save multiple distinct copies of your objects and recover from unintended user actions and application failures. If you've never set versioning on your bucket, it has no versioning state. In that case, the GetBucketVersioning request does not return a versioning state value. For more information about versioning, see Versioning in the Amazon S3 User Guide. @@ -1955,10 +2111,10 @@ end get_job_tagging(id, x-amz-account-id) get_job_tagging(id, x-amz-account-id, params::Dict{String,<:Any}) -Returns the tags on an S3 Batch Operations job. To use this operation, you must have -permission to perform the s3:GetJobTagging action. For more information, see Controlling -access and labeling jobs using tags in the Amazon S3 User Guide. Related actions include: - CreateJob PutJobTagging DeleteJobTagging +Returns the tags on an S3 Batch Operations job. To use the GetJobTagging operation, you +must have permission to perform the s3:GetJobTagging action. For more information, see +Controlling access and labeling jobs using tags in the Amazon S3 User Guide. Related +actions include: CreateJob PutJobTagging DeleteJobTagging # Arguments - `id`: The ID for the S3 Batch Operations job whose tags you want to retrieve. @@ -2377,11 +2533,11 @@ end list_access_points(x-amz-account-id) list_access_points(x-amz-account-id, params::Dict{String,<:Any}) -Returns a list of the access points owned by the current account associated with the -specified bucket. You can retrieve up to 1000 access points per call. If the specified -bucket has more than 1,000 access points (or the number specified in maxResults, whichever -is less), the response will include a continuation token that you can use to list the -additional access points. All Amazon S3 on Outposts REST API requests for this action +Returns a list of the access points that are owned by the current account that's associated +with the specified bucket. You can retrieve up to 1000 access points per call. If the +specified bucket has more than 1,000 access points (or the number specified in maxResults, +whichever is less), the response will include a continuation token that you can use to list +the additional access points. All Amazon S3 on Outposts REST API requests for this action require an additional parameter of x-amz-outpost-id to be passed with the request. In addition, you must use an S3 on Outposts endpoint hostname prefix instead of s3-control. For an example of the request syntax for Amazon S3 on Outposts that uses the S3 on Outposts @@ -2401,7 +2557,7 @@ Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys the Amazon Web Services SDK and CLI, you must specify the ARN of the bucket accessed in the format arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/bucket/< - ;my-bucket-name>. For example, to access the bucket reports through outpost my-outpost + ;my-bucket-name>. For example, to access the bucket reports through Outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/bucket/reports. The value must be URL encoded. @@ -2809,7 +2965,7 @@ GetAccessPointPolicy DeleteAccessPointPolicy point accessed in the format arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/accesspoint /<my-accesspoint-name>. For example, to access the access point reports-ap through - outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding + Outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/accesspoint/reports-ap. The value must be URL encoded. - `x-amz-account-id`: The Amazon Web Services account ID for owner of the bucket associated @@ -3005,7 +3161,7 @@ following actions are related to PutBucketPolicy: GetBucketPolicy DeleteB parameter with S3 on Outposts with the Amazon Web Services SDK and CLI, you must specify the ARN of the bucket accessed in the format arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/bucket/< - ;my-bucket-name>. For example, to access the bucket reports through outpost my-outpost + ;my-bucket-name>. For example, to access the bucket reports through Outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/bucket/reports. The value must be URL encoded. @@ -3056,6 +3212,109 @@ function put_bucket_policy( ) end +""" + put_bucket_replication(replication_configuration, name, x-amz-account-id) + put_bucket_replication(replication_configuration, name, x-amz-account-id, params::Dict{String,<:Any}) + + This action creates an Amazon S3 on Outposts bucket's replication configuration. To create +an S3 bucket's replication configuration, see PutBucketReplication in the Amazon S3 API +Reference. Creates a replication configuration or replaces an existing one. For +information about S3 replication on Outposts configuration, see Replicating objects for S3 +on Outposts in the Amazon S3 User Guide. It can take a while to propagate PUT or DELETE +requests for a replication configuration to all S3 on Outposts systems. Therefore, the +replication configuration that's returned by a GET request soon after a PUT or DELETE +request might return a more recent result than what's on the Outpost. If an Outpost is +offline, the delay in updating the replication configuration on that Outpost can be +significant. Specify the replication configuration in the request body. In the replication +configuration, you provide the following information: The name of the destination bucket +or buckets where you want S3 on Outposts to replicate objects The Identity and Access +Management (IAM) role that S3 on Outposts can assume to replicate objects on your behalf +Other relevant information, such as replication rules A replication configuration must +include at least one rule and can contain a maximum of 100. Each rule identifies a subset +of objects to replicate by filtering the objects in the source Outposts bucket. To choose +additional subsets of objects to replicate, add a rule for each subset. To specify a subset +of the objects in the source Outposts bucket to apply a replication rule to, add the Filter +element as a child of the Rule element. You can filter objects based on an object key +prefix, one or more object tags, or both. When you add the Filter element in the +configuration, you must also add the following elements: DeleteMarkerReplication, Status, +and Priority. Using PutBucketReplication on Outposts requires that both the source and +destination buckets must have versioning enabled. For information about enabling versioning +on a bucket, see Managing S3 Versioning for your S3 on Outposts bucket. For information +about S3 on Outposts replication failure reasons, see Replication failure reasons in the +Amazon S3 User Guide. Handling Replication of Encrypted Objects Outposts buckets are +encrypted at all times. All the objects in the source Outposts bucket are encrypted and can +be replicated. Also, all the replicas in the destination Outposts bucket are encrypted with +the same encryption key as the objects in the source Outposts bucket. Permissions To +create a PutBucketReplication request, you must have +s3-outposts:PutReplicationConfiguration permissions for the bucket. The Outposts bucket +owner has this permission by default and can grant it to others. For more information about +permissions, see Setting up IAM with S3 on Outposts and Managing access to S3 on Outposts +buckets. To perform this operation, the user or role must also have the iam:CreateRole +and iam:PassRole permissions. For more information, see Granting a user permissions to pass +a role to an Amazon Web Services service. All Amazon S3 on Outposts REST API requests for +this action require an additional parameter of x-amz-outpost-id to be passed with the +request. In addition, you must use an S3 on Outposts endpoint hostname prefix instead of +s3-control. For an example of the request syntax for Amazon S3 on Outposts that uses the S3 +on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by using the access +point ARN, see the Examples section. The following operations are related to +PutBucketReplication: GetBucketReplication DeleteBucketReplication + +# Arguments +- `replication_configuration`: +- `name`: Specifies the S3 on Outposts bucket to set the configuration for. For using this + parameter with Amazon S3 on Outposts with the REST API, you must specify the name and the + x-amz-outpost-id as well. For using this parameter with S3 on Outposts with the Amazon Web + Services SDK and CLI, you must specify the ARN of the bucket accessed in the format + arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/bucket/< + ;my-bucket-name>. For example, to access the bucket reports through Outpost my-outpost + owned by account 123456789012 in Region us-west-2, use the URL encoding of + arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/bucket/reports. The value + must be URL encoded. +- `x-amz-account-id`: The Amazon Web Services account ID of the Outposts bucket. + +""" +function put_bucket_replication( + ReplicationConfiguration, + name, + x_amz_account_id; + aws_config::AbstractAWSConfig=global_aws_config(), +) + return s3_control( + "PUT", + "/v20180820/bucket/$(name)/replication", + Dict{String,Any}( + "ReplicationConfiguration" => ReplicationConfiguration, + "headers" => Dict{String,Any}("x-amz-account-id" => x_amz_account_id), + ); + aws_config=aws_config, + feature_set=SERVICE_FEATURE_SET, + ) +end +function put_bucket_replication( + ReplicationConfiguration, + name, + x_amz_account_id, + params::AbstractDict{String}; + aws_config::AbstractAWSConfig=global_aws_config(), +) + return s3_control( + "PUT", + "/v20180820/bucket/$(name)/replication", + Dict{String,Any}( + mergewith( + _merge, + Dict{String,Any}( + "ReplicationConfiguration" => ReplicationConfiguration, + "headers" => Dict{String,Any}("x-amz-account-id" => x_amz_account_id), + ), + params, + ), + ); + aws_config=aws_config, + feature_set=SERVICE_FEATURE_SET, + ) +end + """ put_bucket_tagging(tagging, name, x-amz-account-id) put_bucket_tagging(tagging, name, x-amz-account-id, params::Dict{String,<:Any}) @@ -3098,7 +3357,7 @@ GetBucketTagging DeleteBucketTagging as well. For using this parameter with S3 on Outposts with the Amazon Web Services SDK and CLI, you must specify the ARN of the bucket accessed in the format arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/bucket/< - ;my-bucket-name>. For example, to access the bucket reports through outpost my-outpost + ;my-bucket-name>. For example, to access the bucket reports through Outpost my-outpost owned by account 123456789012 in Region us-west-2, use the URL encoding of arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/bucket/reports. The value must be URL encoded. @@ -3148,10 +3407,10 @@ end put_bucket_versioning(versioning_configuration, name, x-amz-account-id) put_bucket_versioning(versioning_configuration, name, x-amz-account-id, params::Dict{String,<:Any}) - This operation sets the versioning state only for S3 on Outposts buckets. To set the + This operation sets the versioning state for S3 on Outposts buckets only. To set the versioning state for an S3 bucket, see PutBucketVersioning in the Amazon S3 API Reference. - Sets the versioning state for an S3 on Outposts bucket. With versioning, you can save -multiple distinct copies of your data and recover from unintended user actions and + Sets the versioning state for an S3 on Outposts bucket. With S3 Versioning, you can save +multiple distinct copies of your objects and recover from unintended user actions and application failures. You can set the versioning state to one of the following: Enabled - Enables versioning for the objects in the bucket. All objects added to the bucket receive a unique version ID. Suspended - Suspends versioning for the objects in the bucket. All @@ -3162,18 +3421,18 @@ your bucket, you have a current version and zero or more noncurrent versions. Yo configure your bucket S3 Lifecycle rules to expire noncurrent versions after a specified time period. For more information, see Creating and managing a lifecycle configuration for your S3 on Outposts bucket in the Amazon S3 User Guide. If you have an object expiration -lifecycle policy in your non-versioned bucket and you want to maintain the same permanent -delete behavior when you enable versioning, you must add a noncurrent expiration policy. -The noncurrent expiration lifecycle policy will manage the deletes of the noncurrent object -versions in the version-enabled bucket. For more information, see Versioning in the Amazon -S3 User Guide. All Amazon S3 on Outposts REST API requests for this action require an -additional parameter of x-amz-outpost-id to be passed with the request. In addition, you -must use an S3 on Outposts endpoint hostname prefix instead of s3-control. For an example -of the request syntax for Amazon S3 on Outposts that uses the S3 on Outposts endpoint -hostname prefix and the x-amz-outpost-id derived by using the access point ARN, see the -Examples section. The following operations are related to PutBucketVersioning for S3 on -Outposts. GetBucketVersioning PutBucketLifecycleConfiguration -GetBucketLifecycleConfiguration +lifecycle configuration in your non-versioned bucket and you want to maintain the same +permanent delete behavior when you enable versioning, you must add a noncurrent expiration +policy. The noncurrent expiration lifecycle configuration will manage the deletes of the +noncurrent object versions in the version-enabled bucket. For more information, see +Versioning in the Amazon S3 User Guide. All Amazon S3 on Outposts REST API requests for +this action require an additional parameter of x-amz-outpost-id to be passed with the +request. In addition, you must use an S3 on Outposts endpoint hostname prefix instead of +s3-control. For an example of the request syntax for Amazon S3 on Outposts that uses the S3 +on Outposts endpoint hostname prefix and the x-amz-outpost-id derived by using the access +point ARN, see the Examples section. The following operations are related to +PutBucketVersioning for S3 on Outposts. GetBucketVersioning +PutBucketLifecycleConfiguration GetBucketLifecycleConfiguration # Arguments - `versioning_configuration`: The root-level tag for the VersioningConfiguration parameters. @@ -3248,8 +3507,8 @@ as long as they have unique tag keys. A tag key can be up to 128 Unicode chara length, and tag values can be up to 256 Unicode characters in length. The key and values are case sensitive. For tagging-related restrictions related to characters and encodings, see User-Defined Tag Restrictions in the Billing and Cost Management User Guide. To -use this action, you must have permission to perform the s3:PutJobTagging action. Related -actions include: CreateJob GetJobTagging DeleteJobTagging +use the PutJobTagging operation, you must have permission to perform the s3:PutJobTagging +action. Related actions include: CreateJob GetJobTagging DeleteJobTagging # Arguments - `tags`: The set of tags to associate with the S3 Batch Operations job. diff --git a/src/services/sagemaker_runtime.jl b/src/services/sagemaker_runtime.jl index 07f2b723b2..254db55d1e 100644 --- a/src/services/sagemaker_runtime.jl +++ b/src/services/sagemaker_runtime.jl @@ -131,9 +131,10 @@ Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys - `"X-Amzn-SageMaker-Inference-Id"`: The identifier for the inference request. Amazon SageMaker will generate an identifier for you if none is specified. - `"X-Amzn-SageMaker-InvocationTimeoutSeconds"`: Maximum amount of time in seconds a - request can be processed before it is marked as expired. + request can be processed before it is marked as expired. The default is 15 minutes, or 900 + seconds. - `"X-Amzn-SageMaker-RequestTTLSeconds"`: Maximum age in seconds a request can be in the - queue before it is marked as expired. + queue before it is marked as expired. The default is 6 hours, or 21,600 seconds. """ function invoke_endpoint_async( EndpointName, diff --git a/src/services/securitylake.jl b/src/services/securitylake.jl index 35aae2e21e..23eb5ff216 100644 --- a/src/services/securitylake.jl +++ b/src/services/securitylake.jl @@ -396,10 +396,11 @@ end create_subscription_notification_configuration(subscription_id, params::Dict{String,<:Any}) Notifies the subscriber when new data is written to the data lake for the sources that the -subscriber consumes in Security Lake. +subscriber consumes in Security Lake. You can create only one subscriber notification per +subscriber. # Arguments -- `subscription_id`: The subscription ID for the notification subscription/ +- `subscription_id`: The subscription ID for the notification subscription. # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: @@ -408,7 +409,9 @@ Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys - `"httpsApiKeyValue"`: The key value for the notification subscription. - `"httpsMethod"`: The HTTPS method used for the notification subscription. - `"roleArn"`: The Amazon Resource Name (ARN) of the EventBridge API destinations IAM role - that you created. + that you created. For more information about ARNs and how to use them in policies, see + Managing data access and Amazon Web Services Managed Policies in the Amazon Security Lake + User Guide. - `"subscriptionEndpoint"`: The subscription endpoint in Security Lake. If you prefer notification with an HTTPs endpoint, populate this field. """ @@ -570,20 +573,15 @@ end delete_datalake_auto_enable(remove_from_configuration_for_new_accounts) delete_datalake_auto_enable(remove_from_configuration_for_new_accounts, params::Dict{String,<:Any}) -Automatically deletes Amazon Security Lake to stop collecting security data. When you -delete Amazon Security Lake from your account, Security Lake is disabled in all Regions. -Also, this API automatically takes steps to remove the account from Security Lake . This -operation disables security data collection from sources, deletes data stored, and stops -making data accessible to subscribers. Security Lake also deletes all the existing settings -and resources that it stores or maintains for your Amazon Web Services account in the -current Region, including security log and event data. The DeleteDatalake operation does -not delete the Amazon S3 bucket, which is owned by your Amazon Web Services account. For -more information, see the Amazon Security Lake User Guide. + DeleteDatalakeAutoEnable removes automatic enablement of configuration settings for new +member accounts (but keeps settings for the delegated administrator) from Amazon Security +Lake. You must run this API using credentials of the delegated administrator. When you run +this API, new member accounts that are added after the organization enables Security Lake +won't contribute to the data lake. # Arguments -- `remove_from_configuration_for_new_accounts`: Delete Amazon Security Lake with the - specified configuration settings to stop ingesting security data for new accounts in - Security Lake. +- `remove_from_configuration_for_new_accounts`: Remove automatic enablement of + configuration settings for new member accounts in Security Lake. """ function delete_datalake_auto_enable( @@ -1232,8 +1230,8 @@ end update_subscription_notification_configuration(subscription_id) update_subscription_notification_configuration(subscription_id, params::Dict{String,<:Any}) -Creates a new subscription notification or adds the existing subscription notification -setting for the specified subscription ID. +Updates an existing notification method for the subscription (SQS or HTTPs endpoint) or +switches the notification subscription endpoint for a subscriber. # Arguments - `subscription_id`: The subscription ID for which the subscription notification is @@ -1246,7 +1244,9 @@ Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys - `"httpsApiKeyName"`: The key name for the subscription notification. - `"httpsApiKeyValue"`: The key value for the subscription notification. - `"httpsMethod"`: The HTTPS method used for the subscription notification. -- `"roleArn"`: The Amazon Resource Name (ARN) specifying the role of the subscriber. +- `"roleArn"`: The Amazon Resource Name (ARN) specifying the role of the subscriber. For + more information about ARNs and how to use them in policies, see, see the Managing data + access and Amazon Web Services Managed Policiesin the Amazon Security Lake User Guide. - `"subscriptionEndpoint"`: The subscription endpoint in Security Lake. """ function update_subscription_notification_configuration( diff --git a/src/services/tnb.jl b/src/services/tnb.jl index a03631e0d6..05df993e3a 100644 --- a/src/services/tnb.jl +++ b/src/services/tnb.jl @@ -12,7 +12,7 @@ Cancels a network operation. A network operation is any operation that is done t network, such as network instance instantiation or termination. # Arguments -- `ns_lcm_op_occ_id`: The ID of a network operation occurrence. +- `ns_lcm_op_occ_id`: The identifier of the network operation. """ function cancel_sol_network_operation( @@ -501,7 +501,7 @@ operation and the status of the tasks. A network operation is any operation that your network, such as network instance instantiation or termination. # Arguments -- `ns_lcm_op_occ_id`: The identifier of the operation occurrence. +- `ns_lcm_op_occ_id`: The identifier of the network operation. """ function get_sol_network_operation( @@ -664,6 +664,10 @@ Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys - `"dry_run"`: A check for whether you have the required permissions for the action without actually making the request and provides an error response. If you have the required permissions, the error response is DryRunOperation. Otherwise, it is UnauthorizedOperation. +- `"tags"`: A tag is a label that you assign to an Amazon Web Services resource. Each tag + consists of a key and an optional value. When you use this API, the tags are transferred to + the network operation that is created. Use tags to search and filter your resources or + track your Amazon Web Services costs. """ function instantiate_sol_network_instance( nsInstanceId; aws_config::AbstractAWSConfig=global_aws_config() @@ -1024,6 +1028,12 @@ delete it. # Arguments - `ns_instance_id`: ID of the network instance. +# Optional Parameters +Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: +- `"tags"`: A tag is a label that you assign to an Amazon Web Services resource. Each tag + consists of a key and an optional value. When you use this API, the tags are transferred to + the network operation that is created. Use tags to search and filter your resources or + track your Amazon Web Services costs. """ function terminate_sol_network_instance( nsInstanceId; aws_config::AbstractAWSConfig=global_aws_config() @@ -1148,6 +1158,10 @@ update, and delete) can be performed. Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: - `"modifyVnfInfoData"`: Identifies the network function information parameters and/or the configurable properties of the network function to be modified. +- `"tags"`: A tag is a label that you assign to an Amazon Web Services resource. Each tag + consists of a key and an optional value. When you use this API, the tags are transferred to + the network operation that is created. Use tags to search and filter your resources or + track your Amazon Web Services costs. """ function update_sol_network_instance( nsInstanceId, updateType; aws_config::AbstractAWSConfig=global_aws_config() diff --git a/src/services/wisdom.jl b/src/services/wisdom.jl index c994551161..b328d4f2bb 100644 --- a/src/services/wisdom.jl +++ b/src/services/wisdom.jl @@ -17,7 +17,8 @@ Creates an Amazon Connect Wisdom assistant. # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: - `"clientToken"`: A unique, case-sensitive identifier that you provide to ensure the - idempotency of the request. + idempotency of the request. If not provided, the Amazon Web Services SDK populates this + field. For more information about idempotency, see Making retries safe with idempotent APIs. - `"description"`: The description of the assistant. - `"serverSideEncryptionConfiguration"`: The KMS key used for encryption. - `"tags"`: The tags used to organize, track, or control access for this resource. @@ -71,7 +72,8 @@ only a single association. # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: - `"clientToken"`: A unique, case-sensitive identifier that you provide to ensure the - idempotency of the request. + idempotency of the request. If not provided, the Amazon Web Services SDK populates this + field. For more information about idempotency, see Making retries safe with idempotent APIs. - `"tags"`: The tags used to organize, track, or control access for this resource. """ function create_assistant_association( @@ -137,7 +139,8 @@ asset. # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: - `"clientToken"`: A unique, case-sensitive identifier that you provide to ensure the - idempotency of the request. + idempotency of the request. If not provided, the Amazon Web Services SDK populates this + field. For more information about idempotency, see Making retries safe with idempotent APIs. - `"metadata"`: A key/value map to store attributes without affecting tagging or recommendations. For example, when synchronizing data between an external system and Wisdom, you can store an external version identifier as metadata to utilize for determining @@ -190,20 +193,11 @@ end Creates a knowledge base. When using this API, you cannot reuse Amazon AppIntegrations DataIntegrations with external knowledge bases such as Salesforce and ServiceNow. If you -do, you'll get an InvalidRequestException error. <p>For example, you're -programmatically managing your external knowledge base, and you want to add or remove one -of the fields that is being ingested from Salesforce. Do the following:</p> -<ol> <li> <p>Call <a -href="https://docs.aws.amazon.com/wisdom/latest/APIReference/API_DeleteKnowledgeBase.ht -ml">DeleteKnowledgeBase</a>.</p> </li> <li> <p>Call -<a -href="https://docs.aws.amazon.com/appintegrations/latest/APIReference/API_DeleteDataInt -egration.html">DeleteDataIntegration</a>.</p> </li> <li> -<p>Call <a -href="https://docs.aws.amazon.com/appintegrations/latest/APIReference/API_CreateDataInt -egration.html">CreateDataIntegration</a> to recreate the DataIntegration or a -create different one.</p> </li> <li> <p>Call -CreateKnowledgeBase.</p> </li> </ol> </note> +do, you'll get an InvalidRequestException error. For example, you're programmatically +managing your external knowledge base, and you want to add or remove one of the fields that +is being ingested from Salesforce. Do the following: Call DeleteKnowledgeBase. Call +DeleteDataIntegration. Call CreateDataIntegration to recreate the DataIntegration or a +create different one. Call CreateKnowledgeBase. # Arguments - `knowledge_base_type`: The type of knowledge base. Only CUSTOM knowledge bases allow you @@ -214,7 +208,8 @@ CreateKnowledgeBase.</p> </li> </ol> </note> # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: - `"clientToken"`: A unique, case-sensitive identifier that you provide to ensure the - idempotency of the request. + idempotency of the request. If not provided, the Amazon Web Services SDK populates this + field. For more information about idempotency, see Making retries safe with idempotent APIs. - `"description"`: The description. - `"renderingConfiguration"`: Information about how to render the content. - `"serverSideEncryptionConfiguration"`: The KMS key used for encryption. @@ -277,7 +272,8 @@ Amazon Connect creates a new Wisdom session for each contact on which Wisdom is # Optional Parameters Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: - `"clientToken"`: A unique, case-sensitive identifier that you provide to ensure the - idempotency of the request. + idempotency of the request. If not provided, the Amazon Web Services SDK populates this + field. For more information about idempotency, see Making retries safe with idempotent APIs. - `"description"`: The description. - `"tags"`: The tags used to organize, track, or control access for this resource. """ diff --git a/src/services/workdocs.jl b/src/services/workdocs.jl index 08140bacd7..5449b76b48 100644 --- a/src/services/workdocs.jl +++ b/src/services/workdocs.jl @@ -1679,6 +1679,47 @@ function restore_document_versions( ) end +""" + search_resources() + search_resources(params::Dict{String,<:Any}) + +Searches metadata and the content of folders, documents, document versions, and comments. + +# Optional Parameters +Optional parameters can be passed as a `params::Dict{String,<:Any}`. Valid keys are: +- `"AdditionalResponseFields"`: A list of attributes to include in the response. Used to + request fields that are not normally returned in a standard response. +- `"Authentication"`: Amazon WorkDocs authentication token. Not required when using Amazon + Web Services administrator credentials to access the API. +- `"Filters"`: Filters results based on entity metadata. +- `"Limit"`: Max results count per page. +- `"Marker"`: The marker for the next set of results. +- `"OrderBy"`: Order by results in one or more categories. +- `"OrganizationId"`: Filters based on the resource owner OrgId. This is a mandatory + parameter when using Admin SigV4 credentials. +- `"QueryScopes"`: Filter based on the text field type. A Folder has only a name and no + content. A Comment has only content and no name. A Document or Document Version has a name + and content +- `"QueryText"`: The String to search for. Searches across different text fields based on + request parameters. Use double quotes around the query string for exact phrase matches. +""" +function search_resources(; aws_config::AbstractAWSConfig=global_aws_config()) + return workdocs( + "POST", "/api/v1/search"; aws_config=aws_config, feature_set=SERVICE_FEATURE_SET + ) +end +function search_resources( + params::AbstractDict{String}; aws_config::AbstractAWSConfig=global_aws_config() +) + return workdocs( + "POST", + "/api/v1/search", + params; + aws_config=aws_config, + feature_set=SERVICE_FEATURE_SET, + ) +end + """ update_document(document_id) update_document(document_id, params::Dict{String,<:Any})