Hello and welcome to the community!
Just to give you some context first: Bitbucket Pipelines builds run in Docker containers. For every step you define in your bitbucket-pipelines.yml file, a Docker container starts, the repo is cloned in that container (unless you disable cloning), and then the commands of that step's script are executed in that container. When the step finishes, the container gets destroyed.
If you don't specify a Docker image in your bitbucket-pipelines.yml file, atlassian/default-image:latest will be used. However, you can use any public and private Docker images including those hosted on Docker Hub, AWS, GCP, Azure, and self-hosted registries accessible on the internet.
With regards to AWS Opsworks, if the service provides a way to deploy from another machine via command line, it may be possible to do this in Pipelines by using the same commands in the script of your bitbucket-pipelines.yml file.
I would recommend looking into AWS Opsworks documentation or contacting their support team regarding how to deploy from another machine via command line. You could then test this first by deploying locally from your machine, and then by deploying from a Docker container on that machine, before configuring it in Pipelines.
You can use secured user-defined variables for storing any credentials that may be required for authentication:
https://support.atlassian.com/bitbucket-cloud/docs/variables-and-secrets/
Kind regards,
Theodora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.