Skip to content

Commit

Permalink
Updates SDK to v2.676.0
Browse files Browse the repository at this point in the history
  • Loading branch information
awstools committed May 13, 2020
1 parent b5d439c commit 4b8bcd0
Show file tree
Hide file tree
Showing 20 changed files with 12,672 additions and 47 deletions.
12 changes: 12 additions & 0 deletions .changes/2.676.0.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
[
{
"type": "feature",
"category": "ElastiCache",
"description": "Amazon ElastiCache now supports auto-update of ElastiCache clusters after the \"recommended apply by date\" of service update has passed. ElastiCache will use your maintenance window to schedule the auto-update of applicable clusters. For more information, see https://docs.aws.amazon.com/AmazonElastiCache/latest/mem-ug/Self-Service-Updates.html and https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/Self-Service-Updates.html"
},
{
"type": "feature",
"category": "Macie2",
"description": "This release introduces a new major version of the Amazon Macie API. You can use this version of the API to develop tools and applications that interact with the new Amazon Macie."
}
]
6 changes: 5 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,11 @@
# Changelog for AWS SDK for JavaScript
<!--LATEST=2.675.0-->
<!--LATEST=2.676.0-->
<!--ENTRYINSERT-->

## 2.676.0
* feature: ElastiCache: Amazon ElastiCache now supports auto-update of ElastiCache clusters after the "recommended apply by date" of service update has passed. ElastiCache will use your maintenance window to schedule the auto-update of applicable clusters. For more information, see https://docs.aws.amazon.com/AmazonElastiCache/latest/mem-ug/Self-Service-Updates.html and https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/Self-Service-Updates.html
* feature: Macie2: This release introduces a new major version of the Amazon Macie API. You can use this version of the API to develop tools and applications that interact with the new Amazon Macie.

## 2.675.0
* feature: WorkMail: Minor API fixes and updates to the documentation.

Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ version.
To use the SDK in the browser, simply add the following script tag to your
HTML pages:

<script src="https://sdk.amazonaws.com/js/aws-sdk-2.675.0.min.js"></script>
<script src="https://sdk.amazonaws.com/js/aws-sdk-2.676.0.min.js"></script>

