-
Notifications
You must be signed in to change notification settings - Fork 11
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
Support AWS System Manager Session Manager #83
Labels
enhancement
New feature or request
Comments
This was referenced Dec 15, 2020
MatthiasScholz
pushed a commit
that referenced
this issue
Dec 17, 2020
MatthiasScholzTW
added a commit
that referenced
this issue
Dec 25, 2020
Open Points
|
MatthiasScholzTW
added a commit
that referenced
this issue
Jan 15, 2021
MatthiasScholzTW
added a commit
that referenced
this issue
Jan 17, 2021
Using AWS System Manager Session Manager instead of SSH access.
MatthiasScholzTW
added a commit
that referenced
this issue
Jan 17, 2021
MatthiasScholzTW
added a commit
that referenced
this issue
Jan 17, 2021
MatthiasScholzTW
added a commit
that referenced
this issue
Jan 17, 2021
MatthiasScholz
added a commit
that referenced
this issue
Jan 17, 2021
* 📌 version updates for all major components | #85 Covering the following dependencies: - nomad: 1.0.2 - consul: 1.9.1 - fabio - terraform modules - terraform-aws-consul module version 0.8.2 - packer definition - terraform: 0.14.4 * ♻️ Migrate from SSH to SSM and restructuring | #83 - Remove SSH dependency - Using AWS System Manager Session Manager instead of SSH access. * ✨ AMI testing during creation - Checking the AMI during the packer build step using goss. * ✨ restart nomad service on instance, solves #62 * 👷 added linting * 🐛 fixing aws provider version due to autoscaling issue An unsolved regression in the terraform-provider-aws ( hashicorp/terraform-provider-aws#14085 ) prevents the creation of autoscaling groups using terraform. * 💩 using fork to unblock waiting for PR | #85 Waiting for PR to be merge: hashicorp/terraform-aws-nomad#85 Co-authored-by: Matthias Scholz <[email protected]> Co-authored-by: Matthias Scholz <[email protected]>
Solved with PR #87. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Making use of the AWS Session Manager will allow to deprecate the bastion setup in order to debug cluster issues where direct instance access is needed.
Using the AWS Session Manager provides better security and less infrastructure to maintain and pay for.
Details
The text was updated successfully, but these errors were encountered: