Slack launched GovSlack in July 2022. With GovSlack, authorities companies, and people they work with, can allow their groups to seamlessly collaborate of their digital headquarters, whereas conserving safety and compliance on the forefront. Utilizing GovSlack contains the next advantages:
- Helps key authorities safety requirements, similar to FedRAMP Excessive, DoD IL4, and ITAR
- Runs in AWS GovCloud knowledge facilities
- Allows exterior collaboration with different GovSlack-using organizations by means of Slack Join
- Supplies entry to your individual set of encryption keys for superior auditing and logging controls
- Permits permission and entry controls at scale by means of Slack’s enterprise-grade admin dashboard
- Features a listing of curated functions (together with DLP and eDiscovery apps) that may combine with Slack
- Maintained and supported by US personnel
Earlier than the massive launch, the Cloud Foundations workforce spent nearly two quarters organising the infrastructure wanted to run GovSlack.
GovSlack is the very first service Slack launched on AWS Gov infrastructure. Subsequently we needed to spend a major period of time studying the variations between customary and Gov AWS and making adjustments to our tooling and the platform to have the ability to run on Gov AWS.
On this weblog put up, we’re going to take a look at how we constructed the AWS infrastructure wanted for GovSlack and challenges we confronted. If you happen to’re occupied with constructing a brand new service on AWS GovCloud, this put up is for you.
How are GovCloud accounts associated to business accounts?
Not way back, Slack began shifting from a single AWS account to baby accounts. As a part of this venture, we additionally made vital adjustments to our international community infrastructure. You may learn extra about this within the weblog posts Constructing the Subsequent Evolution of Cloud Networks at Slack and Constructing the Subsequent Evolution of Cloud Networks at Slack – A Retrospective. We have been capable of make the most of most of our learnings into constructing the GovSlack community infrastructure.
To begin with, AWS Gov accounts do not need any billing functionality. The sources within the Gov accounts will propagate their billing right into a linked shell business AWS account. While you request a Gov AWS account, a linked shell business AWS account is routinely created. Subsequently the very first thing we needed to do was to request a Gov root AWS account utilizing our root payer business account. This was a prolonged course of, however not as a result of it was a technically tough factor to do—it was so simple as clicking a button on our root business AWS account. Nevertheless including the Gov Accounts to our present agreements with AWS did take a couple of weeks. As soon as we had our Gov root account, we have been capable of request extra GovCloud accounts for our service groups. It’s value mentioning that GovCloud baby accounts nonetheless have to be requested utilizing the business AWS API utilizing the create-gov-cloud-account name.
When a brand new GovCloud baby account is created, you possibly can assume the OrganizationAccountAccessRole within the baby account by way of the GovCloud root account’s OrganizationAccountAccessRole (this position title might differ when you override the title utilizing –role-name flag).
Let’s take a look at what are these hyperlinks seem like in a diagram:
As we are able to see above, all our GovCloud sources prices are propagated to our root business AWS account.
How did we create GovCloud accounts?
As we mentioned above, we use the AWS organizations API and the create-gov-cloud-account name to request a brand new GovCloud baby account. This course of creates two new accounts: the GovCloud account and the linked business AWS account. We use a pipeline on the business facet for this portion of the method. Then the linked business AWS account is moved to a extremely restricted OU, so it’s blocked from creating any AWS sources in it.
We use a Jenkins pipeline within the AWS Gov partition to configure the GovCloud baby account. We will assume the OrganizationAccountAccessRole of the brand new baby account from the GovCloud root account as quickly as it’s created. Nevertheless our Gov Jenkins companies are positioned in a devoted baby account. Subsequently there’s a step on this pipeline that may replace the kid account’s OrganizationAccountAccessRole’s belief coverage, so it may be assumed by the Jenkins staff. This step should be accomplished first earlier than we are able to transfer on to different steps of the kid account configuration course of.
How can we separate GovDev and GovProd?
As talked about beforehand, one of many core compliance necessities for a GovCloud atmosphere was that solely US individuals can be licensed to the manufacturing atmosphere. With this requirement in thoughts we made the choice to face up two Gov environments, one being the manufacturing Gov atmosphere, identified internally as “GovProd”, and a second atmosphere, often called “GovDev”. The GovDev atmosphere will be accessed by anybody and check their companies earlier than being deployed to GovProd by US personnel.
To make sure we have now full isolation between these environments, we have now approached the construct out utilizing a full shared-nothing paradigm, which permits the environments to function in utterly completely different AWS organizations. The layer 3 networking mesh we use (Nebula) is totally disconnected, which means the networks are completely segregated from each other.
To archive this, we created two AWS organizations in GovCloud, and beneath every of those organizations, an equivalent set of kid accounts to launch our companies within the Dev and Prod environments.
Is that this actually remoted?
When a brand new baby account is created, we have to use the Gov root account for assuming the OrganizationAccountAccessRole’s into it for the primary portion of the provisioning as we mentioned right here. Since solely US personnel can entry the Gov prod accounts, solely US personnel are capable of entry the Gov root account, as this account has entry to imagine the OrganizationAccountAccessRole within the baby accounts. Subsequently the preliminary provisioning of dev accounts additionally should run on Gov prod Jenkins, and US personnel are required to be engaged to kick off the preliminary a part of GovDev accounts creation.
GovProd additionally lacks some AWS companies, similar to CloudFront and public zones in Route53. Moreover, after we are utilizing the AWS CLI in GovCloud, we should move within the –area flag or set the AWS_DEFAULT_REGION atmosphere variable with a Gov area because the AWS CLI all the time defaults to a business area for API calls.
Route53 and ACM
A few of our Gov companies use AWS ACM for the load balancer SSL certifications. We keep away from utilizing e mail certificates validation as this doesn’t permit us to auto-renew expiring certificates. ACM DNS helps auto-renewal however requires public DNS data to take action. Subsequently, we use the identical devoted business DNS account for validating our ACM certificates as effectively. Entry to this business DNS account is restricted to US personnel.
AWS GovCloud doesn’t help public Route53 zones. Nevertheless personal zones are allowed. We created a GovDev and Gov Prod DNS account for internet hosting personal Route53 zones. The Cloud Foundations workforce creates VPCs in a set of accounts managed by us, then we use AWS Transit gateways to attach completely different areas collectively and construct a worldwide community mesh. Lastly these VPCs are shared into baby accounts to summary the complexity of organising networks from utility groups. You may learn extra about how we do that in our different two weblog posts Constructing the Subsequent Evolution of Cloud Networks at Slack and Constructing the Subsequent Evolution of Cloud Networks at Slack – A Retrospective
The personal Route53 zones we create are hooked up to the shared VPCs, in order quickly as a file is added to those zones, it may be resolved inside our VPCs.
Nevertheless since GovCloud doesn’t help public DNS, we have to create these data on the business facet. Subsequently, we created a devoted business AWS account for internet hosting public GovSlack DNS data. Entry to this business DNS account is restricted to US personnel.
How can we switch artefacts between business and GovCloud?
AWS doesn’t help assuming roles between AWS customary and AWS GovCloud partitions. Subsequently we created a mechanism to compliantly move objects to GovCloud.
This mechanism ensures the objects are pulled into AWS GovCloud partition from the usual partition utilizing AWS IAM credentials. Credentials to entry the usual partition for pulling these objects are saved securely on the AWS GovCloud partition.
We use Terraform modules for constructing our infrastructure as a set of interdependent sources similar to VPCs, Web Gateways, Transit Gateways, and route tables. We wished to make use of the identical modules for constructing our Gov infrastructure so we are able to preserve these patterns constant between AWS Gov and customary partitions. One key distinction between the business and Gov AWS sources are the sources ARNs. Business ARNs begin with
arn:aws versus Gov ARNs begin with
Subsequently we needed to construct a quite simple Terraform module known as
aws_partition. Utilizing outputs of this module, we are able to programmatically construct ARNs and uncover which AWS partition we’re in.
Let’s take a look at the
knowledge "aws_caller_identity" "present" knowledge "aws_arn" "arn_details" arn = knowledge.aws_caller_identity.present.arn output "partition" worth = knowledge.aws_arn.arn_details.partition output "is_govcloud" worth = exchange(knowledge.aws_arn.arn_details.partition, "gov", "") != knowledge.aws_arn.arn_details.partition ? true : false
Now let’s take a look at a instance utilization,
module "aws_partition" supply = "../modules/aws/aws_partition" knowledge "aws_iam_policy_document" "instance" assertion impact = "Permit" actions = [ "s3:GetObject", ] sources = [ "arn:$module.aws_partition.partition:iam::*:role/some-role", ] useful resource "aws_config_config_rule" "instance" rely = module.aws_partition.is_govcloud ? 1 : 0 title = "example-rule" supply proprietor = "AWS" source_identifier = "S3_BUCKET_SERVER_SIDE_ENCRYPTION_ENABLED"
Over the past three years Slack has been working very onerous to utilize AWS’ VPC endpoints for accessing native AWS companies in our business atmosphere. They cut back the latency and enhance the resiliency of our programs, whereas additionally lowering our networking prices.
With all these benefits, it’s very simple to imagine that it’s a easy transfer, however one obvious problem that we have now present in each the business and GovCloud transfer to VPC endpoints is that AWS doesn’t all the time help all companies in all AZs. Very often we have now discovered that we have to help the power for programs to entry AWS companies each with and with out VPC endpoints, which at instances can create summary edge circumstances that may be onerous to account for.
Whereas AWS is continually releasing these VPC endpoints at a AZ degree, we nonetheless haven’t reached 100% of companies enabled for 100% of the areas/AZs we run our service in.
Whereas we have been constructing out the Gov atmosphere, we began through the use of IAM customers to bootstrap the Gov atmosphere, however this was solely ever going to be a short-term answer. AWS just lately launched the AWS-SSO answer into their business atmosphere and much more just lately of their Gov atmosphere. As this was an entire greenfield buildout it was a very good alternative to experiment with new applied sciences and enhance our present implementation.
Not like AWS’ customary IAM roles, AWS-SSO permission units are an org-wide international (throughout the complete org, versus an account) useful resource, and this adjustments how we construct and deploy them.
Since deploying AWS-SSO within the GovCloud atmosphere, we have now taken the learnings and back-ported it into our business atmosphere. Whereas we already had an present SSO system in place for entry to the whole lot of our business AWS atmosphere, utilizing AWS-SSO has made this course of quite a bit smoother and simpler.
So what have we realized?
Rebuilding our complete community infrastructure gave us the power to check our tooling, processes, and Terraform modules, and gave us the chance to make enhancements. We have been capable of clear up a mess of hardcoded values and alter issues to be extra reusable. We have been additionally capable of take a step again and have a deep dive into our processes, instruments, AWS footprint and acquire a better understanding of our platform as this entire course of gave us a possibility to rebuild Slack from scratch.