aws marketplace error - Resource handler returned ...
# support
m
As soon as I launch vapi on aws marketplace it gives this error - Resource handler returned message: "vapi-artifacts already exists I dont have any bucket name vapi-artifacts on my AWS
v
It sounds frustrating to run into that error, especially when you don't see a "vapi-artifacts" bucket in your AWS account. While I don't have specific information about this error, you're not alone in encountering unexpected resource messages like this. If you have any other details or steps you've tried, feel free to share them!
It sounds frustrating to run into that error, especially when you don't see a "vapi-artifacts" bucket in your AWS account. While I don't have specific information about this error, you're not alone in encountering unexpected resource messages like this. If you have any other details or steps you've tried, feel free to share them!
k
The error occurs because the S3 bucket name vapi-artifacts is already taken globally; use a unique bucket name in your deployment to resolve it.
m
right s3 name should be globally unique its not account specific thanks for the help
okay now its deployed on my aws but how can I access the application?
@Shubham Bajaj
k
Hey checking if this is resolved/solved for you? if not, then could you record a loom video describing this error/behavior or inconsistency in the dashboard with the steps to reproduce it? That way, I can share this with my team, and we'll take a look. We'll even try to reproduce the same so we can fix it for you. Also, I'll request you to share your organization ID.
m
@Shubham Bajaj error is resolved but I want to know the app that I have deployed from aws marketplace how can I access the dashboard
k
Hey, Could you please schedule a brief call at your convenience so we can discuss this matter in detail? Kindly use the following link to book a suitable time: .
m
There is no availability in the calendar for this month and next.
k
Hey, it's not currently maintained, but we plan to work on it next quarter and improve the documentation. For now, we can't assist with the on-prem deployment.