Supported URL protocols
The following URL protocols are currently supported:
file://
– you can reference a configuration file from the build working directory. The file:// protocol only supports absolute paths, which requires using the build-specific${
bamboo.build.working.directory}
Bamboo variable to craft the URL, for example:file://${bamboo.build.working.directory}/cloudformation.template
http:// and https://
– you can reference a configuration file from a publicly accessible HTTP/HTTPS URL, for example:- Amazon S3 object: https://s3-ap-southeast-2.amazonaws.com/cloudformation-templates-ap-southeast-2/SQS_With_CloudWatch_Alarms.template
- Accessing private S3 objects via the
s3://
protocol is not yet supported directly, however, you can use the Generate Pre-signed URL action as a workaround.
- Accessing private S3 objects via the
- Raw Bitbucket Cloud snippet: https://bitbucket.org/!api/2.0/snippets/utoolity/eK7d/b5ec11289388bc30846e4efe5b858845bf794fa0/files/Parameter_Validate.json
- Raw GitHub source code: https://raw.githubusercontent.com/awslabs/aws-cloudformation-templates/master/aws/services/DynamoDB/DynamoDB_Table.yaml
- Amazon S3 object: https://s3-ap-southeast-2.amazonaws.com/cloudformation-templates-ap-southeast-2/SQS_With_CloudWatch_Alarms.template
Contextual entity variables
In addition to the substitution of regular Bamboo variables, some tasks also support the substitution of contextual entities via variables to ease composing unique names when operating multiple AWS resources at once, for example creating EBS snapshots from a set of EBS volumes, or EC2 images from a set of EC2 instances.
Refer to Injecting contextual entity variables into task configurations for details.