 | NixOS AWS | 64 Members |
| 16 Servers |
| NixOS AWS | 64 Members |
| 16 Servers |
| Sender | Message | Time |
|---|---|---|
| 21 Oct 2024 | ||
 Arian | Oh i remember what happened here. | 07:12:01 |
| Arian | I think eu-west-2 was accidentally nuked by the infra team | 07:12:23 |
| Arian | * I think eu-west-1 was accidentally nuked by the infra team | 07:14:25 |
| Arian | But that ticket is super out of date. Since 24.05 everything should be available | 07:18:24 |
| Arian | https://github.com/NixOS/nixpkgs/issues/307519#issuecomment-2425821078 | 07:18:37 |
| Arian | How about we make networkd the new default networking backend for 24.11 as a first step to this? | 11:30:04 |
| Arian | I can send a PR for that | 11:30:16 |
 nh2 | In reply to @arianvp:matrix.orgI see. Note that the same is also the case for eu-central-1 now (when I think it wasn't before), just to make sure you know | 15:39:12 |
| Arian | As I said. That list is deprecated. Use https://nixos.github.io/amis instead | 16:26:20 |
| Arian | We can't use AWS for archival. They don't allow you to make public images available forever. They disappear after max period of a year | 16:26:45 |
| Arian | So use the docs linked to query the latest AMI. Anything else is unsupported | 16:27:01 |
| Arian | I also have no control over that old AWS account. I only have access to the new one. | 16:27:33 |
| Arian | * We can't use AWS for archival. They don't allow you to make public images available forever. They disappear after max period of a year | 16:27:41 |
| Arian | I only took over maintainace for 24.05 onwards. There aren't really any guarantees I can give over the old stuff. | 16:28:17 |
| Arian | Wouldn't be surprised all those images disappear at some point | 16:30:13 |
| Arian | Is there a particular reason why you need a 23.05 image instead of a supported image? | 16:33:08 |
| nh2 | Arian: I see. Yes, my reason is that I need to migrate some older 23.05 NixOps deployments to newer NixOS. I understand this isn't your or any NixOS contributor's fault, especially if AWS deletes public AMIs (no idea why they would do that, what is the point?). But it also means that the way NixOps is written is completely unsuitable, and I'm not sure a lot of NixOps authors, contributors, or users are aware of this. | 23:18:38 |
| 22 Oct 2024 | ||
| nh2 | Completely independent question: When I try to use NixOps to launch any newer AMI (it uses RunInstances), AWS errors with HTTP 400: I was puzzled by this, because I reproduced it AMIs for which this works/fails: Does anybody know what in the AMI could cause this? | 00:03:44 |
| Arian | I thought NixOps is unmaintained. I think they even removed the AWS plugin recently | 00:16:31 |
| Arian | Metadata options is part of the AMI. Sec | 00:16:47 |
| Arian | I wonder if it's related to this line: ImdsSupport="v2.0", | 00:17:47 |
| Arian | https://github.com/NixOS/amis/blob/main/upload-ami/src/upload_ami/upload_ami.py#L173 | 00:17:53 |
| Arian | Hmm actually I think maybe NixOps uses a very old version of the AWS SDK that is maybe incompatible with the AWS API? | 00:19:26 |
| Arian | Can you show me the raw curl command? | 00:19:43 |
| Arian | The only hit on google is this one stack overflow issue : https://stackoverflow.com/questions/76495875/cant-provision-ec2-instance-with-ansible | 00:23:03 |
| Arian | You're not on EC2 classic or something weird right? (The old VPC-less EC2) | 00:25:59 |
| Arian | So yeh because the AMI sets that option, i think that causes an implicit MetadataOptions to be passed. However IMDSv2 is new. So maybe you're using a very old SDK. The EC2 API is versioned (See the Version parameter in the curl request) | 00:36:06 |
| Arian | So maybe if you are trying to spawn an instance with IMDSv2 enabled using the older API version you get this error | 00:36:35 |
| Arian | Advice here is: update boto3 | 00:39:34 |
| Arian | * Advice here is: update boto3 dependency of nixops | 00:39:44 |