[aws-opsworkscm]

https://docs.aws.amazon.com/opsworks/latest/userguide/opscm-create-server-cfn.html
has a note that if you use a custom domain you will need to create a cname record before you will be able to use
the server. it has you run
```
aws opsworks describe-servers --server-name server_name
```
to get the value of the endpoint to point the cname at. I thought about filing this as a documentation bug, but realized that it is probably doing this because cloudformation does not provide the endpoint as an output, so even if I am using route53, I probably still have to manually get that endpoint value and then make the cname manually.

However, since the aws cli _can_ get the value, it suggests that CDK can get the value. if CDK can get the value, then CDK should have a method with which I could then provide a call to new route53.CnameRecord() the required inputs.

### Use Case

I'm trying to make standing up the my infrastructure as automatic as possible with little to no human intervention. Having infrastructure as code is after all a great thing, but breaks down when a critical component requires manual configuration.

### Proposed Solution

since AWS Cli can obtain the needed information, so too should CDK be able to. Given an instance of an OpsWorksCM server, I should be able to obtain the value using a method on that server.

### Other

* [ ] :wave: I may be able to implement this feature request
* [ ] :warning: This feature might incur a breaking change

---

This is a :rocket: Feature Request

Start with the AWS OpsWorksCM server construct and the CloudFormation documentation at the linked OpsWorksCM page, then compare its available values with `aws opsworks describe-servers --server-name server_name`. Check how the server could expose the endpoint needed by `route53.CnameRecord`; done means the endpoint is available through the CDK server instance for fully automated DNS configuration.

Written by the indexing model from the issue text.