What authentication does the AWS OpsWorks API use?

OpsWorks is signed with AWS Signature Version 4 using IAM access keys. Each stack additionally has its own permissions model - SetPermission grants a user SSH and sudo access on instances inside a stack. Through Jentic, AWS credentials live in your Jentic One instance and are used to sign each control-plane call on the agent's behalf.

Can I deploy an app across all instances with a single API call?

Yes. CreateDeployment takes a stackId, an optional appId, an optional list of instanceIds, and a Command (Name=deploy, undeploy, configure, restart, execute_recipes, etc.). If you omit instanceIds, OpsWorks runs the command across the whole stack and returns a deploymentId you can poll with DescribeDeployments.

What are the rate limits for OpsWorks?

OpsWorks applies per-account throttling on the control plane. Long-running operations like CreateInstance + StartInstance run Chef recipes that can take several minutes per instance, so always poll DescribeInstances rather than retrying the create call.

How do I deploy an app through Jentic?

Use the Jentic search query 'deploy an OpsWorks app', load CreateDeployment, and execute it with stackId, appId and Command.Name=deploy. Jentic signs the request with SigV4 against your stored AWS credentials and returns the deploymentId, which the agent can then check with DescribeDeployments.

Is AWS OpsWorks Stacks being deprecated?

AWS has communicated that OpsWorks Stacks will reach End-of-Life. The control-plane API remains available for existing customers, but new workloads should target Systems Manager, CloudFormation, or container-based services. The Describe* endpoints are particularly useful for inventorying existing stacks ahead of migration.

Can I limit what my agent is allowed to do with the AWS OpsWorks API?

Yes. Jentic One is self-hosted, so the rules you set on your own instance decide which OpsWorks operations and AWS credentials your agent can use. Because OpsWorks carries stack, layer, and instance ids in the request body rather than the URL path, scoping is done per operation rather than by path prefix. You can allow only the operations the agent needs, such as DescribeStacks and CreateDeployment, and leave destructive ones like DeleteStack and DeleteInstance out unless you explicitly add them.