Service Descriptors

Cloud CMS allows you to connect to external cloud-based services for purposes of things like:

  • external data storage for binary data
  • auto-record updates to dns servers
  • event handling to cloud notification handlers

To configure these services, you simply create a service descriptor via the main interface:

Service descriptors are declared once and can be re-used multiple times within your platform, across different projects and applications. Service descriptors are encrypted on the server side and their configuration information, while externally editable, is not readable by anything other than internal services within Cloud CMS.

In other words, service descriptor information is treated as highly secure and cannot be retrieved via the content API.

Amazon S3

Here is a sample configuration for Amazon S3:

{
    "title": "My Amazon S3 Configuration",
    "key": "my_s3",
    "type": "AWS_S3",
    "family": "BINARY_STORAGE_SERVICE",
    "configuration": {
        "accessKey": "<amazon access key>",
        "secretKey": "<amazon secret key>",
        "bucketName": "mybucket",
        "region": "<amazon region id>"
    }
}

Amazon SNS

Here is a sample configuration for Amazon SNS so that SNS will pick up notification messages for application deployments:

{
    "title": "My Amazon SNS Configuration",
    "key": "my_sns",
    "type": "AWS_SNS",
    "family": "DEPLOYMENT_NOTIFICATION_SERVICE",
    "configuration": {
        "accessKey": "<amazon access key>",
        "secretKey": "<amazon secret key>",
        "region": "<amazon region id>"
    }
}

Amazon Route 53

Here is a sample configuration for Amazon Route 53:

{
    "title": "My Amazon Route53 Configuration",
    "key": "my_route53",
    "type": "AWS_ROUTE53",
    "family": "DNS_SERVICE",
    "configuration": {
        "accessKey": "<amazon access key>",
        "secretKey": "<amazon secret key>",
        "region": "<amazon region id>"
    }
}