Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is it possible to finish this tutorial with the required instructions at the end for ecs deployment? #8

Open
helloravi opened this issue Apr 6, 2017 · 10 comments

Comments

@helloravi
Copy link

No description provided.

@so0k
Copy link
Owner

so0k commented Apr 16, 2017

Hi @helloravi - sorry for slow response. I think the ECS deployment part isn't complete as I haven't continued working on this. Sorry for the confusion

@helloravi
Copy link
Author

Thank you for replying. Whatever you wrote so far was quite helpful. If you can get around to finish the ecs part it would be great.

@so0k
Copy link
Owner

so0k commented Apr 16, 2017

it's not a bad idea, I'd re-organise it slightly though as some Dockerfiles are mixed with golang code (messy)

I'd also move all the manual steps to Terraform like in this repository (sets up ECS infra for similar s3 based app): https://github.com/so0k/exercise-infra

@helloravi
Copy link
Author

Thank you very much. I have never used Terraform. Just looking into it. Do you know a resource which shows how to set up a ECS cluster using CLI?

@so0k
Copy link
Owner

so0k commented Apr 17, 2017

the repo I linked above does exactly that:
https://github.com/so0k/exercise-infra/blob/master/README.md#getting-started

you run terraform plan and it'll give you a full overview of the VPC / Subnets / Security Groups / IAM Roles / Auto Scaling Groups / Load Balancers / ... everything required to provision a full ECS cluster

@so0k
Copy link
Owner

so0k commented Apr 17, 2017

not only that, if you need to modify something, you can change the code, run another plan to verify the changes you made will be applied as expected, then you can apply the new changes effectively managing your full infrastructure as code - not just fire it off once to create it, but continuously improve it and giving you an easy way to re-create everything from scratch if it were ever required

@helloravi
Copy link
Author

Vincent,
I have never even set up a basic cluster using ECS CLI. I have only started with ECS recently. I set up a dummy cluster using the GUI on web.

I wanted to set up one using the basic ECS CLI so that I get familiar with ECS CLI set up. I want to move on to Terraform once I do that. What do you advice?

I am looking at using something like https://github.com/remind101/empire later once I am familiar enough with ECS. Do you have any advice on this?

Once again, your demo tutorial was very helpful :)

@so0k
Copy link
Owner

so0k commented Apr 17, 2017

https://github.com/aws/amazon-ecs-cli should be the first stop I guess, apart from that there's Convox and Blox.

I prefer kubernetes as this gives you cloud provider independency, but I suggest you start with ecs-cli

@helloravi
Copy link
Author

Waav. You are super helpful.

I was doing this tutorial
http://docs.aws.amazon.com/AmazonECS/latest/developerguide/ECS_CLI_tutorial.html

I was having trouble with
ecs-cli up --keypair id_rsa --capability-iam --size 2 --instance-type t2.medium
And when I was searching for this I came across your demo app.

I have some key pair issue :) I made sure the pem is from the same region as suggested in some comments but still going no where with it.

Where are you from?
Also, interesting username so+0k?

@helloravi
Copy link
Author

Thanks got this resolved!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants