-
Notifications
You must be signed in to change notification settings - Fork 25
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
Next steps? IP address/connect to server questions #3
Comments
Hey there! Thanks for using the solution! So the code is actually pulling down https://github.com/lloesche/valheim-server-docker and running it using AWS ECS. Because we are using ECS Fargate - there is no actual "Instance" to manage. The solution assigns a public IP to the "task" (basically instructions and a template to run the valheim server docker image). You can see that by clicking on I will try to add some better documentation shortly that covers this. I will also look into capability for adding a Domain Name to the solution. |
Nice!! That's perfect. Got the IP 👍 Wonder if there's a way to get that programmatically with AWS cli and print to the console? |
@rossvz I did look into trying to add it as a CloudFormation stack output - but didn't have much luck. The CLI command option is an interesting idea. I will look into that - maybe the CDK has some sort of "post deploy" functionality? Otherwise we could add the CLI command to the readme (feel free to PR :) - otherwise I will try and get to it this weekend). Thanks again for opening this issue! |
Use named handler export rather than default export for lambdas
Hey there! I'm fairly inexperienced with AWS in general, but definitely haven't used ECS and CDK before!
I have ran the deployment script and I can see the container and stuff in ECS console. I think I'm missing a conceptual step - is this actually running the container and instance, or just creating the container image? Is there a manual step that needs to happen after the deploy?
If I go into ECS console -> Clusters I can see the Service and Task defined, but nothing under ECS Instances:
The text was updated successfully, but these errors were encountered: