Update DNS A record on Windows Server

normally you wouldn't be fooling with an A record
cname www <ipdaddress of web server>

Where was the old webserver and where is the new webserver ?
Is the web address the same as the AD domain?

domains sit with Godaddy
changed my named server on GoDaddy to goto AWS

my website works external, but wont forward internal users to the new website

Do you have an internal domain name that's the same as your registered domain name? Otherwise there's probably no need for an internal DNS record for the website at all. Internal users can just use the public DNS record.

so the local domain name and the site domain name is the same domain name i.e.
AD Domain is example.com
website is also example.com
you must use a subdomain i.e. www
A WWW <AWS IPADDRESS>

internal domain is different than website

then you either wait for the TTL to expire or on the dns servers flush the dns cache

Is there a forward lookup zone for the external domain on the internal DNS server? If so, what's it being used for? You may be able to get rid of that zone entirely, especially if the website's A record is the only thing in it.

local domain:
staff.example.com

website
example.com

there is an existing forwarding zone for
example.com  in the dns server

example.com needs to forward to example.com (aws site)

there is an existing forwarding zone for
example.com  in the dns server

Aside from the website's A record, what records are in that example.com zone?

got it.
Added an
 A record in the example.com forwarding zone.
with the IP address of AWS site.

Seems like the key here is "redirect site".

Redirects are better done using HTTPS 302 requests, rather than DNS.

For a specific/correct answer provide actual URLs + their redirection targets.

If your ad is staff.example.com

Make sure you do not have example.com as authoritative, which based on your subsequent response it is.