gkirok/AWS SSM EKS Action
Connects to eks with private endpoint using ssm session on bastion server
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Oct 18, 2022
- License
- GPL 3.0
Pinned Snippet
uses: gkirok/aws-ssm-eks@9c037ac58f2ac4ddfdc5d13333e98b0ff4f2e54d # v2tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| AWS_ACCESS_KEY_ID | Your AWS_ACCESS_KEY_ID | no | — |
| AWS_SECRET_ACCESS_KEY | Your AWS_SECRET_ACCESS_KEY | no | — |
| AWS_REGION | The region of the cluster | no | — |
| CLUSTER_NAME | The name of the cluster you're using | yes | — |
| BASTION_NAME | The name of the bastion server you're using | no | — |
| BASTION_ID | The instance id of the bastion server you're using | no | — |
| SSM_PORT | The local port used by ssm session manager | no | — |
| kubectl_cmd | The arguments that you want to pass through to the kubectl command | yes | — |
Outputs
| name | description |
|---|---|
| cmd-out | The output of the aws ssm command |