You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* tasks. If you specify multiple capacity providers in a strategy that all have a weight
784
780
* of <code>0</code>, any <code>RunTask</code> or <code>CreateService</code> actions using
785
781
* the capacity provider strategy will fail.</p>
786
-
* <p>An example scenario for using weights is defining a strategy that contains two
787
-
* capacity providers and both have a weight of <code>1</code>, then when the
788
-
* <code>base</code> is satisfied, the tasks will be split evenly across the two
789
-
* capacity providers. Using that same logic, if you specify a weight of <code>1</code> for
790
-
* <i>capacityProviderA</i> and a weight of <code>4</code> for
791
-
* <i>capacityProviderB</i>, then for every one task that's run using
792
-
* <i>capacityProviderA</i>, four tasks would use
793
-
* <i>capacityProviderB</i>.</p>
782
+
* <p>Weight value characteristics:</p>
783
+
* <ul>
784
+
* <li>
785
+
* <p>Weight is considered after the base value is satisfied</p>
786
+
* </li>
787
+
* <li>
788
+
* <p>Default value is <code>0</code> if not specified</p>
789
+
* </li>
790
+
* <li>
791
+
* <p>Valid range: 0 to 1,000</p>
792
+
* </li>
793
+
* <li>
794
+
* <p>At least one capacity provider must have a weight greater than zero</p>
795
+
* </li>
796
+
* <li>
797
+
* <p>Capacity providers with weight of <code>0</code> cannot place tasks</p>
798
+
* </li>
799
+
* </ul>
800
+
* <p>Task distribution logic:</p>
801
+
* <ol>
802
+
* <li>
803
+
* <p>Base satisfaction: The minimum number of tasks specified by the base value are placed on that capacity provider</p>
804
+
* </li>
805
+
* <li>
806
+
* <p>Weight distribution: After base requirements are met, additional tasks are distributed according to weight ratios</p>
807
+
* </li>
808
+
* </ol>
809
+
* <p>Examples:</p>
810
+
* <p>Equal Distribution: Two capacity providers both with weight <code>1</code> will split tasks evenly after base requirements are met.</p>
811
+
* <p>Weighted Distribution: If capacityProviderA has weight <code>1</code> and capacityProviderB has weight <code>4</code>, then for every 1 task on A, 4 tasks will run on B.</p>
794
812
* @public
795
813
*/
796
814
weight?: number | undefined;
797
815
798
816
/**
799
817
* <p>The <i>base</i> value designates how many tasks, at a minimum, to run on
800
-
* the specified capacity provider. Only one capacity provider in a capacity provider
818
+
* the specified capacity provider for each service. Only one capacity provider in a capacity provider
801
819
* strategy can have a <i>base</i> defined. If no value is specified, the
802
820
* default value of <code>0</code> is used.</p>
821
+
* <p>Base value characteristics:</p>
822
+
* <ul>
823
+
* <li>
824
+
* <p>Only one capacity provider in a strategy can have a base defined</p>
825
+
* </li>
826
+
* <li>
827
+
* <p>Default value is <code>0</code> if not specified</p>
828
+
* </li>
829
+
* <li>
830
+
* <p>Valid range: 0 to 100,000</p>
831
+
* </li>
832
+
* <li>
833
+
* <p>Base requirements are satisfied first before weight distribution</p>
834
+
* </li>
835
+
* </ul>
803
836
* @public
804
837
*/
805
838
base?: number | undefined;
@@ -1175,7 +1208,7 @@ export interface Cluster {
1175
1208
1176
1209
/**
1177
1210
* <p>The number of services that are running on the cluster in an <code>ACTIVE</code>
1178
-
* state. You can view these services with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListServices.html">PListServices</a>.</p>
1211
+
* state. You can view these services with <a href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListServices.html">ListServices</a>.</p>
* <p>For information about Amazon Web Services CDK considerations, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/update-service-parameters.html">Amazon Web Services CDK considerations</a>.</p>
748
+
* <p>This parameter doesn't trigger a new service deployment.</p>
* that collects logs and metrics for increased visibility.
922
937
* Only the tasks that Amazon ECS services create are supported with Service Connect.
923
938
* For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html">Service Connect</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>
939
+
* <p>This parameter triggers a new service deployment.</p>
0 commit comments