Deploys AWS ssosync to sync Google Groups with AWS SSO.

AWS ssosync is a Lambda application that regularly manages Identity Store users.

This component requires manual deployment by a privileged user because it deploys a role in the root or identity management account.

Usage

You should be able to deploy the aws-ssosync component to the same account as aws-sso. Typically that is the core-gbl-root or gbl-root stack.

Stack Level: Global Deployment: Must be deployed by managers or SuperAdmin using atmos CLI

The following is an example snippet for how to use this component:

(stacks/catalog/aws-ssosync.yaml)

components:
  terraform:
    aws-ssosync:
      vars:
        enabled: true
        name: aws-ssosync
        google_admin_email: [email protected]
        ssosync_url_prefix: "https://github.com/Benbentwo/ssosync/releases/download"
        ssosync_version: "2.0.2"
        google_credentials_ssm_path: "/ssosync"
        log_format: text
        log_level: debug
        schedule_expression: "rate(15 minutes)"

We recommend following a similar process to what the AWS ssosync documentation recommends.

Deployment

Overview of steps:

1. Configure AWS IAM Identity Center
2. Configure Google Cloud console
3. Configure Google Admin console
4. Deploy the aws-ssosync component
5. Deploy the aws-sso component

1. Configure AWS IAM Identity Center (AWS SSO)

Follow AWS documentation to configure SAML and SCIM with Google Workspace and IAM Identity Center.

As part of this process, save the SCIM endpoint token and URL. Then in AWS SSM Parameter Store, create two SecureString parameters in the same account used for AWS SSO. This is usually the root account in the primary region.

/ssosync/scim_endpoint_access_token
/ssosync/scim_endpoint_url

One more parameter you'll need is your Identity Store ID. To obtain your Identity Store ID, go to the AWS Identity Center console and select Settings. Under the Identity Source section, copy the Identity Store ID. In the same account used for AWS SSO, create the following parameter:

/ssosync/identity_store_id

2. Configure Google Cloud console

Within the Google Cloud console, we need to create a new Google Project and Service Account and enable the Admin SDK API. Follow these steps:

1. Open the Google Cloud
console: https://console.cloud.google.com
2. Create a new project. Give the project a descriptive name such as AWS SSO Sync
3. Enable Admin SDK in APIs: APIs & Services > Enabled APIs & Services > + ENABLE APIS AND SERVICES

# use raw URL so that this works in both GitHub and docusaurus

4. Create Service Account: IAM & Admin > Service Accounts > Create Service Account (ref).

# use raw URL so that this works in both GitHub and docusaurus

5. Download credentials for the new Service Account: IAM & Admin > Service Accounts > select Service Account > Keys > ADD KEY > Create new key > JSON

# use raw URL so that this works in both GitHub and docusaurus

6. Save the JSON credentials as a new SecureString AWS SSM parameter in the same account used for AWS SSO. Use the full JSON string as the value for the parameter.

/ssosync/google_credentials

3. Configure Google Admin console

• Open the Google Admin console
• From your domain’s Admin console, go to Main menu menu > Security > Access and data control > API controls (ref)
• In the Domain wide delegation pane, select Manage Domain Wide Delegation.
• Click Add new.
• In the Client ID field, enter the client ID obtained from the service account creation steps above.
• In the OAuth Scopes field, enter a comma-delimited list of the scopes required for your application. Use the scope https://www.googleapis.com/auth/cloud_search.query for search applications using the Query API.
• Add the following permission: (ref)

https://www.googleapis.com/auth/admin.directory.group.readonly
https://www.googleapis.com/auth/admin.directory.group.member.readonly
https://www.googleapis.com/auth/admin.directory.user.readonly

4. Deploy the aws-ssosync component

Make sure that all four of the following SSM parameters exist in the target account and region:

• /ssosync/scim_endpoint_url
• /ssosync/scim_endpoint_access_token
• /ssosync/identity_store_id
• /ssosync/google_credentials

If deployed successfully, Groups and Users should be programmatically copied from the Google Workspace into AWS IAM Identity Center on the given schedule.

If these Groups are not showing up, check the CloudWatch logs for the new Lambda function and refer the FAQs included below.

