# Vault Credential store brokering with Boundary

**URL:** <https://discuss.hashicorp.com/t/vault-credential-store-brokering-with-boundary/39646>\
**Category:** Vault\
**Tags:** boundary\
**Created:** [May 18, 2022, 9:23am UTC](https://discuss.hashicorp.com/t/vault-credential-store-brokering-with-boundary/39646 "2022-05-18T09:23:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![akhila98](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/akhila98/32/28107_2.png) [@akhila98](https://discuss.hashicorp.com/u/akhila98)\
**Post date:** [May 18, 2022, 9:23am UTC](https://discuss.hashicorp.com/t/vault-credential-store-brokering-with-boundary/39646/1 "2022-05-18T09:23:34Z")

</div>

Integrating vault with boundary credential store , inorder to login into aws ec2 instance,  
but have to statically provide the credential inorder to login into ec2.

./boundary connect ssh -target-id ttcp\_1234567890 -addr=http://XXXXXXXXXXX -username hello  
Credentials:  
Credential Source ID: clvlt\_jnEOdYQyew  
Credential Source Name: new ec2  
Credential Store ID: csvlt\_4lWBv8Wke7  
Credential Store Type: vault  
Secret:  
null  
hello@hst\_1234567890’s password:

It is not taking the vault secret created in vault ,basically which it should  
So is there any alternative to login into AWS resources through credential provided in vault .  
the documentation has the analyst role able to connect postgres db without providing the credential.  
boundary connect postgres -target-id ttcp\_1r9XGCXdwE -dbname northwind

So is there the similar approach for logging into ec2 instance.