The Amazon S3 Glacier Connector enables you to integrate with Amazon S3 Glacier to store files in a secure, low-cost, cloud-based service.
This connector allows your OutSystems apps to consume the following Amazon S3 Glacier capabilities:
Create and delete vaults for storing data
Upload, download, and delete archives in a vault
List the files in a vault
Setup SNS Topic notifications for asynchronous jobs completion
This component is based on the AWS SDK for .NET v3.
To use this connector you must have:
An AWS account, so you can use Amazon Glacier
An AWS access key (access key ID and secret access key)
Depending on the connector actions you want to consume, additional permissions must be set. Refer to this guide for a complete list of permissions.
See the AWS documentation for detailed information on Amazon S3 Glacier.
To configure your connector to access Amazon S3 Glacier, you need the following AWS authentication information:
AWS access key ID
Secret access key of your AWS access key
AWS Region of the service endpoint to which you want to connect. To reduce latency, choose a region close to your application server. See the API documentation for a list of region names.
Use the above information to fill in the following site properties available in the AmazonGlacierConnector_IS module:
Access Key
Secret Access Key
Region (default value is "USEast1")
The connector uses the values in these site properties as the default AWS credentials to authenticate in Amazon S3 Glacier.
Alternatively, you can specify different credentials when invoking an action from the connector in your logic by using the AWSCredentials input parameter:
Each time you run an action from the connector, the authentication in Amazon S3 Glacier is performed as follows (see this logic in GetGlacierCredentials action):
If the AWSCredentials input parameter is passed (the parameter isn’t mandatory), these values are used to authenticate.
Otherwise, the authentication uses the values in the Access Key, Secret Access Key, and Region site properties.
If the values in the site properties are not set, an exception is raised: “Invalid configuration. Please validate the values."
With this design, you have the flexibility to define a set of AWS credentials for specific actions, while using the ones configured in the site properties as default credentials for the remaining actions.