5. Deploy the aws-sso component

Use the names of the Groups now provisioned programmatically in the aws-sso component catalog. Follow the aws-sso component documentation to deploy the aws-sso component.

FAQ

Why is the tool forked by Benbentwo?

The awslabs tool requires AWS Secrets Managers for the Google Credentials. However, we would prefer to use AWS SSM to store all credentials consistency and not require AWS Secrets Manager. Therefore we've created a Pull Request and will point to a fork until the PR is merged.

Ref:

• awslabs/ssosync#133
• awslabs/ssosync#93

What should I use for the Google Admin Email Address?

The Service Account created will assume the User given by --google-admin / SSOSYNC_GOOGLE_ADMIN / var.google_admin_email. Therefore, this user email must be a valid Google admin user in your organization.

This is not the same email as the Service Account.

If Google fails to query Groups, you may see the following error:

Notifying Lambda and mark this execution as Failure: googleapi: Error 404: Domain not found., notFound

Common Group Name Query Error

If filtering group names using query strings, make sure the provided string is valid. For example, google_group_match: "name:aws*" is incorrect. Instead use google_group_match: "Name:aws*"

If not, you may again see the same error message:

Notifying Lambda and mark this execution as Failure: googleapi: Error 404: Domain not found., notFound

Ref:

The specific error you are seeing is because the google api doesn't like the query string you provided for the -g parameter. try -g "Name:Fuel*"

awslabs/ssosync#91

Requirements

Name	Version
terraform	>= 1.0.0
archive	>= 2.3.0
aws	>= 4.0
null	>= 3.0

Providers

Name	Version
archive	>= 2.3.0
aws	>= 4.0
null	>= 3.0

Modules

Name	Source	Version
ssosync_artifact	cloudposse/module-artifact/external	0.8.0
this	cloudposse/label/null	0.25.0

Resources

Name	Type
aws_cloudwatch_event_rule.ssosync	resource
aws_cloudwatch_event_target.ssosync	resource
aws_iam_role.default	resource
aws_lambda_function.ssosync	resource
aws_lambda_permission.allow_cloudwatch_execution	resource
null_resource.extract_my_tgz	resource
archive_file.lambda	data source
aws_iam_policy_document.ssosync_lambda_assume_role	data source
aws_iam_policy_document.ssosync_lambda_identity_center	data source
aws_ssm_parameter.google_credentials	data source
aws_ssm_parameter.identity_store_id	data source
aws_ssm_parameter.scim_endpoint_access_token	data source
aws_ssm_parameter.scim_endpoint_url	data source

Inputs

