You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
STACKIT Provider : Failing to create MongoDB Flex Instance #1772
We are using STACKIT Terraform provider version 0.115.0.
When we run terraform apply to create the mongodb flex instance we simply get 404 error with the message Calling API: 404 Not Found, status code 404, Body: {"message":"mongodb not │ found","code":404,"type":"NotFound"}
We also tried with version 0.114.0 and we received the same error message as above.
Steps to reproduce
Simply declare the MongoDB Flex instance in the terrafor code to create a new MongoFlex instance.
resource"stackit_mongodbflex_instance""example" {
project_id="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"name="example-instance"acl=["0.0.0.0/0"]
flavor={
cpu =1
ram =4
}
replicas=1storage={
class ="premium-perf2-mongodb"
size =10
}
version="7.0"options={
type ="Single"
snapshot_retention_days =3
point_in_time_window_hours =30
}
backup_schedule="0 0 * * *"
}
Run terraform apply
It produces the issue.
with stackit_mongodbflex_instance.mongodb-cluster (mongodb-cluster),
│ on cdk.tf.json line 132, in resource.stackit_mongodbflex_instance.mongodb-cluster (mongodb-cluster):
│ 132: }
│
│ Calling API: 404 Not Found, status code 404, Body: {"message":"mongodb not
│ found","code":404,"type":"NotFound"}
│
│
│ Trace ID: "8eb72ba607dc14ea50e36e259d23936c"
Actual behavior
The STACKIT API is returning 404 even for the API calls.
Expected behaviour
The stack creation should simply succeed with creation of MongoDB flex instance.
Environment
OS: MacOS/Linux
Terraform version (see terraform --version): v1.15.2
Version of the STACKIT Terraform provider: v0.115.0 & v.114.0 as well
Activity
saurabh2590 commentedon Sep 18, 2026
Please also see audit log entry. Maybe it has a hint that an old route is being called.
saurabh2590 commentedon Sep 18, 2026
It seems that the bug is not in the terraform provider but more at the API level as we can reproduce the bug also on the portal.
Manuelvaas commentedon Sep 23, 2026
Hi @saurabh2590,
Thank you for reporting this issue; we will take a look at it.
Best Regards,
Manuel