Add support for the new Cognito Managed Login UI

[obrassard]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Amazon Cognito introduces Managed Login, a fully-managed, hosted sign-in and sign-up experience that customers can personalize to align with their company or application branding.

Announcement

I am trying to create a Cognito User pool using the new Managed Login UI. Based on the documentation it seems that it is not yet supported in @pulumi/aws/cognito.

I found some documentation related to this feature in@pulumi/aws-native (https://www.pulumi.com/registry/packages/aws-native/api-docs/cognito/userpooldomain/) however when using the package it seems that this type of entity cannot be created by AWS Cloud Control API.

  const domain = new aws_native.cognito.UserPoolDomain("main", {
    domain: "myCustomDomainPrefix",
    userPoolId: pool.id,
    managedLoginVersion: 2, // 2 for the new UI
  });

This code returns the following error message : UnsupportedActionException: The resource AWS::Cognito::UserPoolDomain is not yet supported via Cloud Control API

Is there a plan to support this new feature soon in Pulumi ?
Thanks

[obrassard]

After more search, I realized that part of the Managed UI could be setup with the aws-nativeplugin.
https://www.pulumi.com/registry/packages/aws-native/api-docs/cognito/managedloginbranding/

However, we still haven't found a way to configure the UserPoolDomain properly so that it uses the new type of login page. By default it it the Hosted UI v1.

[corymhall]

@obrassard it looks like the AWS::Cognito::UserPoolDomain is not supported by AWS Cloud Control which means it will not be available here.

Unfortunately it looks like we have a process to never unpublish a resource once it has been published. At some point in the past it looks like AWS switched the setting on that resource indicating that it had CCAPI support, we published a version with that resource, and then AWS switched the setting off again. In the past I've seen AWS do this by mistake or because there was an issue with the rollout and they had to rollback CCAPI support.

We should update the logic here to add the deprecation message for this resource

pulumi-aws-native/provider/pkg/schema/gen.go

Lines 924 to 926 in 447dd91

	if !ctx.isSupported {
	deprecationMessage = fmt.Sprintf("%s is not yet supported by AWS Cloud Control, so its creation will currently fail. Please use the classic AWS provider, if possible.", resourceTypeName)
	}