-
Currently it appears the module supports only a single subnet ID. This means if you're using spot instances in an ASG, you can get denied provisioning an instance due to limited capacity in that speci…
-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help…
-
### Describe the bug
I am trying to use the ASG module.
The invocation of the module is as follows:
module "paloalto" {
source = "../../../terraform-aws-swfw-modules/modules/asg"
ssh_ke…
-
### What happened?
**Context**
- Python Pulumi project
- Creates VPC + EKS using Crosswalk
- Creates Managed Node Groups w/ Launch Templates
The motivation here is to set capacity reservations in t…
-
### Terraform Core Version
v1.3.9
### AWS Provider Version
5.73.0
### Affected Resource(s)
```
resource "aws_redshift_cluster" "redshift_cluster" {
cluster_identifier = "redshif…
-
### Terraform Core Version
1.9.2
### AWS Provider Version
5.74.0
### Affected Resource(s)
aws_medialive_input
aws_medialive_channel
### Expected Behavior
AWS Medialive Channel cr…
-
### Terraform Core Version
1.8.1
### AWS Provider Version
5.51.1
### Affected Resource(s)
aws_fsx_lustre_file_system has a variable named 'Subnet_ids' which should be a list of string.
…
-
## Description
I'm using terraform-aws-modules/eks/aws//modules/eks-managed-node-group directly.
During planning, a delete & recreation of the policy attachments for the node group is being plan…
-
## Describe the bug
The bug manifests on our cluster created with the following networking parameters:
```shell
az aks show --subscription ExampleSubscription -n example-cluster-name -g example-clust…
-
I'm seeing a behavior in aws_mwaa_environment that I was not seeing previously. With hashicorp/aws v4.64.0, every time I deploy, it destroys and recreates the aws_mwaa_environment with this message s…