Your best option would be to simply create a new developer account and sign up for S3 again with a different ID. This would appear to be a clear Amazon bug and I doubt there's anything that can be done by anyone except Amazon technical support.
There is no documented way to change ownership of a bucket. To the contrary, the documentation states that bucket ownership cannot be changed.
Bucket ownership is not transferable
Even it were possible, that still leaves the issue of ownership of the objects in the bucket, since ...
This question is a bit old, but for those looking for an easier method.
You can delete your aws s3 folder with no name by deleting the contents within it.
The blank (no name) folder will be removed automatically.
as also mentioned, the likely cause of these existing is a double-slash. In my case I was inserting a variable between two slashes and that ...
If you aren't able to edit the permissions, you may have lost access to these objects.
Bucket and object permissions are completely independent; an object does not inherit the permissions from its bucket. For example, if you create a bucket and grant write access to another user, you will not be able to access that user’s objects unless the user explicitly ...
Why can't you use your bill to get that number ? Is that not what shows up in the detail section of the Amazon Simple Storage Service TimedSTorage-ByteHrs section? It breaks it down by total size of stored object (<1TB, 1-50TB, 50+ ...et.c.) but you can do simple math then.