Hi @billowy-army-68599,
Does not seems like
dig https://sts.eu-west-1.amazonaws.com/
; <<>> DiG 9.10.6 <<>> https://sts.eu-west-1.amazonaws.com/
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 45986
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;https://sts.eu-west-1.amazonaws.com/. IN A
;; AUTHORITY SECTION:
. 10800 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2023060401 1800 900 604800 86400
;; Query time: 83 msec
;; SERVER: 20018a07b3ff500:1#53(20018a07b3ff500:1)
;; WHEN: Sun Jun 04 133520 WEST 2023
;; MSG SIZE rcvd: 140
nslookup sts.eu-west-1.amazonaws.com
Server: 20018a07b3ff500:1
Address: 20018a07b3ff500:1#53
Non-authoritative answer:
Name: sts.eu-west-1.amazonaws.com
Address: 67.220.224.163
big-jordan-24260
06/04/2023, 9:01 PM
Hi,
Only to provide more information on this topic, the only solution that I found is to rebuild the entire project, by deleting all resources in AWS and creating the stacks and deploy again.