aws-sdk-ecs 1.6.0 → 1.7.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 53753bedee288b71f54f3c7159fb138c33258636
4
- data.tar.gz: e51e5731b26691a59852e41588bb86a5706ac42f
3
+ metadata.gz: 1192b07cf1d3c418a52e3b6f24232c709f194c33
4
+ data.tar.gz: 459dda7b74df8222d05a24d9e032cd911a6af557
5
5
  SHA512:
6
- metadata.gz: ca4c4779b0511d4692d89173adb7d6fdc1a228154530918ececeea26c1d1a9d5cdd802252ea6eb14c927dddd50e36a12ce114bc0c2fcad469d1419d4de147c8f
7
- data.tar.gz: db2e94f0a85499247d5e13b559c19a5ac6c2f2be23d7b6143e55982f7eb3bdb6585f9d5d9492a67e7a13859833ffe5c1fb6e8322ec594b7536a70f1f57508709
6
+ metadata.gz: 97707f6e2e42433deea9adc95b0d992e4e5d82bd98fecba10f76e88b94956791c4e4731c3cfe03d3afe0f75820d69df0cb4bf756274b384e38814f8a37e46ad2
7
+ data.tar.gz: debdcf457e39e5edac642f31f71bebde5a73df26bcf79892a6321b369cb9d9dbdeb35e409a1fb9f0385041e21f7007faa5f22ee34c5b731e9d2d38c88e584ef9
@@ -43,6 +43,6 @@ require_relative 'aws-sdk-ecs/customizations'
43
43
  # @service
44
44
  module Aws::ECS
45
45
 
46
- GEM_VERSION = '1.6.0'
46
+ GEM_VERSION = '1.7.0'
47
47
 
48
48
  end
@@ -2864,6 +2864,10 @@ module Aws::ECS
2864
2864
  # of the same task on a single container instance when port mappings are
2865
2865
  # used.
2866
2866
  #
2867
+ # Docker for Windows uses different network modes than Docker for Linux.
2868
+ # When you register a task definition with Windows containers, you must
2869
+ # not specify a network mode.
2870
+ #
2867
2871
  # For more information, see [Network settings][2] in the *Docker run
2868
2872
  # reference*.
2869
2873
  #
@@ -4371,7 +4375,7 @@ module Aws::ECS
4371
4375
  params: params,
4372
4376
  config: config)
4373
4377
  context[:gem_name] = 'aws-sdk-ecs'
4374
- context[:gem_version] = '1.6.0'
4378
+ context[:gem_version] = '1.7.0'
4375
4379
  Seahorse::Client::Request.new(handlers, context)
4376
4380
  end
4377
4381
 
@@ -419,20 +419,15 @@ module Aws::ECS
419
419
  # @return [String]
420
420
  #
421
421
  # @!attribute [rw] cpu
422
- # The number of `cpu` units reserved for the container. If your
423
- # containers will be part of a task using the Fargate launch type,
424
- # this field is optional and the only requirement is that the total
425
- # amount of CPU reserved for all containers within a task be lower
426
- # than the task `cpu` value.
422
+ # The number of `cpu` units reserved for the container. This parameter
423
+ # maps to `CpuShares` in the [Create a container][1] section of the
424
+ # [Docker Remote API][2] and the `--cpu-shares` option to [docker
425
+ # run][3].
427
426
  #
428
- # For containers that will be part of a task using the EC2 launch
429
- # type, a container instance has 1,024 `cpu` units for every CPU core.
430
- # This parameter specifies the minimum amount of CPU to reserve for a
431
- # container, and containers share unallocated CPU units with other
432
- # containers on the instance with the same ratio as their allocated
433
- # amount. This parameter maps to `CpuShares` in the [Create a
434
- # container][1] section of the [Docker Remote API][2] and the
435
- # `--cpu-shares` option to [docker run][3].
427
+ # This field is optional for tasks using the Fargate launch type, and
428
+ # the only requirement is that the total amount of CPU reserved for
429
+ # all containers within a task be lower than the task-level `cpu`
430
+ # value.
436
431
  #
