Skip to content
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

Switch GitLab to stock Amazon Linux 2 AMI #4188

Closed
6 tasks
hannes-ucsc opened this issue May 13, 2022 · 1 comment
Closed
6 tasks

Switch GitLab to stock Amazon Linux 2 AMI #4188

hannes-ucsc opened this issue May 13, 2022 · 1 comment
Assignees
Labels
compliance [subject] Information and software security demo [process] To be demonstrated at the end of the sprint demoed [process] Successfully demonstrated to team enh [type] New feature or request infra [subject] Project infrastructure like CI/CD, build and deployment scripts orange [process] Done by the Azul team ssp [process] Resolution is reflected in SSP

Comments

@hannes-ucsc
Copy link
Member

hannes-ucsc commented May 13, 2022

Data Browser System Overview - Logging   Monitoring(17)

In light of the demise of RancherOS and the fact that compliance auditors will likely balk at our usage of rather obscure 3rd party image, we should switch to the Amazon Linux 2 AMI. It already contains the SSM agent allowing the instance to be scanned by Amazon Inspector. On Amazon Linux 2, the CloudWatch agent can be installed via yum. It will send the system logs to CloudWatch (#3894).

Configure cloud-init (which is pre-installed in the AMI) via instance user data to:

  • install Docker
  • start Docker
  • write a crontab that launches the clamav and freshclam containers
  • start the GitLab DinD container
  • start the GitLab container
  • start the GitLab runner container
@hannes-ucsc hannes-ucsc added the orange [process] Done by the Azul team label May 13, 2022
@melainalegaspi melainalegaspi added enh [type] New feature or request infra [subject] Project infrastructure like CI/CD, build and deployment scripts compliance [subject] Information and software security labels May 13, 2022
@hannes-ucsc
Copy link
Member Author

For demo, show that dev or prod instance is on the new AMI hard-coded in the TF config. Mention integration with systemd, show conversion of YAML userdata to JSON, show jl, jw and qq primitives.

@hannes-ucsc hannes-ucsc added the demo [process] To be demonstrated at the end of the sprint label Sep 14, 2022
achave11-ucsc pushed a commit that referenced this issue Sep 20, 2022
Only .shared & .gitlab were deployed. The .gitlab component was subsequently
destroyed again. The main purpose was to have a GitLab instance to test the
changes for #4188 on.
@hannes-ucsc hannes-ucsc added the demoed [process] Successfully demonstrated to team label Sep 20, 2022
@hannes-ucsc hannes-ucsc added the ssp [process] Resolution is reflected in SSP label Jul 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compliance [subject] Information and software security demo [process] To be demonstrated at the end of the sprint demoed [process] Successfully demonstrated to team enh [type] New feature or request infra [subject] Project infrastructure like CI/CD, build and deployment scripts orange [process] Done by the Azul team ssp [process] Resolution is reflected in SSP
Projects
None yet
Development

No branches or pull requests

2 participants