bug: terraform aws_acm_certificate data source runs indefinitely

[tiagoposse]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When attempting to retrieve an ACM certificate using the terraform data source "aws_acm_certificate", the certificate is never read and the call runs indefinitely until cancelled.

Expected Behavior

The certificate is retrieved and the terraform plan executes.

How are you starting LocalStack?

With a docker run command

Steps To Reproduce

How are you starting localstack (e.g., bin/localstack command, arguments, or docker-compose.yml)

docker run localstack/localstack-pro:2.0.1 ...

Terraform code

The following terraform module is sufficient to reproduce this issue:

resource "aws_route53_zone" "this" {
  name = "example.com"
}

module "acm" {
  source  = "terraform-aws-modules/acm/aws"
  version = "4.3.2"

  domain_name         = "*.example.com"
  wait_for_validation = true
  zone_id             = aws_route53_zone.this.zone_id
}

data "aws_acm_certificate" "this" {
  depends_on = [module.acm]

  domain = "*.example.com"
}

Environment

- Docker
- LocalStack: 2.0.1

Anything else?

terraform_exec.txt
localstack_log.txt

[localstack-bot]

Welcome to LocalStack! Thanks for reporting your first issue and our team will be working towards fixing the issue for you or reach out for more background information. We recommend joining our Slack Community for real-time help and drop a message to LocalStack Pro Support if you are a Pro user! If you are willing to contribute towards fixing this issue, please have a look at our contributing guidelines and our contributing guide.

[whummer]

Thanks for reporting @tiagoposse . We have now pushed a few enhancements in #8162 which should fix the Terraform deployment of ACM certificates. Can you please pull the latest Docker image and give it another try? Please keep us posted on how it goes.. Thanks!

[tiagoposse]

Unfortunately the "latest" image returns

LocalStack supervisor: localstack process (PID 16) returned with exit code -11
LocalStack supervisor: exiting

when running this example

[whummer]

Thanks for the update @tiagoposse . Exit code -11 usually means "segmentation fault", which indicates a fatal error in the execution, usually caused by an invalid memory access.

This type of error is usually quite specific to the environment you're running in (operating system, CPU architecture, Docker version, etc). Can you please share a few more details about your environment?

Also, are you seeing any more details in the logs, perhaps with DEBUG=1 or LS_LOG=trace (for detailed trace logging) enabled - can you please share the logs with these configs enabled? Thanks for your help in resolving this.

[tiagoposse]

Not sure if it's the same error currently (pulled new latest and error code looks different), but facing an error still.

I'm running in docker, in an M1 macbook with Monterey 12.4.

Client: Docker Engine - Community
 Version:           20.10.20
 API version:       1.41
 Go version:        go1.19.2
 Git commit:        9fdeb9c3de
 Built:             Tue Oct 18 17:43:24 2022
 OS/Arch:           darwin/arm64
 Context:           orbstack
 Experimental:      true

Server:
 Engine:
  Version:          23.0.5
  API version:      1.42 (minimum version 1.12)
  Go version:       go1.20.3
  Git commit:       94d3ad69cc598b5a8eb8a643d6999375953512e8
  Built:            Sun Apr 30 20:03:42 2023
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          v1.7.0
  GitCommit:        1fbd70374134b891f97ce19c70b6e50c7b9f4e0d
 runc:
  Version:          1.1.7
  GitCommit:        860f061b76bb4fc671f0f9e900f7d80ff93d4eb7
 docker-init:
  Version:          0.19.0
  GitCommit:

env config:

DEFAULT_REGION=eu-central-1
HOSTNAME_EXTERNAL=localhost.localstack.cloud
DOCKER_HOST=unix:///var/run/docker.sock
HOST_TMP_FOLDER=/tmp/localstack
PERSISTENCE=1
DEBUG=1
LS_LOG=trace
ENFORCE_IAM=0

Logs attached
log.txt

[tiagoposse]

for anyone interested, the error I faced was related to persistence. Deleting the local volume and re-starting localstack fixed it