437
432
  # <note markdown="1"> You can determine the number of CPU units that are available per EC2
438
433
  # instance type by multiplying the vCPUs listed for that instance type
@@ -451,14 +446,28 @@ module Aws::ECS
451
446
  # were 100% active all of the time, they would be limited to 512 CPU
452
447
  # units.
453
448
  #
454
- # The Docker daemon on the container instance uses the CPU value to
455
- # calculate the relative CPU share ratios for running containers. For
456
- # more information, see [CPU share constraint][5] in the Docker
457
- # documentation. The minimum valid CPU share value that the Linux
458
- # kernel allows is 2; however, the CPU parameter is not required, and
459
- # you can use CPU values below 2 in your container definitions. For
460
- # CPU values below 2 (including null), the behavior varies based on
461
- # your Amazon ECS container agent version:
449
+ # Linux containers share unallocated CPU units with other containers
450
+ # on the container instance with the same ratio as their allocated
451
+ # amount. For example, if you run a single-container task on a
452
+ # single-core instance type with 512 CPU units specified for that
453
+ # container, and that is the only task running on the container
454
+ # instance, that container could use the full 1,024 CPU unit share at
455
+ # any given time. However, if you launched another copy of the same
456
+ # task on that container instance, each task would be guaranteed a
457
+ # minimum of 512 CPU units when needed, and each container could float
458
+ # to higher CPU usage if the other container was not using it, but if
459
+ # both tasks were 100% active all of the time, they would be limited
460
+ # to 512 CPU units.
461
+ #
462
+ # On Linux container instances, the Docker daemon on the container
463
+ # instance uses the CPU value to calculate the relative CPU share
464
+ # ratios for running containers. For more information, see [CPU share
465
+ # constraint][5] in the Docker documentation. The minimum valid CPU
466
+ # share value that the Linux kernel will allow is 2; however, the CPU
467
+ # parameter is not required, and you can use CPU values below 2 in
468
+ # your container definitions. For CPU values below 2 (including null),
469
+ # the behavior varies based on your Amazon ECS container agent
470
+ # version:
462
471
  #
463
472
  # * **Agent versions less than or equal to 1.1.0:** Null and zero CPU
464
473
  # values are passed to Docker as 0, which Docker then converts to
@@ -468,6 +477,11 @@ module Aws::ECS
468
477
  # * **Agent versions greater than or equal to 1.2.0:** Null, zero, and
469
478
  # CPU values of 1 are passed to Docker as 2.
470
479
  #
480
+ # On Windows container instances, the CPU limit is enforced as an
481
+ # absolute limit, or a quota. Windows containers only have access to
482
+ # the specified amount of CPU that is described in the task
483
+ # definition.
484
+ #
471
485
  #
472
486
  #
473
487
  # [1]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -543,17 +557,20 @@ module Aws::ECS
543
557
  #
544
558
  # @!attribute [rw] links
545
559
  # The `link` parameter allows containers to communicate with each
546
- # other without the need for port mappings, using the `name` parameter
547
- # and optionally, an `alias` for the link. This construct is analogous
548
- # to `name:alias` in Docker links. This field is not valid for
549
- # containers in tasks using the Fargate launch type. Up to 255 letters
550
- # (uppercase and lowercase), numbers, hyphens, and underscores are
551
- # allowed for each `name` and `alias`. For more information on linking
552
- # Docker containers, see
560
+ # other without the need for port mappings. Only supported if the
561
+ # network mode of a task definition is set to `bridge`. The
562
+ # `name:internalName` construct is analogous to `name:alias` in Docker
563
+ # links. Up to 255 letters (uppercase and lowercase), numbers,
564
+ # hyphens, and underscores are allowed. For more information about
565
+ # linking Docker containers, go to
553
566
  # [https://docs.docker.com/engine/userguide/networking/default\_network/dockerlinks/][1].
