Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting up aws-saas-boot for Keycloak #518

Open
sj-metta opened this issue Jun 11, 2023 · 2 comments
Open

Setting up aws-saas-boot for Keycloak #518

sj-metta opened this issue Jun 11, 2023 · 2 comments
Labels
needs-reproduction Can't reproduce issue

Comments

@sj-metta
Copy link

❓ General Issue

The Question

Hi Team , I am trying to setup saas boost as POC for Keyclock. I am getting below error in cloud formation
Embedded stack arn:aws:cloudformation:ap-south-1:7----9:stack/sb-dev5-idp-9UQAMTET4MLY-keycloak-----/-----02cf-11ee------0ad4aa078e90 was not successfully created: The following resource(s) failed to create: [InvokeKeycloakSetup, KeycloakRecordSetAlias].

Environment

  • AWS SaaS Boost Version: 2.2.3

Other information

@sj-metta sj-metta added the triage Needs categorization and prioritization label Jun 11, 2023
@sj-metta
Copy link
Author

I having trouble providing a domain , looks like a DNS issue but not getting any more information from error.

@brtrvn
Copy link
Contributor

brtrvn commented Jun 20, 2023

When you choose Keycloak as your System Users identity provider, you have to provide 3 things:

  • The domain name you want to use for the Keycloak install that SaaS Boost is going to provision
  • The Route 53 public hosted zone that has NS name server entries in it for the FQDN in step 1
  • An Amazon Certificate Manager (ACM) SSL cert that matches the domain name in step 1 either as a wildcard cert or a specific one.

SaaS Boost will add an A record to the hosted zone for the domain name you gave to the installer when setting up the load balancer. It's your responsibility to make sure the domain name you use for your Keycloak install is routable from the internet (DNS is active and property setup).

To debug what happened, I'd double check the CloudWatch Logs for the Keycloak setup Lambda, the CodeBuild project that deploys Keycloak to ECS, and general DNS debugging like doing an nslookup or dig against the domain name you used for your Keycloak install.

All of these restrictions are in place because Keycloak requires a valid, public SSL certificate in order to operate.

@brtrvn brtrvn added needs-reproduction Can't reproduce issue and removed triage Needs categorization and prioritization labels Jul 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-reproduction Can't reproduce issue
Projects
None yet
Development

No branches or pull requests

2 participants