Post-Deploy Verifications are in preview for select pilot organizations and read Amazon CloudWatch Logs only.
1. Connect Amazon CloudWatch
Open Settings -> Integrations and select Configure on the Amazon CloudWatch card under Observability.1
Add a connection
Select Add AWS connection and enter the account ID and region.Under Environments, enter the deployment environments this account serves, for example
production. Match the environment the pipeline reports.2
Create the IAM role
Select Set up and validate on the connection. In the AWS account, create the IAM role named in the dialog,
gitar-cloudwatch-mcp-<region>.Choose Custom trust policy and paste the Role trust policy from the dialog. The policy permits Gitar to assume the role only with the organization’s external ID.3
Attach the permissions policy
Add an inline policy named
GitarCloudWatchRead with the CloudWatch permissions policy from the dialog.The policy grants read-only access to CloudWatch Logs Insights queries, log group listing and log anomalies in this account and region.Narrow the log group ARNs to limit access.4
Validate access
Select Validate access. Gitar checks role assumption, log group listing and access to the log groups configured for repositories using this connection.
Accounts, regions and environments
Each connection covers one AWS account and region. To read from another account or region, add another connection. The environment of a deployment decides which connection Gitar reads through, so staging and production can live in different accounts. With more than one connection, each must be tagged, and an environment can be tagged on only one connection.2. Map services to log groups
Open Settings -> Configuration and open the post-deploy verification settings for a repository, then turn on Verify deployments. A repository can only be turned on once the organization has a CloudWatch connection. Add a service for each deployable unit the repository builds, such asapi or worker.
Each log group applies to every environment by default. Limit it to specific environments only when its name differs between accounts, for example
/ecs/api-staging and /ecs/api-production.
Service and environment names may contain letters, digits, ., _, - and /, up to 64 characters.
Plans start with the next full review after verification is enabled. PRs without a plan are not verified.
3. Report deployments
Open Settings -> API Keys and select Create API key. Store the key as a secret in the deployment system, for exampleGITAR_API_KEY. See Creating an API token for details.
Deployment request
After each successful deployment from the default branch, send one Create deployment request per service. Each deployment becomes the baseline for the next one in its stream. Setservice to the configured service name and environment to the matching connection tag. The API reference defines repository owner and name for each code host and the optional deployed_at timestamp.
202 response confirms the deployment was recorded and lists the PRs scheduled for verification. Results appear in Observability from the first checkpoint, 15 minutes after deployment.
GitHub Actions
Add a step after the deployment step of a workflow that deploys from the default branch:GitLab CI
Add a job after the deployment job of a pipeline that deploys from the default branch. Store the API key as a masked CI/CD variable namedGITAR_API_KEY.
CI_PROJECT_NAMESPACE supplies the full namespace path and CI_PROJECT_NAME supplies the project path.
For a pipeline that deploys several services, add one step or job per service, or loop over them.