554
567
  # This parameter maps to `Links` in the [Create a container][2]
555
- # section of the [Docker Remote API][3] and the `--link` option to
556
- # [docker run][4].
568
+ # section of the [Docker Remote API][3] and the `--link` option to [
569
+ # `docker run` ][4].
570
+ #
571
+ # <note markdown="1"> This parameter is not supported for Windows containers.
572
+ #
573
+ # </note>
557
574
  #
558
575
  # Containers that are collocated on a single container instance may be
559
576
  # able to communicate with each other without requiring links or host
@@ -565,7 +582,7 @@ module Aws::ECS
565
582
  # [1]: https://docs.docker.com/engine/userguide/networking/default_network/dockerlinks/
566
583
  # [2]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
567
584
  # [3]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/
568
- # [4]: https://docs.docker.com/engine/reference/run/
585
+ # [4]: https://docs.docker.com/engine/reference/commandline/run/
569
586
  # @return [Array<String>]
570
587
  #
571
588
  # @!attribute [rw] port_mappings
@@ -573,10 +590,15 @@ module Aws::ECS
573
590
  # containers to access ports on the host container instance to send or
574
591
  # receive traffic.
575
592
  #
576
- # If using containers in a task with the Fargate, exposed ports should
577
- # be specified using `containerPort`. The `hostPort` can be left blank
593
+ # For task definitions that use the `awsvpc` network mode, you should
594
+ # only specify the `containerPort`. The `hostPort` can be left blank
578
595
  # or it must be the same value as the `containerPort`.
579
596
  #
597
+ # Port mappings on Windows use the `NetNAT` gateway address rather
598
+ # than `localhost`. There is no loopback for port mappings on Windows,
599
+ # so you cannot access a container's mapped port from the host
600
+ # itself.
601
+ #
580
602
  # This parameter maps to `PortBindings` in the [Create a container][1]
581
603
  # section of the [Docker Remote API][2] and the `--publish` option to
582
604
  # [docker run][3]. If the network mode of a task definition is set to
@@ -673,13 +695,14 @@ module Aws::ECS
673
695
  # @!attribute [rw] mount_points
674
696
  # The mount points for data volumes in your container.
675
697
  #
676
- # If using the Fargate launch type, the `sourceVolume` parameter is
677
- # not supported.
678
- #
679
698
  # This parameter maps to `Volumes` in the [Create a container][1]
680
699
  # section of the [Docker Remote API][2] and the `--volume` option to
681
700
  # [docker run][3].
682
701
  #
702
+ # Windows containers can mount whole directories on the same drive as
703
+ # `$env:ProgramData`. Windows containers cannot mount directories on a
704
+ # different drive, and mount point cannot be across drives.
705
+ #
683
706
  #
684
707
  #
685
708
  # [1]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -701,8 +724,12 @@ module Aws::ECS
701
724
  #
702
725
  # @!attribute [rw] linux_parameters
703
726
  # Linux-specific modifications that are applied to the container, such
704
- # as Linux KernelCapabilities. This field is not valid for containers
705
- # in tasks using the Fargate launch type.
727
+ # as Linux KernelCapabilities.
728
+ #
729
+ # <note markdown="1"> This parameter is not supported for Windows containers or tasks
730
+ # using the Fargate launch type.
731
+ #
732
+ # </note>
706
733
  # @return [Types::LinuxParameters]
707
734
  #
708
735
  # @!attribute [rw] hostname
@@ -722,6 +749,10 @@ module Aws::ECS
722
749
  # `User` in the [Create a container][1] section of the [Docker Remote
723
750
  # API][2] and the `--user` option to [docker run][3].
724
751
  #
752
+ # <note markdown="1"> This parameter is not supported for Windows containers.
753
+ #
754
+ # </note>
755
+ #
725
756
  #
726
757
  #
727
758
  # [1]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -747,6 +778,10 @@ module Aws::ECS
747
778
  # container. This parameter maps to `NetworkDisabled` in the [Create a
748
779
  # container][1] section of the [Docker Remote API][2].
749
780
  #
781
+ # <note markdown="1"> This parameter is not supported for Windows containers.
782
+ #
783
+ # </note>
784
+ #
750
785
  #
751
786
  #
752
787
  # [1]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -760,6 +795,11 @@ module Aws::ECS
760
795
  # container][1] section of the [Docker Remote API][2] and the
761
796
  # `--privileged` option to [docker run][3].
762
797
  #
798
+ # <note markdown="1"> This parameter is not supported for Windows containers or tasks
799
+ # using the Fargate launch type.
800
+ #
801
+ # </note>
802
+ #
763
803
  #
764
804
  #
765
805
  # [1]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -773,6 +813,10 @@ module Aws::ECS
773
813
  # the [Create a container][1] section of the [Docker Remote API][2]
774
814
  # and the `--read-only` option to `docker run`.
775
815
  #
816
+ # <note markdown="1"> This parameter is not supported for Windows containers.
817
+ #
818
+ # </note>
819
+ #
776
820
  #
777
821
  #
778
822
  # [1]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -785,6 +829,10 @@ module Aws::ECS
785
829
  # the [Docker Remote API][2] and the `--dns` option to [docker
786
830
  # run][3].
787
831
  #
832
+ # <note markdown="1"> This parameter is not supported for Windows containers.
833
+ #
834
+ # </note>
835
+ #
788
836
  #
789
837
  #
790
838
  # [1]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -798,6 +846,10 @@ module Aws::ECS
798
846
  # section of the [Docker Remote API][2] and the `--dns-search` option
799
847
  # to [docker run][3].
800
848
  #
849
+ # <note markdown="1"> This parameter is not supported for Windows containers.
850
+ #
851
+ # </note>
852
+ #
801
853
  #
802
854
  #
803
855
  # [1]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -813,6 +865,10 @@ module Aws::ECS
813
865
  # [Create a container][1] section of the [Docker Remote API][2] and
814
866
  # the `--add-host` option to [docker run][3].
815
867
  #
868
+ # <note markdown="1"> This parameter is not supported for Windows containers.
869
+ #
870
+ # </note>
871
+ #
816
872
  #
817
873
  #
818
874
  # [1]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -836,6 +892,8 @@ module Aws::ECS
836
892
  # information, see [Amazon ECS Container Agent Configuration][4] in
837
893
  # the *Amazon Elastic Container Service Developer Guide*.
838
894
  #
895
+ # This parameter is not supported for Windows containers.
896
+ #
839
897
  # </note>
840
898
  #
841
899
  #
@@ -873,6 +931,10 @@ module Aws::ECS
873
931
  # container instance, log in to your container instance and run the
874
932
  # following command: `sudo docker version | grep "Server API version"`
875
933
  #
934
+ # <note markdown="1"> This parameter is not supported for Windows containers.
935
+ #
936
+ # </note>
937
+ #
876
938
  #
877
939
  #
878
940
  # [1]: https://docs.docker.com/engine/reference/api/docker_remote_api_v1.27/#create-a-container
@@ -2116,8 +2178,8 @@ module Aws::ECS
2116
2178
  # container instance, the Docker daemon creates it. If the location
2117
2179
  # does exist, the contents of the source path folder are exported.
2118
2180
  #
2119
- # If you are using the Fargate launch type, the `host` parameter is
2120
- # not supported.
2181
+ # If you are using the Fargate launch type, the `sourcePath` parameter
2182
+ # is not supported.
2121
2183
  # @return [String]
2122
2184
  #
2123
2185
  # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/HostVolumeProperties AWS API Documentation
@@ -3027,8 +3089,7 @@ module Aws::ECS
3027
3089
  # }
3028
3090
  #
3029
3091
  # @!attribute [rw] source_volume