Name	Description	Type	Default	Required
additional_tag_map	Additional key-value pairs to add to each map in tags_as_list_of_maps. Not added to tags or id. This is for some rare cases where resources want additional configuration of tags and therefore take a list of maps with tag key, value, and additional configuration.	map(string)	{}	no
architecture	Architecture of the Lambda function	string	"x86_64"	no
attributes	ID element. Additional attributes (e.g. workers or cluster) to add to id, in the order they appear in the list. New attributes are appended to the end of the list. The elements of the list are joined by the delimiter and treated as a single ID element.	list(string)	[]	no
context	Single object for setting entire context at once. See description of individual variables for details. Leave string and numeric variables as null to use default value. Individual variable settings (non-null) override settings in context object, except for attributes, tags, and additional_tag_map, which are merged.	any	{ "additional_tag_map": {}, "attributes": [], "delimiter": null, "descriptor_formats": {}, "enabled": true, "environment": null, "id_length_limit": null, "label_key_case": null, "label_order": [], "label_value_case": null, "labels_as_tags": [ "unset" ], "name": null, "namespace": null, "regex_replace_chars": null, "stage": null, "tags": {}, "tenant": null }	no
delimiter	Delimiter to be used between ID elements. Defaults to - (hyphen). Set to "" to use no delimiter at all.	string	null	no
descriptor_formats	Describe additional descriptors to be output in the descriptors output map. Map of maps. Keys are names of descriptors. Values are maps of the form {<br/> format = string<br/> labels = list(string)<br/>} (Type is any so the map values can later be enhanced to provide additional options.) format is a Terraform format string to be passed to the format() function. labels is a list of labels, in order, to pass to format() function. Label values will be normalized before being passed to format() so they will be identical to how they appear in id. Default is {} (descriptors output will be empty).	any	{}	no
enabled	Set to false to prevent the module from creating any resources	bool	null	no
environment	ID element. Usually used for region e.g. 'uw2', 'us-west-2', OR role 'prod', 'staging', 'dev', 'UAT'	string	null	no
google_admin_email	Google Admin email	string	n/a	yes
google_credentials_ssm_path	SSM Path for ssosync secrets	string	"/ssosync"	no
google_group_match	Google Workspace group filter query parameter, example: 'name:Admin* email:aws-*', see: https://developers.google.com/admin-sdk/directory/v1/guides/search-groups	string	""	no
google_user_match	Google Workspace user filter query parameter, example: 'name:John* email:admin*', see: https://developers.google.com/admin-sdk/directory/v1/guides/search-users	string	""	no
id_length_limit	Limit id to this many characters (minimum 6). Set to 0 for unlimited length. Set to null for keep the existing setting, which defaults to 0. Does not affect id_full.	number	null	no
ignore_groups	Ignore these Google Workspace groups	string	""	no
ignore_users	Ignore these Google Workspace users	string	""	no
include_groups	Include only these Google Workspace groups. (Only applicable for sync_method user_groups)	string	""	no
label_key_case	Controls the letter case of the tags keys (label names) for tags generated by this module. Does not affect keys of tags passed in via the tags input. Possible values: lower, title, upper. Default value: title.	string	null	no
label_order	The order in which the labels (ID elements) appear in the id. Defaults to ["namespace", "environment", "stage", "name", "attributes"]. You can omit any of the 6 labels ("tenant" is the 6th), but at least one must be present.	list(string)	null	no
label_value_case	Controls the letter case of ID elements (labels) as included in id, set as tag values, and output by this module individually. Does not affect values of tags passed in via the tags input. Possible values: lower, title, upper and none (no transformation). Set this to title and set delimiter to "" to yield Pascal Case IDs. Default value: lower.	string	null	no
labels_as_tags	Set of labels (ID elements) to include as tags in the tags output. Default is to include all labels. Tags with empty values will not be included in the tags output. Set to [] to suppress all generated tags. Notes: The value of the name tag, if included, will be the id, not the name. Unlike other null-label inputs, the initial setting of labels_as_tags cannot be changed in later chained modules. Attempts to change it will be silently ignored.	set(string)	[ "default" ]	no
log_format	Log format for Lambda function logging	string	"json"	no
log_level	Log level for Lambda function logging	string	"warn"	no
name	ID element. Usually the component or solution name, e.g. 'app' or 'jenkins'. This is the only ID element not also included as a tag. The "name" tag is set to the full id string. There is no tag with the value of the name input.	string	null	no
namespace	ID element. Usually an abbreviation of your organization name, e.g. 'eg' or 'cp', to help ensure generated IDs are globally unique	string	null	no
regex_replace_chars	Terraform regular expression (regex) string. Characters matching the regex will be removed from the ID elements. If not set, "/[^a-zA-Z0-9-]/" is used to remove all characters other than hyphens, letters and digits.	string	null	no
region	AWS Region where AWS SSO is enabled	string	n/a	yes
schedule_expression	Schedule for trigger the execution of ssosync (see CloudWatch schedule expressions)	string	"rate(15 minutes)"	no
ssosync_url_prefix	URL prefix for ssosync binary	string	"https://github.com/Benbentwo/ssosync/releases/download"	no
ssosync_version	Version of ssosync to use	string	"v2.0.2"	no
stage	ID element. Usually used to indicate role, e.g. 'prod', 'staging', 'source', 'build', 'test', 'deploy', 'release'	string	null	no
sync_method	Sync method to use	string	"groups"	no
tags	Additional tags (e.g. {'BusinessUnit': 'XYZ'}). Neither the tag keys nor the tag values will be modified by this module.	map(string)	{}	no
tenant	ID element _(Rarely used, not included by default)_. A customer identifier, indicating who this instance of a resource is for	string	null	no

