ecs-deploy | continuous deployment platform for AWS ECS | Continuous Deployment library

 by   in4it Go Version: 0.0.37 License: Apache-2.0

kandi X-RAY | ecs-deploy Summary

kandi X-RAY | ecs-deploy Summary

ecs-deploy is a Go library typically used in Devops, Continuous Deployment, Docker applications. ecs-deploy has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

ECS Deploy is a REST API server written in Go that can be used to deploy services on ECS from anywhere. It typically is executed as part of your deployment pipeline. Continuous Integration software (like Jenkins, CircleCI, Bitbucket or others) often don't have proper integration with ECS. This API server can be deployed on ECS and will be used to provide continuous deployment on ECS.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              ecs-deploy has a low active ecosystem.
              It has 258 star(s) with 124 fork(s). There are 12 watchers for this library.
              OutlinedDot
              It had no major release in the last 12 months.
              There are 0 open issues and 5 have been closed. On average issues are closed in 61 days. There are 5 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of ecs-deploy is 0.0.37

            kandi-Quality Quality

              ecs-deploy has no bugs reported.

            kandi-Security Security

              ecs-deploy has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

            kandi-License License

              ecs-deploy is licensed under the Apache-2.0 License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              ecs-deploy releases are available to install and integrate.
              Installation instructions, examples and code snippets are available.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of ecs-deploy
            Get all kandi verified functions for this library.

            ecs-deploy Key Features

            No Key Features are available at this moment for ecs-deploy.

            ecs-deploy Examples and Code Snippets

            No Code Snippets are available at this moment for ecs-deploy.

            Community Discussions

            QUESTION

            How to use CodeDeploy with ECS, ALB and Auto Scaling
            Asked 2021-Feb-18 at 19:35

            I'm trying to use CodeDeploy and ECS with an Application Load Balancer, and Auto Scaling with a strategy on the number of request of this ALB.

            I'm using this URL as some sort of tutorial, but i don't really understand how CodeDeploy will integrate with ECS and other stuffs.

            First, as i can see, i need two target groups on my ALB. But i only have one (that is, instance(s) that are / will be created by Auto Scaling)

            So what do i need to do ? Does creating an empty target group, and telling CodeDeploy to use both work ?

            What will it do, deploy instances in this target group and redirect a part of or the whole trafic to it once working ? As stated in the same link

            "During deployment, CodeDeploy installs your update into a new, replacement task set."

            So it seems to create new tasks, but on what instance then ?

            ...

            ANSWER

            Answered 2021-Feb-08 at 01:27

            So what do i need to do ? Does creating an empty target group, and telling CodeDeploy to use both work ?

            It can't be empty. Your new TG can be same as your first one. So at this stage you will have to TGs which are same (except thier name).

            The second TG is specified when you create your ECS deployment group in CodeDeploy.

            What will it do, deploy instances in this target group and redirect a part of or the whole traffic to it once working ? As stated in the same link

            These will be same instances as the one running your current ecs task.

            So it seems to create new tasks, but on what instance then ?

            These will be same instances as those that run your current task.

            Source https://stackoverflow.com/questions/66090487

            QUESTION

            Why ECS pipeline needed Task Definition while Service already have the task definition assigned in AWS?
            Asked 2020-Sep-13 at 21:54

            on bitbucket, the config is required to use both 'service' and 'task definition', I think this is redundant because the service already assigned with task definition, or we have an explanation?

            ...

            ANSWER

            Answered 2020-Sep-13 at 21:54

            The task definition in ECS service you are showing is probably the initial deployment. When you do subsequent deployments you update the task definition with new image version, or extra parameters. You can't update ECS task without providing task definition.

            The task definition is thus required. It's same if you use CodeDeploy to deploy to ECS - task definition must be provided:

            -AppSpec 'resources' section for Amazon ECS deployments

            TaskDefinition – Required. This is the task definition for the Amazon ECS service to deploy.

            Source https://stackoverflow.com/questions/63874941

            QUESTION

            How to use previous task definition with ECS and bitbucket pipeline deployment
            Asked 2020-May-19 at 05:04

            I'm following this doc https://confluence.atlassian.com/bitbucket/deploy-to-amazon-ecs-892623902.html to set up a pipeline to deploy to the ECS cluster.

            This doc is using a custom task def JSON file and using the same for the deployment after updating the image name.

            Am I required to copy the complete task definition JSON and put that in my repository? My task definition has lots of environment variables in it. I do not want to expose them by putting it in the repository.

            Or, the task definition template will update the default task definition and create a new revision. (not overwrite)

            The deployment step is

            ...

            ANSWER

            Answered 2020-May-18 at 22:01

            You can use aws cli to run this command and retrieve the existing task definition JSON: https://docs.aws.amazon.com/cli/latest/reference/ecs/describe-task-definition.html

            Source https://stackoverflow.com/questions/61870907

            QUESTION

            Jenkins ecs Command not found
            Asked 2020-Feb-06 at 19:00

            I installed third party tool (ecs deploy using pip install ecs-deploy) .When I try to deploy using command ecs deploy demo-cluster demo-service in command prompt its working fine when I try with jenkins to deploy getting error

            ...

            ANSWER

            Answered 2020-Feb-05 at 12:24

            QUESTION

            Cross-Account ECS Deployment
            Asked 2019-Sep-26 at 14:21

            I am trying to deploy an image from ECR of one account (AccountA) to ECS Cluster of another (AccountB) using CodePipeline. I am getting a permissions related error in the deploy phase.

            Here is my pipeline role in AccountA:

            ...

            ANSWER

            Answered 2019-Sep-26 at 14:21

            Lets assume:

            Account_A => CodePipeline & Source
            Account_B => ECS

            Here is what is required:

            Account_A:
            * AWSCodePipelineServiceRole
            * Artifact_Store_S3_Bucket
            * KMS_Key_for_Pipeline_Artifact (Customer Managed Key)
            * Bucket Policy on Artifact_Store_S3_Bucket to Allow Account_B access
            * Key Policy on KMS_Key_for_Pipeline_Artifact to Allow Access to Cross_Account_Role (from Account_B)

            Account_B
            * Cross_Account_Role (Trust relationship with Account_A and Full_ECS permissions)
            * ECS with a running that is to be replaced with deployment

            imagedefinitions.json (must be part of your source code)

            Source https://stackoverflow.com/questions/58088134

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install ecs-deploy

            You can download ecs-deploy and ecs-client from the releases page or you can use the image from dockerhub.
            Create an SNS topic, add https subscriber with URL https://your-domain.com/ecs-deploy/webhook
            Create a CloudWatch Event for ECS tasks/services
            Create an EC2 Auto Scaling Lifecycle hook, and a CloudWatch event to capture the Lifecycle hook
            Let the SNS topic be the trigger for the CloudWatch events

            Support

            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/in4it/ecs-deploy.git

          • CLI

            gh repo clone in4it/ecs-deploy

          • sshUrl

            git@github.com:in4it/ecs-deploy.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link