3030
- # The name of the volume to mount. If using the Fargate launch type,
3031
- # the `sourceVolume` parameter is not supported.
3092
+ # The name of the volume to mount.
3032
3093
  # @return [String]
3033
3094
  #
3034
3095
  # @!attribute [rw] container_path
@@ -3628,6 +3689,10 @@ module Aws::ECS
3628
3689
  # instantiations of the same task on a single container instance when
3629
3690
  # port mappings are used.
3630
3691
  #
3692
+ # Docker for Windows uses different network modes than Docker for
3693
+ # Linux. When you register a task definition with Windows containers,
3694
+ # you must not specify a network mode.
3695
+ #
3631
3696
  # For more information, see [Network settings][2] in the *Docker run
3632
3697
  # reference*.
3633
3698
  #
@@ -4673,6 +4738,17 @@ module Aws::ECS
4673
4738
  # The ARN of the IAM role that containers in this task can assume. All
4674
4739
  # containers in this task are granted the permissions that are
4675
4740
  # specified in this role.
4741
+ #
4742
+ # IAM roles for tasks on Windows require that the `-EnableTaskIAMRole`
4743
+ # option is set when you launch the Amazon ECS-optimized Windows AMI.
4744
+ # Your containers must also run some configuration code in order to
4745
+ # take advantage of the feature. For more information, see [Windows
4746
+ # IAM Roles for Tasks][1] in the *Amazon Elastic Container Service
4747
+ # Developer Guide*.
4748
+ #
4749
+ #
4750
+ #
4751
+ # [1]: http://docs.aws.amazon.com/AmazonECS/latest/developerguide/windows_task_IAM_roles.html
4676
4752
  # @return [String]
4677
4753
  #
4678
4754
  # @!attribute [rw] execution_role_arn
@@ -4705,10 +4781,22 @@ module Aws::ECS
4705
4781
  # more information, see [Task Networking][1] in the *Amazon Elastic
4706
4782
  # Container Service Developer Guide*.
4707
4783
  #
4784
+ # <note markdown="1"> Currently, only the Amazon ECS-optimized AMI, other Amazon Linux
4785
+ # variants with the `ecs-init` package, or AWS Fargate infrastructure
4786
+ # support the `awsvpc` network mode.
4787
+ #
4788
+ # </note>
4789
+ #
4708
4790
  # If the network mode is `host`, you can't run multiple
4709
4791
  # instantiations of the same task on a single container instance when
4710
4792
  # port mappings are used.
4711
4793
  #
4794
+ # Docker for Windows uses different network modes than Docker for
4795
+ # Linux. When you register a task definition with Windows containers,
4796
+ # you must not specify a network mode. If you use the console to
4797
+ # register a task definition with Windows containers, you must choose
4798
+ # the `<default>` network mode object.
4799
+ #
4712
4800
  # For more information, see [Network settings][2] in the *Docker run
4713
4801
  # reference*.
4714
4802
  #
@@ -5220,8 +5308,11 @@ module Aws::ECS
5220
5308
  # guaranteed to persist after the containers associated with it stop
5221
5309
  # running.
5222
5310
  #
5223
- # If you are using the Fargate launch type, the `host` parameter is
5224
- # not supported.
5311
+ # Windows containers can mount whole directories on the same drive as
5312
+ # `$env:ProgramData`. Windows containers cannot mount directories on a
5313
+ # different drive, and mount point cannot be across drives. For
5314
+ # example, you can mount `C:\my\path:C:\my\path` and `D:\:D:`, but
5315
+ # not `D:\my\path:C:\my\path` or `D:\:C:\my\path`.
5225
5316
  # @return [Types::HostVolumeProperties]
5226
5317
  #
5227
5318
  # @see http://docs.aws.amazon.com/goto/WebAPI/ecs-2014-11-13/Volume AWS API Documentation
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: aws-sdk-ecs
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.6.0
4
+ version: 1.7.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Amazon Web Services
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2017-12-04 00:00:00.000000000 Z
11
+ date: 2017-12-08 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: aws-sdk-core