Thanks for the heads up on this thread :-)
Very sorry for the delayed response Ross.
Are there any pitfalls at all to be aware of in terms of S2 Member/ Amazon S3 and Cloudfront integration.
DNS will change obviously, but domain name will of course stay the same.
Does S3 work from the domain name?
None that I’m aware of. S3/CloudFront are based on host addresses established on the Amazon side of things. Unless you’ve configured CNAMEs for your Buckets or CloudFront distros; there is really nothing to worry about. Even then, the changes would occur in DNS alone; and should not be impacted by your s2Member installation.
I can’t really think of any issue with this.
Does S3 work from the domain name?
No. It’s a remote server with it’s own host name (i.e. a 3rd party service).
Are there any changes I will need to make with S2 integration at all, or anything I need to be aware of?
I would be sure to run the s2Member® Server Scanner on your new server before moving.
See: Knowledge Base » s2Member® Server Scanner
You will want to make sure that you have all of the required PHP extensions installed (the Server Scanner will help you with that). You will also want to verify things like email server configuration, SSL certificates, etc. All of that is standard stuff though, when you prepare a server.
Also, make sure that your /wp-content/plugins/s2member-logs/ directory remains writable on the new server; after you move things over. I can’t think of anything more that would be s2Member-specific really.