I haven’t tested/laid hands on the AWS OpsWorks for Chef Automate, but I understand it provides Chef Management and Automate.
Any restriction with integrating Chef Compliance?
Chef Automate overlays Compliance and I wanna make sure no integration issues exist with AWS OpWorks deployment with Standalone Compliance.
Also I will have the ability to access the CLI on the OpWorks systems? i.e be able to configure LDAP on the Chef Server?
Best information are:
https://docs.chef.io/aws_opsworks_chef_automate.html
And you can join the #opsworks-automate channel on http://community-slack.chef.io/ to discuss it.
To answer your question here, automate include visibility which encompass manage/compliance and reporting as long as you use a recent version of chef client:
Quote of myself from slack:
Note
Chef 12.16.42 or greater and Chef Server 12.11.0 or greater are required.
[9:51]
https://docs.chef.io/setup_visibility_chef_automate.html
[9:53]
To collect via chef-server
[9:53]
and chef-client 12.12.15 to send directly from client to automate (chef-solo/zero use cases)
And yes at end it starts an EC2 instance, so you can access it through SSH, some caveats apply to the positioning of the AutomateServer:
Quote from AWS documentation:
Ensure the instance has outbound Internet access, and the AWS service agent is able to issue commands. Be sure that your VPC (a VPC with a single public subnet) has DNS resolution enabled, and that your subnet has the Auto-assign Public IP setting enabled.