Quick Start
Get results in < 5 minutes for either AWS, GCP, or Azure
All Cloud Provider Pre-requisites
1) Configure an environment variable file (use one of our templates to get started) to control the specifics of cloud-concierge's coverage.
2) Run docker pull dragondropcloud/cloud-concierge:latest
to pull the latest image.
AWS
a) Run aws config
on your CLI and ensure that credentials with read-only access to your cloud are configured. If referencing state files stored in an s3 bucket, the credentials specified should be able to read those state files as well.
b) Run the cloud-concierge container using the following command:
On Windows, substitute $HOME/.aws:
for ~/.aws:
in the above command.
c) Upon job completion, check the repository against which you configured cloud-concierge to run. There will be a new Pull Request that has been created by Cloud Concierge.
GCP
a) Run gcloud auth application-default login
on your CLI and ensure that your role has read-only access to your cloud. If referencing state files stored in a GCS bucket, the selected role should be able to read those state files as well.
b.1) On MacOS/Linux, run the cloud-concierge container using the following command:
b.2) On Windows, run the cloud-concierge container using the following command:
Azure
a) Create a service account with read-access to your cloud environment, as well as the ability to read state files in an Azure blob storage container if necessary for your cloud-concierge execution. Store credentials for this service account in the file ~/.azure/sa_credentials.json
with the following format*:
*We are very aware that this is not an ideal workflow, and are tracking a ticket to improve the ease of using cloud-concierge with Azure here.
b) Run the cloud-concierge container using the following command:
On Windows, substitute $HOME/.azure:
for ~/.azure:
in the above command.
Last updated