-
❯ terraform init
There are some problems with the configuration, described below.
The Terraform configuration must be valid before initialization so that
Terraform can determine which modules and…
-
### Terraform Core Version
1.1-1.5
### AWS Provider Version
5.20.0
### Affected Resource(s)
aws_instance, aws_ebs_volume, aws_volume_attachment
### Expected Behavior
When added f…
-
Hello, as I see in code you're using ec2 describe-instances to filter running instances. But in my case my hybrid instances doesn't appear as ec2 instances but are still available for connection.
-
The EC2 driver maintains information about the instances it creates then uses that information to destroy the instance.
This isn't a problem (usually) when running molecule tests to completion. How…
-
### What happened?
An EC2 instance, a dedicated EBS Volume and VolumeAttachment to attach the Volume to the EC2 instance. As soon as the EC2 instance will be replaced because of userData change, a …
-
**Rancher Server Setup**
- Rancher version: 2.7
- Installation option (Docker install/Helm Chart): Helm
- If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): k3s 1.24.8
-…
-
### Description
**Context**
We run Karpenter in production for an O(15) node EKS cluster, using four (mutually exclusive) NodePools for different classes of application.
Our primary NodePool is…
-
### Describe the bug
When creating a new ec2 Instance in the CDK v2 with `requireImdsv2` as `true`:
```typescript
new ec2.Instance(this, 'Instance', {
// ... other required params
…
-
A user should be able to provide a pre-created SSH Key for an EC2 instance, with a fallback of Terraform handling it if you don't want to make your own.
-
User Story
As EKS user
I wanna enable IMDSv2 for my launch templates
so that my EC2 instance running without IMDSv1
Full backgrund can be seen here:
https://aws.amazon.com/blogs/security/get-th…