Hello,

Playing with TFC, I noticed when there was an issue with AWS credentials, I used short-lived credentials (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN). The terraform plan just hung there without showing any clue what was wrong.

Raw log downloaded:

Terraform v1.6.2
on linux_amd64
Initializing plugins and modules...
{"@Level":"info","@message":"Terraform 1.6.2","@module":"terraform.ui","@timestamp":"2023-12-15T21:14:55.531419Z","terraform":"1.6.2","type":"version","ui":"1.2"}

------------ System Message ------------
Force cancel received. The operation will now be aborted.

------------ System Message ------------
Force cancel received. The operation will now be aborted.

------------ System Message ------------
Force cancel received. The operation will now be aborted.

------------ System Message ------------
Force cancel received. The operation will now be aborted.

resource "aws_instance" "web" {
ami = data.aws_ami.ubuntu.id
instance_type = "t2.micro"
key_name = aws_key_pair.deployer.key_name
user_data = file("data.sh")
vpc_security_group_ids = [
aws_security_group.allow_ssh.id,
aws_security_group.allow_http.id
]
I have the data.sh file in the repository, and I also have the index.html file. When Terraform runs, it applies the data.sh file, but for some reason, it doesn't apply the index.html file that is located in the same repository. Do I need to add something else for it to also take into account the index.html file?
#! /bin/bash
sudo apt update
sudo apt install -y nginx
sudo rm /var/www/html/index.nginx-debian.html
sudo cp index.html /var/www/html/
sudo systemctl start nginx
sudo systemctl enable nginx