| 14 Sep 2024 |
commiterate | it doesn't help that basically the only part of Amazon that uses Go on the regular is Twitch | 08:23:28 |
Arian | Yeh it seems to be a recurring theme. Cloud watch agent can't log journal logs and doesn't work out of the box on Amazon Linux 2023 etc. | 08:23:45 |
commiterate | not that the codebases in the other languages are much better, but that's par for the course at most companies | 08:23:51 |
Arian | But I just use big hammer until it works | 08:24:38 |
commiterate | is the main thing we need EIC and Image Builder expanding ImportVmImage + distribution-only image pipelines?
I have those 2 as the highest priority requests right now. Instance Refresh from Cfn is slightly lower in priority for my use case specifically.
I can push all 3 though since they're all owned by different divisions. | 08:26:31 |
Arian | I'm not very interested in the image builder stuff unless I can make a pipeline that just does CopySnapshot + RegisterImage | 08:28:02 |
Arian | Because then I can use it for GC | 08:28:07 |
commiterate | yeah that's what I'm trying to get them to do | 08:28:14 |
commiterate | since Image Builder is the only sane AMI lifecycle management option | 08:28:20 |
commiterate | * since Image Builder is the only sane AMI distribution + lifecycle management option | 08:28:32 |
Arian | The other option is to just write some DescribeSnapshot glue | 08:28:42 |
commiterate | eh, it feels like everything else has to add a lot of extra complexity to clean up orphaned resources | 08:29:17 |
Arian | But idk if they're super interested in adding it. Bottle rocket is also just using their own scripts (very similar to ours) and they're an Amazon team | 08:29:50 |
Arian | But they don't have any incentive for cleaning up images I think :') | 08:30:10 |
commiterate | Image Builder is kind of lower priority for them because internally they don't use any of the native services to build AMIs | 08:30:18 |
Arian | Bottlerocket actually uses EBS direct API which I experimented adding too | 08:31:10 |
commiterate | they've also decided against dogfooding certain public services and start prioritizing internal ones again because some internal requirements aren't externalizable | 08:31:12 |
Arian | But turns out to be slower because GitHub actions heavily throttles it for some reason | 08:31:28 |
commiterate | that shift started happening I think 1.5-2 years ago | 08:31:33 |
Arian | Like. Uploads taking 2 days... | 08:32:01 |
Arian | Instead of 1 minute | 08:32:05 |
Arian | Still haven't figured out what is happening there | 08:32:19 |
Arian | But I expect some whitelist at GitHub side that only allows high bandwidth traffic to S3 and EC2 | 08:32:45 |
Arian | Worked fine on self-hosted EC2 runners | 08:32:58 |
| 16 Sep 2024 |
| silentlurker joined the room. | 19:57:05 |
| 19 Sep 2024 |
commiterate | Image Builder PM said distribution-only pipelines are possible today. You just abuse image workflows which can be empty and avoid EC2 instance launch unlike image recipes (the pipeline requires either a workflow or recipe).
They aren't currently considering VM import from S3 or EBS via CloudFormation and need more customer requests to consider it. Trying to see if I can change that stance.
| 18:18:39 |
| 20 Sep 2024 |
commiterate | * Image Builder PM said distribution-only pipelines are possible today. You just abuse image workflows which can be empty and avoid EC2 instance launch unlike image recipes (the pipeline requires either a workflow or recipe). Also seems to only use SSM Agent and no AWSTOE if you do need to run build or test commands.
They aren't currently considering VM import from S3 or EBS via CloudFormation and need more customer requests to consider it. Trying to see if I can change that stance.
| 04:56:27 |
Arian | Interesting. I tried to wiggle myself through the docs and couldn't figure out how last time | 08:04:11 |
Arian | Would that mean id have to create a workflow for each image that I upload? | 08:05:04 |
Arian | Ugh AWS docs are so terribly inscrutable sometimes | 08:08:36 |