I have recently encountered problems running the OSB Cloud Module Installer. Have tried on three different AWS instances (all based on different Oracle AMIs). This worked fine a few weeks ago. Could Amazon have introduced changes on S3 that could affect the way the OSB Cloud Module registers with S3?
Here is some output from the installer:
Oracle Secure Backup Database Web-Service Install Tool, build 2010-03-02
OTN userid is valid.
AWS credentials are valid.
S3 user already registered.
Registration ID: XXXXXXXXXXXXXXXXXXXXXXXX
S3 Logging Bucket: XXXXXXXXXXXXXXXXXX
Validating log bucket location ...
Time-out checking log bucket location.
Please try again later.
my problem seems to be caused by us having deleted the bucket at an earlier stage. When we ran the installer script again, the installer was confused by this, and was not able to re-create a bucket.