Skip to content
This repository was archived by the owner on Nov 19, 2025. It is now read-only.

Conversation

@PettitWesley
Copy link
Contributor

@PettitWesley PettitWesley commented May 9, 2019

The V1 Path format will eventually be deprecated: https://forums.aws.amazon.com/ann.jspa?annID=6776

Testing

  • [N/A ] Unit tests passed
  • [N/A ] Integration tests passed
  • [N/A ] Unit tests added for new functionality
  • [N/A ] Listed manual checks and their outputs in the comments (example)
  • [N/A ] Link to issue or PR for the integration tests:

Documentation

  • [ √] Contacted our doc writer
  • [ √] Updated our README

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

* If you are using Docker compose version 3, the `cpu_shares`, `mem_limit`, and `mem_reservation` fields are optional and must be specified in the ECS params file rather than the compose file.
* In Docker compose version 2, the `cpu_shares`, `mem_limit`, and `mem_reservation` fields can be specified in either the compose or ECS params file. If they are specified in the ECS params file, the values will override values present in the compose file.
* If you are using a private repository for pulling images, `repository_credentials` allows you to specify an AWS Secrets Manager secret ARN for the name of the secret containing your private repository credentials as a `credential_parameter`.
* `init_process_enabled` is a [Linux-specific option](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_LinuxParameters.html) that can be be set to run an init process inside the container that forwards signals and reaps processes. This parameter maps to the `--init` option to [docker run](https://docs.docker.com/engine/reference/run/). This parameter requires version 1.25 of the Docker Remote API or greater on your container instance.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My editor (Atom) seems to have automatically removed the spaces at the end of these lines

@PettitWesley
Copy link
Contributor Author

Only tested a few... but all should work...

wget https://amazon-ecs-cli.s3.amazonaws.com/ecs-cli-linux-amd64-latest
--2019-05-08 19:59:42--  https://amazon-ecs-cli.s3.amazonaws.com/ecs-cli-linux-amd64-latest
Resolving amazon-ecs-cli.s3.amazonaws.com... 52.216.112.203
Connecting to amazon-ecs-cli.s3.amazonaws.com|52.216.112.203|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 29793728 (28M) [binary/octet-stream]
Saving to: ‘ecs-cli-linux-amd64-latest.2’

ecs-cli-linux-amd64-latest.2                  100%[==============================================================================================>]  28.41M  5.69MB/s    in 6.5s

2019-05-08 19:59:49 (4.39 MB/s) - ‘ecs-cli-linux-amd64-latest.2’ saved [29793728/29793728]

Copy link
Contributor

@efekarakus efekarakus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@PettitWesley PettitWesley merged commit d04587e into aws:dev May 9, 2019
@PettitWesley PettitWesley deleted the s3-v2-path branch May 9, 2019 19:45
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants