Giter VIP home page Giter VIP logo

Comments (5)

uttarasridhar avatar uttarasridhar commented on July 17, 2024

You don’t have to copy the credentials manually. We persist the profile name in ~/.ecs/config with the key as aws_profile. We use that while calling the AWS SDK (which fetches the credentials from the profile at that time). Please let us know if you have any other questions.

from amazon-ecs-cli.

MrAtheist avatar MrAtheist commented on July 17, 2024

Fair enough. But apparently you need those set in config when trying to up a cluster.

$> ecs-cli up --keypair ~/.ssh/id_rsa --capability-iam --size 2 --instance-type t2.medium

ERRO[0000] Error executing 'up': Set a region with the --region flag or AWS_REGION environment variable

With everything set in config, I got another error:

INFO[0000] Created cluster                               cluster=cluster
INFO[0001] Waiting for your cluster resources to be created 
INFO[0001] Cloudformation stack status                   stackStatus=CREATE_IN_PROGRESS
ERRO[0031] Failure event                                 reason= resourceType=AWS::CloudFormation::Stack
ERRO[0031] Error executing 'up': Cloudformation failure waiting for 'CREATE_COMPLETE'. State is 'ROLLBACK_COMPLETE'

Not sure where to go from there...

from amazon-ecs-cli.

uttarasridhar avatar uttarasridhar commented on July 17, 2024

Ah! AWS region doesn't get copied from aws cli profile.
As for the error message, I have a pull request that will show a more descriptive reason for failure.

For now, you can go to the Cloudformation console and look for the stack with name amazon-ecs-cli-setup- and look for an error message there. Apologies for the inconvenience.

from amazon-ecs-cli.

dtest avatar dtest commented on July 17, 2024

Ran into this today. Could the region be copied from the profile on ecs configure?

from amazon-ecs-cli.

iwootten avatar iwootten commented on July 17, 2024

Hmm I got the same issue as @MrAtheist - the error being that the tutorial in the docs here: http://docs.aws.amazon.com/AmazonECS/latest/developerguide/ECS_CLI_tutorial.html misses out where to get the 'keypair' parameter from (it's definitely not id_rsa as in the example).

After following these steps: http://docs.aws.amazon.com/AmazonECS/latest/developerguide/get-set-up-for-amazon-ecs.html#create-an-iam-role, I've created mine - but be aware you connect using the name of the pair you generate, not the .pem file you download (you'll use that to connect to instances).

from amazon-ecs-cli.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.