-
Notifications
You must be signed in to change notification settings - Fork 36
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
Clarification on Manager Image #6
Comments
Hi @mikesiconolfi ! Thanks for your interest in this project. No, the AMI should be an Amazon Linux image. I'm currently using You may obtain an AMI ID for this stack using the AWS CLI: export AWS_DEFAULT_REGION='<your-AWS-region>'
aws ec2 describe-images \
--owners amazon \
--filters 'Name=name,Values=amzn2-ami-hvm-*-gp2' \
'Name=image-type,Values=machine' \
'Name=virtualization-type,Values=hvm' \
'Name=architecture,Values=x86_64' \
--query 'reverse(sort_by(Images, &CreationDate))[0].ImageId' \
--output text |
In order to make this step easier for newcomers to this template, it would be great to have a default ami populated in the template based on the region its deployed in. |
PR #11 removes the CloudFormation parameter, so that we're no longer required to pass an AMI ID, that might not be easy to find. Instead, AMI IDs are now retrieved with |
Looks like this has never been merged |
Im trying to deploy your aws template but not sure what i need to do for the Manager Image ID? Do i need to create my own server with docker and gitlab-runner installed on it first?
The text was updated successfully, but these errors were encountered: