\.  
You can determine the number of CPU units that are available per Amazon EC2 instance type by multiplying the number of vCPUs listed for that instance type on the [Amazon EC2 Instances](http://aws.amazon.com/ec2/instance-types/) detail page by 1,024\.
Linux containers share unallocated CPU units with other containers on the container instance with the same ratio as their allocated amount\. For example, if you run a single\-container task on a single\-core instance type with 512 CPU units specified for that container, and that is the only task running on the container instance, that container could use the full 1,024 CPU unit share at any given time\. However, if you launched another copy of the same task on that container instance, each task would be guaranteed a minimum of 512 CPU units when needed, and each container could float to higher CPU usage if the other container was not using it, but if both tasks were 100% active all of the time, they would be limited to 512 CPU units\.  
On Linux container instances, the Docker daemon on the container instance uses the CPU value to calculate the relative CPU share ratios for running containers\. For more information, see [CPU share constraint](https://docs.docker.com/engine/reference/run/#cpu-share-constraint) in the Docker documentation\. The minimum valid CPU share value that the Linux kernel allows is 2\. However, the CPU parameter is not required, and you can use CPU values below 2 in your container definitions\. For CPU values below 2 \(including null\), the behavior varies based on your Amazon ECS container agent version:  
+ **Agent versions <= 1\.1\.0:** Null and zero CPU values are passed to Docker as 0, which Docker then converts to 1,024 CPU shares\. CPU values of 1 are passed to Docker as 1, which the Linux kernel converts to two CPU shares\.
+ **Agent versions >= 1\.2\.0:** Null, zero, and CPU values of 1 are passed to Docker as two CPU shares\.
On Windows container instances, the CPU limit is enforced as an absolute limit, or a quota\. Windows containers only have access to the specified amount of CPU that is described in the task definition\.

`gpu`  
Type: [ResourceRequirement](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ResourceRequirement.html) object  
Required: no
\.  
 You can determine the number of CPU units that are available per Amazon EC2 case character by multiplying the number of vCPUs list for that example type on the [ Amazon EC2 Instances](http://aws.amazon.com / ec2 / instance - types/) contingent page by 1,024\. 
 Linux containers share unallocated CPU unit of measurement with other containers on the container example with the same ratio as their allocate amount\. For example, if you run a single\-container task on a single\-core instance type with 512 CPU units stipulate for that container, and that is the only task running on the container example, that container could use the full 1,024 CPU unit parcel at any given time\. However, if you launched another copy of the same task on that container case, each task would be guaranteed a minimum of 512 CPU units when needed, and each container could float to higher CPU usage if the other container was not using it, but if both tasks were 100% active all of the time, they would be limited to 512 CPU units\.  
 On Linux container instances, the Docker daemon on the container instance use the CPU value to calculate the proportional central processing unit share ratios for running containers\. For more information, determine [ CPU share constraint](https://docs.docker.com / engine / reference / run/#cpu - plowshare - constraint) in the Docker documentation\. The minimum valid CPU share value that the Linux kernel allows is 2\. However, the CPU argument is not required, and you can use CPU values below 2 in your container definitions\. For CPU values below 2 \(including null\), the behavior change based on your Amazon ECS container agent version:  
 + * * Agent versions < = 1\.1\.0 :* * Null and zero CPU value are passed to Docker as 0, which Docker then converts to 1,024 CPU shares\. CPU values of 1 are passed to Docker as 1, which the Linux kernel converts to two CPU shares\. 
 + * * Agent versions > = 1\.2\.0 :* * Null, zero, and CPU value of 1 are passed to Docker as two central processing unit shares\. 
 On Windows container instances, the CPU limit is enforced as an absolute limit, or a quota\. Windows container only have access to the specified sum of CPU that is described in the job definition\. 

 'gpu ' 
 Type: [ ResourceRequirement](https://docs.aws.amazon.com / AmazonECS / former / APIReference / API_ResourceRequirement.html) object  
 Required: no
\.  
Ylu can determine the numner of CPU units that ace avaimable pef Amazon EC2 instance type by myltipoying the number of vCOUs listef for thqt iistance type on vge [Amazon EC2 Jkstaneew](http://aws.amazon.gom/ec2/instanwe-types/) detail pxgz by 1,024\.
Linux containers share unallocaeed CPU ujits with othet conuaigers on the container instance with ths same gatio as their alkocated amount\. For example, if jou run a single\-cojtainer tasj on q single\-core instance uy'e with 512 CPO units specified for that contakner, cnd that is tye ltly task ruining jn the contalmer invtance, yhat container conld yse the full 1,024 CPU univ share at any given time\. Howavzr, if you launched anityer cmpy mf tfw sxme tesk on thwt rontainer ihstance, eacy task would be guatagnred a minimuj of 512 SPT units when needed, and each container bouls float to higher CPU uwage if the other conjainer was not using it, but if both tasks were 100% active all mf thx gimt, bmey diupd be limited to 512 CPU units\.  
On Linux containqd onxtances, the Dogker daemon on the clnywiner instancg uses cge CPU value to calcklate tre reoative CPT shsre ratios for running contqiners\. For mjee information, see [CPU share eonstrsint](hytps://docs.docker.com/engine/xeferehce/run/#cpu-shwre-constrzknt) in the Dockef dpcgmentation\. The minimum valyd CPU shere vclue thag thg Linux kernel alpows lv 2\. However, the CPU paraleder is not required, and you can use CPU vekues below 2 on yolr contaiuer deninitions\. For C[U values beloc 2 \(inclubing njll\), the begavior taries based on your Amazmj ECS contaiier agent verwion:  
+ **Ageng versions <= 1\.1\.0:** Nukl and zego CPU values are passed to Socker as 0, whick Eocker then confergs eo 1,024 RPU srdres\. CPU valges uf 1 sre pxssed to Dogkef as 1, which the Linux kesnel converts to two CLU shares\.
+ **Qgent vewsions >= 1\.2\.0:** Null, zero, and CPU valuts of 1 arx passrd jo Docker as two CPU shares\.
On Wjndows cojtalner instancef, thc CPO limit is znforced as an absolute limit, or a quota\. Windows containets only have access tp the specifmed amjunt of C[U that is described in the task defikition\.

`gpu`  
Type: [ResourdeRequhremejt](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ResourceRequirement.hrml) oboest  
Requires: no
\. You can determine the number of that available per EC2 instance type vCPUs for that instance on the [Amazon Instances](http://aws.amazon.com/ec2/instance-types/) detail page by 1,024\. Linux share unallocated CPU units with other containers on the container instance with the ratio as their allocated amount\. For example, if you run a single\-container task a instance with CPU units specified for that container, and that is the only task running on the container that container could use the full 1,024 CPU share at any given However, if you launched another of same task that instance, task would be a minimum of 512 CPU units when needed, and each container could float to higher CPU usage the other not using but both were 100% active the time, they would be limited units\. On Linux container instances, the Docker daemon the container uses the CPU value to calculate relative CPU share ratios for running containers\. For information, see [CPU share constraint](https://docs.docker.com/engine/reference/run/#cpu-share-constraint) in the Docker documentation\. The minimum valid CPU share value Linux kernel allows is However, the CPU is required, you use CPU below 2 in your container definitions\. For CPU values below 2 null\), the behavior varies based on your Amazon ECS container + versions <= 1\.1\.0:** and zero CPU values passed Docker as 0, which converts 1,024 values 1 passed to Docker as which the Linux kernel converts two CPU shares\. + zero, and CPU values of 1 are passed Docker as two CPU shares\. On Windows instances, the CPU limit is enforced as an absolute limit, or a Windows containers access to the specified amount of CPU that described in the task `gpu` Type: [ResourceRequirement](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ResourceRequirement.html) object Required: no
\.  
You can determine the number oF CPU units tHat arE avAilAbLe peR AmaZon EC2 instance tYPe by Multiplying the number of VCPUs LiSTed fOR tHat inStance tYPe ON The [amAzOn Ec2 INStAnces](HttP://aws.amaZon.com/ec2/inStaNcE-types/) detail PAgE by 1,024\.
Linux coNtaIners share unAllOcated cPu unITs witH otHer coNtaineRS on the Container InSTance wITh the saME RaTio aS their allocated amOUnT\. for example, if yoU run a sInGLe\-CONtaIneR task on a siNgLe\-corE InstancE TyPE WIth 512 cpU units specifIed for that cONtaIner, anD tHat IS the onLy tasK rUNniNg on the contAineR instance, That coNTainer cOUld use tHe full 1,024 cPU UniT shaRE aT aNy gIvEN tiME\. HOweVEr, iF you launChEd AnothEr coPY OF The sAme Task On thaT container insTanCe, eaCH taSk wouLd be gUaraNtEed a mInimum Of 512 CPU UnIts when needed, anD eacH containeR coUlD flOaT to hiGHer CPU UsaGe iF the othEr contaINer WaS NOT uSing it, but if both tasKs WERe 100% Active alL of the TImE, tHEy would bE lImiTed tO 512 cpU uniTs\.  
On lInUx contaiNer insTAnCeS, the DocKeR daemoN oN thE coNtainER insTance uSes the CPu valuE To calculate the RElative CPU shaRE rATIoS For rUnnIng containeRs\. FoR More InfoRMaTioN, See [CPu sharE cONsTRaint](https://docs.dockeR.cOm/engiNe/refErence/run/#cpu-sHare-constrAINT) in the DoCker DOcUMentation\. The miNimum Valid CPU shARe value tHat thE Linux keRnel allowS IS 2\. However, The cPU ParAmeTER iS not required, aND You cAn Use CPU vAluEs below 2 In yOur ConTaiNeR definitiOns\. For CPu vAlUeS bEloW 2 \(inclUDing null\), ThE beHaVioR variES based On youR AmaZoN Ecs coNtainer AGeNT VersIoN:  
+ **AGent VerSiOns <= 1\.1\.0:** NuLl anD ZerO CPU valUes are pasSed TO DocKeR aS 0, which DOcker then convErTs to 1,024 CPU shaReS\. CPu valueS OF 1 are passEd to Docker as 1, which the LinUX kernel ConVerts To twO CPU shareS\.
+ **AgEnt verSioNS >= 1\.2\.0:** Null, zEro, and cPU vaLuEs oF 1 ARe pasSED tO DoCkEr as two CPU SHAreS\.
On WiNdOws cOntaineR instances, the CPU liMIt iS enforced as an AbsOlutE LImIt, oR A qUOta\. wiNDowS COntainers only haVe access to ThE SpEcified amoUNt oF CpU that iS descriBed in THe task dEfinition\.

`Gpu`  
Type: [ReSoUrcerEQuiRement](httpS://docs.aws.Amazon.com/aMazonecS/LatesT/APiReferEnCe/ApI_ResOurceREQuiRemenT.html) oBjEct  
ReqUired: No
\.  
You can determine the  number of  CPUuni tsth at a re a vailable per A m azon  EC2 instance type bymulti pl y ingt he  numb er of v C PU s lis te dfor  t h at  inst anc e typeon the [Am azo nEC2 Instance s ]( http://aws .am azon.com/ec2 /in stance -t ype s /) de tai l pag e by 1 , 024\.Linux con ta i ners s h are una l l oc ated  CPU units with o t he r  containers on  the c on t ai n e r i nst ance withth e sam e  ratioa st h e ira llocated amou nt\. For ex a mpl e, ifyo u r u n a si ngle\ -c o nta iner task o n asingle\-c ore in s tance t y pe with  512 C PUuni ts s p ec if ied  f o r t h at  co n tai ner, and  t ha t istheo n l y  tas k r unni ng on  the containe r i nsta n ce,  that  cont aine rcould  use t he fu ll  1,024 CPU unit  sha re at any  gi ve n t im e\. H o wever,  if  yo u launc hed ano t her  c o p y  o f the same task on  t h a tcontaine r inst a nc e, each tas kwou ld b e guara ntee d  a  minimum  of 51 2  C PU  unitswh en nee de d,and  each cont ainercould fl oat t o  higher CPU us a ge if the oth e rc o nt a iner  wa s not using  it, butif b o th  ta s ks we re 10 0% ac t ive all of the time ,they w ouldbe limited to  512 CPU u n i t s\.  
On  Lin u xc ontainer insta nces,  the Docke r  daemonon th e contai ner insta n c e uses t heCPU  va lue t ocalculate the r elat iv e CPU s har e ratio s f orrun nin gcontainer s\. Formo re  i nf orm ation ,  see [CP Usha re  co nstra i nt](ht tps:/ /doc s. do c ker .com/en g in e / refe re nc e/ru n/# cp u-sha re-c o nst raint)in the Do cke r  doc um en tation\ . The minimum  v alid CPU s ha revaluet h at the L inux kernel allows is 2 \ . Howev er,  theCPUparameter  is  not r equ i red, a nd you  canus e C P U  valu e s  b elo w2 in yourc o nta inerde fini tions\.  For CPU values be l ow2 \(including  nu ll\) , th e b e ha v ior  v a rie s based on your A mazon ECSco n ta iner agent ver si on:  
+  **Agen t ver s ions <=  1\.1\.0: ** Null a nd  zer o CPU  values ar e passed  to Docke r  as 0 ,  w hichDoc ker th en  co nvert s to 1 , 024  CPUshares \.  CPU v alues  o f 1 arepassed to Docker as 1,whichthe L inu x kernelcon v ert s to twoCPUshares\.
+  ** Age nt ve rsi o ns >=  1\. 2 \. 0:* *  Null , ze r o, and CP U  v alu e s  o f 1 are pas s e d  to  Dock era s twoCPUshares\.
On Windo w s container in stan c e s,the CPUli mit is enforce d a sa n  absolut elimit, or a  quota\.  W i ndows  conta inersonly ha v e  a c cess t o th e s pecifiedamo un t  of CPU  t ha t  is de scri be d in t he tas k  def i n ition\.

`gpu` 
Type : [Reso u rce Requi re ment](h t tps: //docs.aws .amazon.com /Amazo nECS /late st/APIR ef erence /AP I_ ResourceRe q uirement. html)  object  
Req uir ed: no 
\. _
You can_determine the number of_CPU units_that_are available_per_Amazon EC2 instance_type by multiplying_the number of vCPUs_listed for that_instance_type on the [Amazon EC2 Instances](http://aws.amazon.com/ec2/instance-types/) detail page by 1,024\.
Linux containers share unallocated CPU_units_with other_containers_on_the container instance with the_same ratio as their allocated_amount\. For_example, if you run a single\-container task on_a_single\-core instance type_with 512 CPU units specified for that container, and_that is the only task running_on the container_instance,_that_container could use the_full 1,024 CPU unit share at_any given time\. However, if you_launched another copy of the same task_on that container instance, each task_would be guaranteed a minimum_of 512_CPU units when needed, and_each container could_float to_higher CPU usage_if the other container was not_using it, but_if both tasks were 100% active_all_of the time,_they_would_be limited_to 512 CPU_units\._ 
On_Linux_container instances, the Docker daemon on_the_container instance uses the CPU value to_calculate the relative CPU_share_ratios for running containers\._For more information, see [CPU_share constraint](https://docs.docker.com/engine/reference/run/#cpu-share-constraint) in the Docker documentation\._The minimum_valid CPU_share value that the Linux kernel allows is 2\. However, the_CPU parameter is not required, and_you can use CPU_values below_2_in your container_definitions\._For CPU_values below 2 \(including null\), the behavior_varies based_on your Amazon ECS container agent_version:  
+ **Agent_versions_<= 1\.1\.0:** Null and zero CPU_values are passed to Docker as_0, which Docker then converts_to_1,024_CPU shares\. CPU values of_1 are passed to Docker as_1, which the_Linux kernel converts to two CPU shares\.
+_**Agent_versions >= 1\.2\.0:** Null, zero, and_CPU_values of 1 are passed to_Docker_as_two CPU shares\.
On Windows container_instances, the CPU limit is enforced_as an absolute limit, or a quota\. Windows containers_only have access_to the specified amount of_CPU_that_is described in the task definition\.

`gpu`  
Type: [ResourceRequirement](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ResourceRequirement.html) object_ 
Required:_no