AWS Connect dynamic attributes has an extra dot . added

Question

Hi,
I'm using the start_outbound_voice_contact in lambda to start a contact flow.
The lambda is passing an attribute of S3 path/ folder name where a voice recording is stored.
I want to use this path to play the recording in a Get Customer Input block.

This is what I have configured in the Set Contact Attributes block:
User defined : Namespace
Value: FileName
Set dynamically
Namespace: External 
Value: $.Attributes.FileName

If I change the attribute to "$.External.FileName", it doesn't work.

When I look at the Cloudwatch logs, I see the parameter as below
"Parameters": {
        "Value": "..Provide+options+if+no+agent+is+available.wav",
        "Key": "FileName"
    }

Below is what I have configured in the Get Customer Input block:
Specify an audio file from an S3 bucket
Set manually
S3 file path: https://.s3.amazonaws.com/prompts-audiofiles/$['Attributes']['FileName']

In the Cloudwatch logs, the S3 path has a . included before the file name and hence the prompt is failing:

"Parameters": {
        "PromptLocation": "https://.s3.amazonaws.com/prompts-audiofiles/.Provide+options+if+no+agent+is+available.wav",
        "Timeout": "5000",
        "PromptSource": "S3",
        "MaxDigits": "1"
    }

Can anyone help identify and fix this issue of an extra dot . added for the parameter?

Thanks

Answer

Oh! Since the S3Path attribute is coming from the lambda function, I was using the Namespace as External.
Based on Kike's response, it also worked when I used User Defined.

So now with the value as "S3Path" it finally worked.

Thank you so much for your help @Kike and @lukwarne!

Answer

Hi
When you call [start_outbound_voice_contact](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/connect/client/start_outbound_voice_contact.html),  Are you passing your attributes to Attributes param?
```python
    Attributes={
        's3url': 'http://mybucket/mypath/filename.wav'
    },
```
Later in the contact flow you can reference this value using $.Attributes.s3url . No need to setContactAttribute inside the Contact Flow

The second part, I recommend to include the full path in the Attribute and then using **Set Dynamically** -> **User Defined** -> **$.S3url** (or $.Attributes.s3url) in GetCustomerInput block
Example:
![](/media/postImages/original/IMnDcrfvvaQnuHjyYoBjLHaQ)

Notes: 
- It has to be dynamically because with this connect will render de value of $.s3url
- also the way to access nested values is using "." (like $.Attributes.filename)

AWS Connect dynamic attributes has an extra dot . added

Relevant content