You're welcome Sunny

Thanks for your input, i have one further question, if i now integrate Amazon S3, would this mean that all old avatars and cover images will move to amazon and thereafter i can delete the cache folder.

Yes, all the old avatar, cover or other media file will push into Amazon S3, but have to wait for your cronjob process and it will took time to push those item into your Amazon S3.

You actually no need to delete it manually, because we do have a setting call 'Delete Files After Upload' from backend > Easysocial > setting > storage , mean when those item already pushed in Amazon S3, it will automatically help you delete the file from your server.

Secondly doesnt the cache get regenerated? i mean after cleaning?.
What i was thinking is to delete the cache folder, take akeeba and move the site to local for upgrade.

Yes, it can regenerate again for those cache image link but you have to truncate this table #__social_links from your database.

Because the system will check whether this link stream is it already cached before, if don't have, the system will automatically re-crawl again that link website and stored the data into your database.

Also is using Amazon S3 reversible? i.e if i decide later on to stop using Amazon S3, would my website server images from local.

I had a bad experience about 2 years ago, i had used Amazon S3 feature in easysocial, but when later i shifted back to local, the images were not found as the links were pointing to Amazon.

Yes, it can able to pull back those image file from Amazon S3 to your local server.
Currently I can't recall what is the issue you facing previously, perhaps you can try into your development site and see whether after pull back the image from Amazon S3 is it able to show correctly the image link on frontend.