Closed nobodynate closed 10 months ago
With terraform 1.4.5 and aws-cli/2.11.12 I was able to deploy this without error. The deprecated warning still appears, but I get the success message instead of file provisioner error.
Apply complete! Resources: 48 added, 0 changed, 0 destroyed.
Now I think the actual issue is the i/o timeout error. Maybe this is just an issue on the user's network configuration?
Launched with Terraform version 1.2.0
and 1.5.6
and neither had the error.
Did run into a error with bucket ACLs.
Error: creating S3 bucket ACL for cg-keystore-s3-bucket-rce-web-app-cgidbw91vqponv: AccessControlListNotSupported: The bucket does not allow ACLs
I'll open a PR to fix this. Going to removing the aws_s3_bucket_acl
resources, its now default for aws buckets to be private. Going to also cleanup some of the TF ""module"".
Hi everyone, I am still getting the timeout error :(
AWS CLI version: aws-cli/2.15.6 Python/3.11.6 Darwin/23.1.0 exe/x86_64 prompt/off Terraform: Terraform v1.6.6
Is there any fix for this?
@adiveli
Could you public IP have changed?
If you look in the whitelist.txt
does it differ than what you get from running curl ifconfig.me
?
You can also try seeing if the port is open
nmap -T4 -Pn -p 22 54.198.184.232
@andrew-aiken I have reissued : config whitelist --auto ; and now it seems to work. Thanks a lot for your help 🫡
Discord Thread
On a newly installed environment, when trying to deploy the rce_web_app scenario, a user got the following errors:
According to terraform aws provider docs
aws_s3_bucket_object
has been deprecated in favor of theaws_s3_object
and will be removed in a future version (though I can't find which version).The scenario successfully deploys in a docker container with Terraform 1.3.9.