What outbound traffic requirements does Bamboo have for its "Elastic Bamboo" feature?
Asked by drewk:

Assuming we're starting with zero outbound access to the Internet, what outbound traffic requirements does Bamboo have for its "Elastic Bamboo" feature?

I assume it hits one or more AWS API endpoints. Assuming I want to restrict access based on the FQDN of these endpoints, what are they?

e.g <https://foo.aws.api.com> and <https://bar.aws.api.com>


Answers:
author: Steffen Opel _Utoolity_
body: The [Elastic Bamboo](https://confluence.atlassian.com/bamboo/about-elastic-bamboo-289277118.html) feature hits several AWS API endpoints indeed. Here are your options:

Regions and Endpoints {#toc-hId--1329469102}
--------------------------------------------

AWS maintains a list of [Regions and Endpoints](http://docs.aws.amazon.com/general/latest/gr/rande.html):
> To reduce data latency in your applications, most Amazon Web Services offer a regional endpoint to make your requests. An endpoint is a URL that is the entry point for a web service. For example, <https://dynamodb.us-west-2.amazonaws.com> is an entry point for the Amazon DynamoDB service.

* Not all AWS services are necessarily available in all regions right away, though region coverage is typically increased over time. The endpoint naming pattern seems extremely consistent meanwhile though, thus it should be possible to deduce future regional endpoints so that you wouldn't need to extend your configuration every other week (see also [Regions and Availability Zones](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html)).

Elastic Bamboo AWS Service Usage {#toc-hId--441965421}
------------------------------------------------------

The subset of AWS services facilitated by Elastic Bamboo could be deduced from the actions in an applicable [IAM Policy](http://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) for Bamboo. Unfortunately those are still not officially documented as of today though:

* <https://jira.atlassian.com/browse/BAM-14086>

However, a related long standing issue has at least seen some helpful comments in this regard:

* <https://jira.atlassian.com/browse/BAM-11932>
* The latest official statement from Atlassian I'm aware of there is [this comment](https://jira.atlassian.com/browse/BAM-11932?focusedCommentId=517789&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-517789), but there are meanwhile more actions involved so you would need to follow the comment thread to identify resp. gaps.

Regardless, your question is only concerned with the services themselves rather than actions on those, I think the following endpoints would still be sufficient right now regarding Elastic Bamboo itself:

* [Amazon EC2](http://docs.aws.amazon.com/general/latest/gr/rande.html#ec2_region)

* [Amazon S3](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region)

AWS IP Address Ranges {#toc-hId-445538260}
------------------------------------------

AWS also maintains a list of [AWS IP Address Ranges](http://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html) meanwhile:
> Amazon Web Services (AWS) publishes its current IP address ranges in JSON format. To view the current ranges, download the `.json` file. To maintain history, save successive versions of the `.json` file on your system. To determine whether there have been changes since the last time that you saved the file, check the publication time in the current file and compare it to the publication time in the last file that you saved.

Given the enormous worldwide range of all the AWS' CIDR blocks, this is obviously not all that limiting, but better than nothing of course, esp. given AWS has terms of services against malicious usage and is capable of detecting and blocking AWS accounts that systematically violate those.

* ![information](/html/@4DF2F60CA30FBCA0CD7B960B5D0F871B/images/emoticons/information.png "information") Please note that you can meanwhile [Subscribe to AWS Public IP Address Changes via Amazon SNS](https://aws.amazon.com/blogs/aws/subscribe-to-aws-public-ip-address-changes-via-amazon-sns/), as outlined in section *AWS IP Address Ranges Notifications* further down on the IP Address Ranges page.


Tags: aws

elastic-agent