To connect your application with Cyberin S3 Object Storage, set up S3 endpoint, Space name, access key and secret key. These are the settings the app uses to authenticate with the storage service and perform actions such as uploading, downloading and retrieving files.
Prior to connecting the application, collect the following information from your Cyberin storage configuration:
Endpoint URL URL used by the application to communicate with the storage service.
Space name The name of the Space where your files are stored.
Access Key ID: The identifier used to authenticate requests.
Secret Access Key: The credential paired with the access key.
Region: The region value required by the storage service and application.
Please confirm this is the correct Storage account & space? Do not tell anyone your secret key.
Head to the app storage settings, find the S3 compatible endpoint or custom endpoint field.
Copy the Endpoint from your Cyberin S3 Object Storage configuration. Do not use your website address or a public URL of a file, these are not necessarily the API endpoint for performing storage operations.
If the application automatically connects to Amazon S3, make sure that you configure the custom endpoint, not the default endpoint.
Space name to access the files
Ensure that the spelling is correct and that you are directing the application to the proper storage location. Always return the Space name, no matter which object key or file path the application is requesting.
For example, the object key for a file saved as documents/invoice.pdf is documents/invoice.pdf. The storage container is named after the space name and the file after the object key.
Enter your Access Key ID and Secret Access Provide the S3 authentication configuration for your application.
extra whitespace, a missing letter or an expired secret key. If you rotated the credentials, update your application to use the new values.
The access key also needs to have the correct permissions for the actions that you are requesting. For instance, an application that uploads a file needs write access and an application that downloads a file needs read access.
Or better, store credentials in environment variables or a credential manager. Do not put secrets into public source code.
Some apps may need additional configuration to connect to S3 compatible storage.
Check application requirements:
Region: Enter the region value you used for your storage setup
Custom endpoint Routes Requests to the correct storage endpoint.
Use a path-style URL or a style virtual-hosted URL supported if your application supports style support.
Authentication Signature Use a signature version that is supported by the storage service and the application.
You need these values based on how the application works with s3 compatible . The default settings are different for each application.
Save Configuration In the app (if there is such an option), test the connection.
If no connection test provided do a simple operation the access key should be able to do e.g. upload a small test file
Can we shrink these figures:
The application will communicate with the endpoint you have established.
The credentials are okay .
Task was successfully completed.
Your uploaded file will be in the Space you want.
If the connection is successful but the action fails, check the permissions needed for the action.
Access Denied You are not permitted to access / on this server. Please verify the access key, secret key and permissions for the operation.
Connection Failed Please check the endpoint url, network connectivity and if the application supports custom s3 compatible endpoints.
Space not found: Check the Space name and that the endpoint and region are correct for the storage you want to access.
Auth or Sig Failed Check your credentials, region setting, system time (if applicable) and the authentication settings supported by the application.
Upload Works Download disables read permission. Check that the application is using the right access method for the file.
Files uploaded to wrong folder Check the Application Space Name and Object Key Set.
If the problem persists, please write down exactly what error message you got and what you were doing when you got it. Do not include your secret key or other sensitive credentials in support requests.