I tried out the creation of EC2 Instances using aws_launch_template{} and aws_instance{} resources , but after doing that, the detailed monitoring does not activate and for some reason I get such result:

I am looking at creating an AWS Data Pipeline with scheduling everyday at 12.30AM WITH Terraform.

I am using the aws_vpc_ipam_pools data source to return a list of IPAM pools in an AWS account.

Does terraform need origial code to run terraform destroy?

trying to create aws resources , i get problems in tags , can some one please help
but i want to merge tags with local.tags and with the addition tags for the resource creation , i think something to do with list and object ,

I have the infrastructure for AWS being created using Terraform. There is a SNS topic already present in another AWS account which I have to subscribe for an SQS that I have in my AWS account. How to add this subscription topic to the SQS during resource creation of SQS using Terraform?
As the SNS topic is already present in another account, I just need to refer this subscription to the SQS in my account.
Is there a way to provide subscription arn in the syntax of

I’m running into very strange behavior in terraform when making use of the jsonencode() function. I am using the AWS secrets manager terraform module to generate a database secret for my application.

I will create aws_lb and aws_lb_target_group by using Terraform, then create an ECS Service. Here are my codes:

We do have done lot of manual network configuration such as vpc peering, routing table changes, all those changes done by manually after initial network configuration has been setup using Terraform. Recently I have done new ALB related changes using Terraform, does Terraform apply destroy manually created resources, because I can only see my ALB changes only going to apply when I tested using terraform plan. seemed to be all manual changes not identified by terraform. I’m ok as far as Terraform. plan to going to destroy the manually created configuration.

I’m trying to link aws wafv2 with the API gateway stage: