1663832908583941.png)
S3 bucket
Here is the process to add custom files upload through S3 bucket.
S3 offers scalable, secure object storage for diverse use cases like data lakes, websites, apps, backups, and analytics. Its management features help optimize, organize, and control data access to meet business and compliance requirements.
Go to the Hello panel and click on All inboxes in the Manage section. And click on the All inboxes.
Select the inbox where to add custom files
Click on Custom File Upload
Click on Upload Type and Select S3 instead of Hello.
After that enter All the Access key of S3 bucket
Add The keys and TEST the connection
NOTE: For testing purposes a custom test bucket is created at hello. You can access the credentials from here
S3_bucket_name: hellocustomtest
S3_access_key: AKIAQRWMYOQYJ75GB5GE
S3_secret_key: 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
S3_region: ap-south-1
Click upon Test Connection .
After that Click Upon Save and Mark it as Active .
Notes -
1.Users can select S3 as a custom file store.
Setting is available for all the inboxes (currently twitter and numbers do not support the attachments but the setting is still available for the same).
All inbound and outbound messages are stored in hello S3 by default.
When a user selects storage to the client's S3, all inbound and outbound files are stored in the user's s3 for that particular inbox.
setting can only be applied to a particular inbox, for the same setting to new inbox, users need to create a new setting in another inbox.
by default attachments are stored in hello S3.
for successful completion of test/connection, S3 should be open for put,delete,and get operations.
as we are not storing any attachment data, any lost attachments and in-bounds cannot be recovered from the hello end. (in case of client S3 connection failure or accidental deletes)
As some attachments are still stored on respective micro-services (whatsapp, mailer) those attachments are not deleted from the hello end.
