[Enhancement]: Provide a way to retrieve the id of the default Sagemaker Service Catalog portfolio

[dorranh]

Description

As a user of Sagemaker, I would like to be able to provision new Sagemaker Domains via Terraform which use a custom default execution role that has access to the default service catalog portfolio which AWS provides.

While I can enable this portfolio with the aws_sagemaker_servicecatalog_portfolio_status resource, it does not return the portfolio ID required to grant my custom IAM role access to the portfolio via the aws_servicecatalog_principal_portfolio_association resource (see https://github.com/hashicorp/terraform-provider-aws/issues/28348).

This requires us to introduce manual steps in our deployment process or use workarounds like the one described in https://github.com/hashicorp/terraform-provider-aws/issues/28348.

Allowing the aws_servicecatalog_portfolio resource to query by name rather than an id as previously suggested in https://github.com/hashicorp/terraform-provider-aws/issues/20719 would be one fix for this, though there may also be other solutions to the above problem.

Affected Resource(s) and/or Data Source(s)

• aws_servicecatalog_portfolio
• aws_servicecatalog_principal_portfolio_association
• aws_sagemaker_servicecatalog_portfolio_status

Potential Terraform Configuration

No response

References

• https://github.com/hashicorp/terraform-provider-aws/issues/28348
• https://github.com/hashicorp/terraform-provider-aws/issues/20719

Would you like to implement a fix?

None

[github-actions[bot]]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.