#terraform-aws-modules (2021-03)
Terraform Modules
Discussions related to https://github.com/terraform-aws-modules
Archive: https://archive.sweetops.com/terraform-aws-modules/
2021-03-01
I given access and facing this below issue any idea please let me know
Error: Error fetching Availability Zones: UnauthorizedOperation: You are not authorized to perform this operation. status code: 403, request id: 5a71c76f-205a-495e-95a9-11a1b212104d
The AWS credentials you are using don’t have the right permissions
yes now I am able to perform operations and thank you :)
2021-03-04
Error: InvalidGroup.NotFound: The security group ‘sg-0400485cb9a0fd264’ does not exist status code: 400, request id: d835e39c-64ba-439a-99b1-510dea8fda73
2021-03-05
hi guys, anyone knows how to create “trusted advisor” in terraform?
2021-03-06
hi guys,
I create d the kafka cluster with three brokers and not able to create the topics through terraform script, facing the below issue.
[1m[31mError: [0m[0m[1mkafka: client has run out of available brokers to talk to (Is your cluster reachable?)[0m
[0m on main.tf line 45, in resource "kafka_acl" "mytfkafkatopic_acl":
45: resource "kafka_acl" "mytfkafkatopic_acl" [4m{[0m
[0m
[0m[0m
[31m
[1m[31mError: [0m[0m[1mkafka: client has run out of available brokers to talk to (Is your cluster reachable?)[0m
[0m on main.tf line 45, in resource "kafka_acl" "mytfkafkatopic_acl":
45: resource "kafka_acl" "mytfkafkatopic_acl" [4m{[0m
Sounds like you’re not on the same network as the kafka cluster
you cannot do this from your workstation unless your workstation has access to the VPC
2021-03-09
2021-03-17
what is stream_names referring to here https://github.com/cloudposse/terraform-aws-cloudwatch-logs
2021-03-22
Hello,
We have a terraform RDS module that uses random_string to generate and set the password. Something similar to https://gist.github.com/smiller171/6be734957e30c5d4e4b15422634f13f4. We updated a field in the cluster parameter group and found that the RDS password was re-generated. However the RDS instances still have the old password set and the new password just doesn’t work even though it has been updated in the secrets manager and TF output etc. Can someone shed some light onto how TF manages RDS passwords? Thanks in advance !!
Hmm that’s odd that the password would be regenerated when updating your cluster parameter group. Seems unexpected
I’m surprised rerunning your terraform doesn’t cause differences in the plan
The original password should be in your tfstate, terraform should spot the difference in ssm and on your rds instance, and allow you to apply the original values to both rds and ssm
is this going to be enabled again soon? Anything we can do right now to enable bucket logging? https://github.com/cloudposse/terraform-aws-tfstate-backend/blob/793d3f90c25d9f17f4a299be7b13ae5141795345/main.tf#L106
This comment is only related to bridgecrew static analysis for security scanning.
It has nothing to do with the functionality of the module