Error inspecting states in the "s3" backend: S3 bucket does not exist - amazon-s3

Question

(I am new to this)
I am getting bellow error. I have recreated the S3 bucket so S3 bucket exit. I am building the Job from Jenkins but getting below error:
*mError inspecting states in the "s3" backend:
S3 bucket does not exist.
The referenced S3 bucket must have been previously created. If the S3 bucket
was created within the last minute, please wait for a minute or two and try
again.
Error: NoSuchBucket: The specified bucket does not exist
status code: 404, request id: DYAYRHWTW78XAKK5, host id: j6D4Tz3pfEmBBN/gEFKgKrY7JasryFp19UjXJL+7reoK0nn1WnnqZXLSgSJiL+/09foJSgVPUyg=*
I have remove the .terraform directory from my system. but still getting same error I used terraform init to re-create the .terraform.
I'm building from the Jenkins server. what else can I do?
as previously suggested by the member here. I have removed .terraform directory. Although I'm using Jenkins to initiate the build. someone said I have to erase the .terraform from jenkins server, but i don't know how to locate that file from Jenkins server.
Please see full Log below:
Started by user admin
Obtained jenkinsfile from git https://Adeboy007#bitbucket.org/adeboy007/tomcat-pipeline.git
[Pipeline] Start of Pipeline
[Pipeline] node
Running on Jenkins in /var/lib/jenkins/workspace/tomcat-pipeline
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
Selected Git installation does not exist. Using Default
The recommended git tool is: NONE
using credential bitbucket
> git rev-parse --resolve-git-dir /var/lib/jenkins/workspace/tomcat-pipeline/.git # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url https://Adeboy007#bitbucket.org/adeboy007/tomcat-pipeline.git # timeout=10
Fetching upstream changes from https://Adeboy007#bitbucket.org/adeboy007/tomcat-pipeline.git
> git --version # timeout=10
> git --version # 'git version 2.34.1'
using GIT_ASKPASS to set credentials bitbucket
> git fetch --tags --force --progress -- https://Adeboy007#bitbucket.org/adeboy007/tomcat-pipeline.git +refs/heads/*:refs/remotes/origin/* # timeout=10
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
Checking out Revision 61de65ab355b6faa5171142415c8ab56504f4758 (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 61de65ab355b6faa5171142415c8ab56504f4758 # timeout=10
Commit message: "change a to s"
> git rev-list --no-walk e181749493b7349ac4018dd85186ccda89f24423 # timeout=10
[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] withCredentials
Masking supported pattern matches of $AWS_ACCESS_KEY_ID or $AWS_SECRET_ACCESS_KEY
[Pipeline] {
[Pipeline] withEnv
[Pipeline] {
[Pipeline] stage
[Pipeline] { (checkout)
[Pipeline] echo
Pulling changes from the branch master
[Pipeline] git
Selected Git installation does not exist. Using Default
The recommended git tool is: NONE
using credential bitbucket
> git rev-parse --resolve-git-dir /var/lib/jenkins/workspace/tomcat-pipeline/.git # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url https://Adeboy007#bitbucket.org/adeboy007/tomcat-pipeline.git # timeout=10
Fetching upstream changes from https://Adeboy007#bitbucket.org/adeboy007/tomcat-pipeline.git
> git --version # timeout=10
> git --version # 'git version 2.34.1'
using GIT_ASKPASS to set credentials bitbucket
> git fetch --tags --force --progress -- https://Adeboy007#bitbucket.org/adeboy007/tomcat-pipeline.git +refs/heads/*:refs/remotes/origin/* # timeout=10
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
Checking out Revision 61de65ab355b6faa5171142415c8ab56504f4758 (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 61de65ab355b6faa5171142415c8ab56504f4758 # timeout=10
> git branch -a -v --no-abbrev # timeout=10
> git branch -D master # timeout=10
> git checkout -b master 61de65ab355b6faa5171142415c8ab56504f4758 # timeout=10
Commit message: "change a to s"
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (terraform plan)
[Pipeline] sh
+ pwd
/var/lib/jenkins/workspace/tomcat-pipeline
+ terraform init -input=true
[0m[1mInitializing the backend...[0m
[0m[0m[1mBackend configuration changed![0m
Terraform has detected that the configuration specified for the backend
has changed. Terraform will now check for existing state in the backends.
[0m
[31m
[1m[31mError: [0m[0m[1mError inspecting states in the "s3" backend:
S3 bucket does not exist.
The referenced S3 bucket must have been previously created. If the S3 bucket
was created within the last minute, please wait for a minute or two and try
again.
Error: NoSuchBucket: The specified bucket does not exist
status code: 404, request id: DYAYRHWTW78XAKK5, host id: j6D4Tz3pfEmBBN/gEFKgKrY7JasryFp19UjXJL+7reoK0nn1WnnqZXLSgSJiL+/09foJSgVPUyg=
Prior to changing backends, Terraform inspects the source and destination
states to determine what kind of migration steps need to be taken, if any.
Terraform failed to load the states. The data in both the source and the
destination remain unmodified. Please resolve the above error and try again.[0m
[0m[0m[0m
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (terraform apply approval)
Stage "terraform apply approval" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (terraform apply)
Stage "terraform apply" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (terraform destroy approval)
Stage "terraform destroy approval" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (terraform destroy)
Stage "terraform destroy" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // withCredentials
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code 1
Finished: FAILURE