|Posted: Wednesday Jun 6th, 2012 at 9:26 am #15684|
Error code: 400. Error Message: Unable to delete existing Amazon® CloudFront Origin Access Identity. Unable to delete existing Amazon® CloudFront Origin Access Identity. Bad Request
I set up and tested Amazon S3 bucket – works fine.
Having trouble setting CloudFront:
I’m assuming s2member’s keeps track of current setup and may “confused” as it shows a distribution exists, while I manually removed all distributions (the one set by s2member and others I set myself for other purposes). I tried removing/re-entring the keypair ID and private key and nothing worked.
Is there a way to reset s2member to start afresh? Alternatively, somehow make it realize there are no distros so no need to delete anything before setting a new s2member distrto? Perhaps the issue is elsewhere.
Followed other threads with similar issues, but couldn’t find answers which seemed pertaining to the case at hand. The one potentially relevant post is: http://www.s2member.com/forums/topic/unable-to-auto-configure-amazon-cloudfront/#post-11763
Please advise. Many Thanks…
Addenda (some thoughts which may help):
2. Saved the configuration and inspected the file. Seems that some of the CloudFront stuff isn’t cleared. I’m contemplating clearing it manually then reloading the config file. There are two potential issues with that:
3. The above seems to indicate a need for additional logic: Since users may modify the setup on Amazon manually (or there can be some glitch), it would make sense to add code to verify the setup on Amazon and adjust s2member accordingly. Right now it seems that s2member believes there’s a CloudFront distro it needs to delete, before reconfiguring, while I’ve manually removed all distros.
Please advise. Let me know if the config file idea may work, or else, some other way to resolve this… Thanks again.
- s2Member® Products