Outputs

Name	Description
arn	ARN of the lambda function
invoke_arn	Invoke ARN of the lambda function
qualified_arn	ARN identifying your Lambda Function Version (if versioning is enabled via publish = true)

References

• cloudposse/terraform-aws-components - Cloud Posse's upstream component

Tip

👽 Use Atmos with Terraform

Cloud Posse uses atmos to easily orchestrate multiple environments using Terraform.
Works with Github Actions, Atlantis, or Spacelift.

Watch demo of using Atmos with Terraform

Example of running atmos to manage infrastructure from our Quick Start tutorial.

Related Projects

Check out these related projects.

• Cloud Posse Terraform Modules - Our collection of reusable Terraform modules used by our reference architectures.
• Atmos - Atmos is like docker-compose but for your infrastructure

Tip

Use Terraform Reference Architectures for AWS

Use Cloud Posse's ready-to-go terraform architecture blueprints for AWS to get up and running quickly.

✅ We build it together with your team.
✅ Your team owns everything.
✅ 100% Open Source and backed by fanatical support.

📚 Learn More

Cloud Posse is the leading DevOps Accelerator for funded startups and enterprises.

Your team can operate like a pro today.

Ensure that your team succeeds by using Cloud Posse's proven process and turnkey blueprints. Plus, we stick around until you succeed.

Day-0: Your Foundation for Success

• Reference Architecture. You'll get everything you need from the ground up built using 100% infrastructure as code.
• Deployment Strategy. Adopt a proven deployment strategy with GitHub Actions, enabling automated, repeatable, and reliable software releases.
• Site Reliability Engineering. Gain total visibility into your applications and services with Datadog, ensuring high availability and performance.
• Security Baseline. Establish a secure environment from the start, with built-in governance, accountability, and comprehensive audit logs, safeguarding your operations.
• GitOps. Empower your team to manage infrastructure changes confidently and efficiently through Pull Requests, leveraging the full power of GitHub Actions.

Day-2: Your Operational Mastery

• Training. Equip your team with the knowledge and skills to confidently manage the infrastructure, ensuring long-term success and self-sufficiency.
• Support. Benefit from a seamless communication over Slack with our experts, ensuring you have the support you need, whenever you need it.
• Troubleshooting. Access expert assistance to quickly resolve any operational challenges, minimizing downtime and maintaining business continuity.
• Code Reviews. Enhance your team’s code quality with our expert feedback, fostering continuous improvement and collaboration.
• Bug Fixes. Rely on our team to troubleshoot and resolve any issues, ensuring your systems run smoothly.
• Migration Assistance. Accelerate your migration process with our dedicated support, minimizing disruption and speeding up time-to-value.
• Customer Workshops. Engage with our team in weekly workshops, gaining insights and strategies to continuously improve and innovate.

✨ Contributing

This project is under active development, and we encourage contributions from our community.

Many thanks to our outstanding contributors:

For 🐛 bug reports & feature requests, please use the issue tracker.

In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.

1. Review our Code of Conduct and Contributor Guidelines.
2. Fork the repo on GitHub
3. Clone the project to your own machine
4. Commit changes to your own branch
5. Push your work back up to your fork
6. Submit a Pull Request so that we can review your changes

NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!

🌎 Slack Community

Join our Open Source Community on Slack. It's FREE for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally sweet infrastructure.

📰 Newsletter

Sign up for our newsletter and join 3,000+ DevOps engineers, CTOs, and founders who get insider access to the latest DevOps trends, so you can always stay in the know. Dropped straight into your Inbox every week — and usually a 5-minute read.

📆 Office Hours

Join us every Wednesday via Zoom for your weekly dose of insider DevOps trends, AWS news and Terraform insights, all sourced from our SweetOps community, plus a live Q&A that you can’t find anywhere else. It's FREE for everyone!

License

Preamble to the Apache License, Version 2.0

Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

  https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.

Trademarks

All other trademarks referenced herein are the property of their respective owners.

---

Copyright © 2017-2024 Cloud Posse, LLC