You can also build a custom browser SDK with your specified set of AWS services.
This can allow you to reduce the SDK's size, specify different API versions of
Expand Down
29 changes: 16 additions & 13 deletions apis/elasticache-2015-02-02.normal.json
Original file line number Diff line number Diff line change
Expand Up @@ -358,7 +358,7 @@
"shape": "InvalidParameterValueException"
}
],
"documentation": "<p>Global Datastore for Redis offers fully managed, fast, reliable and secure cross-region replication. Using Global Datastore for Redis, you can create cross-region read replica clusters for ElastiCache for Redis to enable low-latency reads and disaster recovery across regions. For more information, see <a href=\"/AmazonElastiCache/latest/red-ug/Redis-Global-Clusters.html\">Replication Across Regions Using Global Datastore</a>. </p> <ul> <li> <p>The <b>GlobalReplicationGroupId</b> is the name of the Global Datastore.</p> </li> <li> <p>The <b>PrimaryReplicationGroupId</b> represents the name of the primary cluster that accepts writes and will replicate updates to the secondary cluster.</p> </li> </ul>"
"documentation": "<p>Global Datastore for Redis offers fully managed, fast, reliable and secure cross-region replication. Using Global Datastore for Redis, you can create cross-region read replica clusters for ElastiCache for Redis to enable low-latency reads and disaster recovery across regions. For more information, see <a href=\"/AmazonElastiCache/latest/red-ug/Redis-Global-Clusters.html\">Replication Across Regions Using Global Datastore</a>. </p> <ul> <li> <p>The <b>GlobalReplicationGroupIdSuffix</b> is the name of the Global Datastore.</p> </li> <li> <p>The <b>PrimaryReplicationGroupId</b> represents the name of the primary cluster that accepts writes and will replicate updates to the secondary cluster.</p> </li> </ul>"
},
"CreateReplicationGroup": {
"name": "CreateReplicationGroup",
Expand Down Expand Up @@ -685,7 +685,7 @@
"shape": "InvalidParameterValueException"
}
],
"documentation": "<p>Deleting a Global Datastore is a two-step process: </p> <ul> <li> <p>First, you must <a>DisassociateGlobalReplicationGroup</a> to remove the secondary clusters in the Global Datastore.</p> </li> <li> <p>Once the Global Datastore contains only the primary cluster, you can use DeleteGlobalReplicationGroup API to delete the Global Datastore while retainining the primary cluster using Retain…= true.</p> </li> </ul> <p>Since the Global Datastore has only a primary cluster, you can delete the Global Datastore while retaining the primary by setting <code>RetainPrimaryCluster=true</code>.</p> <p>When you receive a successful response from this operation, Amazon ElastiCache immediately begins deleting the selected resources; you cannot cancel or revert this operation.</p> <note> <p>This operation is valid for Redis only.</p> </note>"
"documentation": "<p>Deleting a Global Datastore is a two-step process: </p> <ul> <li> <p>First, you must <a>DisassociateGlobalReplicationGroup</a> to remove the secondary clusters in the Global Datastore.</p> </li> <li> <p>Once the Global Datastore contains only the primary cluster, you can use DeleteGlobalReplicationGroup API to delete the Global Datastore while retainining the primary cluster using Retain…= true.</p> </li> </ul> <p>Since the Global Datastore has only a primary cluster, you can delete the Global Datastore while retaining the primary by setting <code>RetainPrimaryCluster=true</code>.</p> <p>When you receive a successful response from this operation, Amazon ElastiCache immediately begins deleting the selected resources; you cannot cancel or revert this operation.</p>"
},
"DeleteReplicationGroup": {
"name": "DeleteReplicationGroup",
Expand Down Expand Up @@ -1177,7 +1177,7 @@
"shape": "InvalidParameterCombinationException"
}
],
"documentation": "<p>Used to failover the primary region to a selected secondary region.</p>"
"documentation": "<p>Used to failover the primary region to a selected secondary region. The selected secondary region will be come primary, and all other clusters will become secondary.</p>"
},
"IncreaseNodeGroupsInGlobalReplicationGroup": {
"name": "IncreaseNodeGroupsInGlobalReplicationGroup",
Expand Down Expand Up @@ -1507,7 +1507,7 @@
"shape": "InvalidParameterCombinationException"
}
],
"documentation": "<p>Modifies the settings for a replication group.</p> <p>For Redis (cluster mode enabled) clusters, this operation cannot be used to change a cluster's node type or engine version. For more information, see:</p> <ul> <li> <p> <a href=\"https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/scaling-redis-cluster-mode-enabled.html\">Scaling for Amazon ElastiCache for Redis (cluster mode enabled)</a> in the ElastiCache User Guide</p> </li> <li> <p> <a href=\"https://docs.aws.amazon.com/AmazonElastiCache/latest/APIReference/API_ModifyReplicationGroupShardConfiguration.html\">ModifyReplicationGroupShardConfiguration</a> in the ElastiCache API Reference</p> </li> </ul> <note> <p>This operation is valid for Redis only.</p> </note>"
"documentation": "<p>Modifies the settings for a replication group.</p> <ul> <li> <p> <a href=\"https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/scaling-redis-cluster-mode-enabled.html\">Scaling for Amazon ElastiCache for Redis (cluster mode enabled)</a> in the ElastiCache User Guide</p> </li> <li> <p> <a href=\"https://docs.aws.amazon.com/AmazonElastiCache/latest/APIReference/API_ModifyReplicationGroupShardConfiguration.html\">ModifyReplicationGroupShardConfiguration</a> in the ElastiCache API Reference</p> </li> </ul> <note> <p>This operation is valid for Redis only.</p> </note>"
},
"ModifyReplicationGroupShardConfiguration": {
"name": "ModifyReplicationGroupShardConfiguration",
Expand Down Expand Up @@ -1612,7 +1612,7 @@
"shape": "InvalidParameterValueException"
}
],
"documentation": "<p>Redistribute slots to ensure unifirom distribution across existing shards in the cluster.</p>"
"documentation": "<p>Redistribute slots to ensure uniform distribution across existing shards in the cluster.</p>"
},
"RebootCacheCluster": {
"name": "RebootCacheCluster",
Expand Down Expand Up @@ -2822,7 +2822,7 @@
"members": {
"GlobalReplicationGroupIdSuffix": {
"shape": "String",
"documentation": "<p>The suffix for name of a Global Datastore. The suffix guarantees uniqueness of the Global Datastore name across multiple regions.</p>"
"documentation": "<p>The suffix name of a Global Datastore. The suffix guarantees uniqueness of the Global Datastore name across multiple regions.</p>"
},
"GlobalReplicationGroupDescription": {
"shape": "String",
Expand Down Expand Up @@ -2887,7 +2887,7 @@
},
"NodeGroupConfiguration": {
"shape": "NodeGroupConfigurationList",
"documentation": "<p>A list of node group (shard) configuration options. Each node group (shard) configuration has the following members: <code>PrimaryAvailabilityZone</code>, <code>ReplicaAvailabilityZones</code>, <code>ReplicaCount</code>, and <code>Slots</code>.</p> <p>If you're creating a Redis (cluster mode disabled) or a Redis (cluster mode enabled) replication group, you can use this parameter to individually configure each node group (shard), or you can omit this parameter. However, when seeding a Redis (cluster mode enabled) cluster from a S3 rdb file, you must configure each node group (shard) using this parameter because you must specify the slots for each node group.</p>"
"documentation": "<p>A list of node group (shard) configuration options. Each node group (shard) configuration has the following members: <code>PrimaryAvailabilityZone</code>, <code>ReplicaAvailabilityZones</code>, <code>ReplicaCount</code>, and <code>Slots</code>.</p> <p>If you're creating a Redis (cluster mode disabled) or a Redis (cluster mode enabled) replication group, you can use this parameter to individually configure each node group (shard), or you can omit this parameter. However, it is required when seeding a Redis (cluster mode enabled) cluster from a S3 rdb file. You must configure each node group (shard) using this parameter because you must specify the slots for each node group.</p>"
},
"CacheNodeType": {
"shape": "String",
Expand Down Expand Up @@ -3185,7 +3185,7 @@
},
"RetainPrimaryReplicationGroup": {
"shape": "Boolean",
"documentation": "<p>If set to <code>true</code>, the primary replication is retained as a standalone replication group. </p>"
"documentation": "<p>The primary replication group is retained as a standalone replication group. </p>"
}
}
},
Expand Down Expand Up @@ -3900,7 +3900,7 @@
},
"Engine": {
"shape": "String",
"documentation": "<p>The Elasticache engine. For preview, it is Redis only.</p>"
"documentation": "<p>The Elasticache engine. For Redis only.</p>"
},
"EngineVersion": {
"shape": "String",
Expand Down Expand Up @@ -3931,7 +3931,7 @@
"documentation": "<p>A flag that enables encryption at rest when set to <code>true</code>.</p> <p>You cannot modify the value of <code>AtRestEncryptionEnabled</code> after the replication group is created. To enable encryption at rest on a replication group you must set <code>AtRestEncryptionEnabled</code> to <code>true</code> when you create the replication group. </p> <p> <b>Required:</b> Only available when creating a replication group in an Amazon VPC using redis version <code>3.2.6</code>, <code>4.x</code> or later.</p>"
}
},
"documentation": "<p>Consists of a primary cluster that accepts writes and an associated secondary cluster that resides in a different AWS region. The secondary cluster accepts only reads. The primary cluster automatically replicates updates to the secondary cluster.</p> <ul> <li> <p>The <b>GlobalReplicationGroupId</b> represents the name of the Global Datastore, which is what you use to associate a secondary cluster.</p> </li> </ul>",
"documentation": "<p>Consists of a primary cluster that accepts writes and an associated secondary cluster that resides in a different AWS region. The secondary cluster accepts only reads. The primary cluster automatically replicates updates to the secondary cluster.</p> <ul> <li> <p>The <b>GlobalReplicationGroupIdSuffix</b> represents the name of the Global Datastore, which is what you use to associate a secondary cluster.</p> </li> </ul>",
"wrapper": true
},
"GlobalReplicationGroupInfo": {
Expand Down Expand Up @@ -4248,7 +4248,7 @@
},
"ApplyImmediately": {
"shape": "Boolean",
"documentation": "<p>If true, this parameter causes the modifications in this request and any pending modifications to be applied, asynchronously and as soon as possible, regardless of the PreferredMaintenanceWindow setting for the replication group. If false, changes to the nodes in the replication group are applied on the next maintenance reboot, or the next failure reboot, whichever occurs first. </p>"
"documentation": "<p>This parameter causes the modifications in this request and any pending modifications to be applied, asynchronously and as soon as possible. Modifications to Global Replication Groups cannot be requested to be applied in PreferredMaintenceWindow. </p>"
},
"CacheNodeType": {
"shape": "String",
Expand Down Expand Up @@ -5886,15 +5886,18 @@
"in-progress",
"stopping",
"stopped",
"complete"
"complete",
"scheduling",
"scheduled",
"not-applicable"
]
},
"UpdateActionStatusList": {
"type": "list",
"member": {
"shape": "UpdateActionStatus"
},
"max": 6
"max": 9
},
"UpdateActionsMessage": {
"type": "structure",
Expand Down
Loading

0 comments on commit 4b8bcd0

Please sign in to comment.