module.networking.module.bastion.aws_autoscaling_group.bastion: aws_autoscaling_group.bastion: diffs didn't match during apply. This is a bug with Terraform and should be reported as a GitHub Issue.

[ghost]

This issue was originally opened by @cmattoon as hashicorp/terraform#17230. It was migrated here as a result of the provider split. The original body of the issue is below.

---

My goal here is to create two autoscaling groups (among all of the other networking, security, etc)

1. An etcd autoscale group provisioned via aws_cloudformation_stack
2. An autoscale group (n=1) provisioned with Terraform. The error appears to be happening here.

I'm currently developing this set of files, so it very well may be user error. The CloudFormation stack failure is likely a separate issue I'm debugging (networking/security-related). I seem to get this error off-and-on, so I'm adding some initial details here.

It looks like the diff points here:
aws_autoscaling_group.bastion.availability_zones = "${split(",", var.azs)}"

Where "${var.azs}" == "us-west-2a,us-west-2b,us-west-2c"

https://gist.github.com/cmattoon/5b339d6616006ef5591a05e5645062a5

[bflad]

This issue was automatically closed by the documentation update in #3897. The configuration fix for diffs didn't match during apply and Mismatch reason: attribute mismatch: availability_zones.XXXXXX is to remove availability_zones configuration if vpc_zone_identifier is also specified. If you must specify availability_zones due to being used in a module that works with both EC2-Classic and VPC, availability_zones can be set to [] (an empty list).

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!