I have been testing landers and the URLs that I have been using all start with:
https://s3.us-east-2.amazonaws.com/ followed by mydomainname.com/xyz.html? and the get parameters and such.
Obviously I do not want "s3.us-east-2.amazonaws.com/" displayed in my URL when directing people to my site. So I messed around with it and discovered that I can remove the "s3.us-east-2.amazonaws.com/" part from the URL and have the URL contain my actual domain name first and that it works.
However because the URL's by default uses the s3 string before my domain name when I go to copy the link from Amazon S3, I am confused whether or not this would negatively effect my URL by any means when connected with Amazon S3? Should I be leaving that part in or am I good to go? 
These strange URL will confuse some users and reduce your conversion rate.
You should register a domain, connect it to CloudFront that will serve the pages on your S3 bucket.
See here the tutorial:
https://stmforum.com/forum/showthrea...osting-and-CDN
I did that already. I guess I was just overthinking it a bit. Thank you!
My current confusion is that when I remove the https://s3.us-east-2.amazonaws.com/ part, now suddenly the offer link does not work for whatever reason. I usually get redirected to the lander that I was at after clicking on the call to action button.
Okay I figured it out. So much moving parts in this business that one missing piece can derail the whole operation.
If you use CloudFront, you should not have to use the S3 URL anywhere.
By going with S3 URL, all your pages are served from the same data center, instead of benefiting from the CloudFront CDN infrastructure.
Glad to see you fixed it.