How do we configure a dedicated GitLab CI runner on an AWS EC2 instance securely so external jobs cannot compromise our build environment?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
How do we configure a dedicated GitLab CI runner on an AWS EC2 instance securely so external jobs cannot compromise our build environment?
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 2 queries…
Searches and sources
ChatGPT2 real searches · gpt-6
site:docs.gitlab.com runner security Docker executor privileged mode protected runners untrusted jobs Google ↗
site:docs.aws.amazon.com EC2 security best practices IMDSv2 Systems Manager private subnet security groups Google ↗
- GitLab Runner installation documentation · docs.gitlab.com
- Security for self-managed runners · docs.gitlab.com
- Docker executor · docs.gitlab.com
- GitLab Runner autoscaling on AWS EC2 · docs.gitlab.com
- GitLab runner configuration · docs.gitlab.com
- Use Docker-in-Docker · docs.gitlab.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
site:docs.gitlab.com runner security Docker executor privileged mode protected runners untrusted jobs OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
site:docs.aws.amazon.com EC2 security best practices IMDSv2 Systems Manager private subnet security groups OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |