- Newest
- Most votes
- Most comments
I'm not able to find a way in the console to check the user_id but one way to get this information quickly is through CLI.
https://docs.aws.amazon.com/cli/latest/reference/connect/list-users.html
To resolve the InvalidParameterException error for the user_id field when creating an AWS Connect Quick Connect resource via Terraform, you need to provide the correct user identifier. Here's how you can find and use the correct user ID:
-
The user ID for Amazon Connect is not the same as the IAM user ID or ARN. It's a unique identifier specific to Amazon Connect.
-
To find the user ID in the Amazon Connect console:
- Log in to the AWS Management Console
- Navigate to the Amazon Connect service
- Select your instance
- Go to "Users, Security, Identity" in the left navigation pane
- Click on "User management"
- Find the user you want to create a Quick Connect for
- The user ID should be visible in the user details or when you edit the user
-
If you can't see the user ID directly in the console, you may need to use the AWS CLI or API to retrieve it. You can use the
list-users
command in the AWS CLI for Amazon Connect: -> aws connect list-users --instance-id your-instance-id Replaceyour-instance-id
with your actual Amazon Connect instance ID. -
Once you have the correct user ID, update your Terraform configuration: -> resource "aws_connect_quick_connect" "example" { instance_id = "your-instance-id" name = "User Quick Connect" description = "Quick connect for a user"
quick_connect_config { quick_connect_type = "USER" user_config { user_id = "correct-user-id-from-connect" contact_flow_id = "contact-flow-id" } } }
-
Ensure that you're using the latest version of the AWS provider for Terraform, as older versions might have issues with certain Amazon Connect resources.
-
Remember to apply the principle of least privilege when setting up your Terraform AWS provider. Ensure your credentials have the necessary permissions to create and manage Quick Connect resources in Amazon Connect.
-
Always test your Terraform configuration in a non-production environment before applying it to your production instance.
If you continue to experience issues, I recommend reviewing the Amazon Connect API documentation for the most up-to-date information on resource identifiers and consulting with AWS support for personalized assistance with your specific use case.
Relevant content
- asked 20 days ago
- asked 3 years ago
- asked 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 22 days ago
What is the format of the user I’d that you are using ?