ECS: Connecting ECS buckets with WINSCP[1]

           

   Article Number:     529892                                   Article Version: 3     Article Type:    How To 
   

 


Product:

 

ECS Appliance Hardware

 

Instructions:

 

 

   

      This setup must be done with a load balancer connected to the ECS, this does not work without one. You will need to create a DNS record locally.  Any special characters in bucket names or namespaces do not work, WINSCP throws an error about the name being invalid (a.g. brian's_bucket).     
     
      User-added image     
     
      Use the baseURL in ECS GUI to setup the hostname for WINSCP use. The name is an identifier and can be anything. The baseURL must match later setup and can look something like this <bo.emc.com>. Do not use anything already taken within the DNS records as this needs to be setup on DNS later.     
     
      To setup a DNS record create the following A and CNAME records using formatting examples:     
     
      Example of an A record pointing to the load balancer IP:     
      bo.emc.com     
     
      Below is the wild card CNAME record example pointing to the A Name record above:     
      *.bo.emc.com      
     
      Below is an example of an ECS user information where you can copy the secret key to populate the the WINSCP configuration to access the bucket:     
      User-added image     
     
      To setup WINSCP using Amazon S3 protocol. The access key ID and Secret access key are what gives you access to buckets and namespaces, the Access key ID is the user the bucket is assigned to and Secret access key is the S3 object access key (in picture below just check show secret key). Whoever you put in your Access key ID will mean you can only see their buckets. Use your baseURL as the hostname and put the namespace for any buckets you are trying to access before such as <namespace.baseURL>.     
     
      User-added image   
                                                                                                                             

 

 

Notes:

 

 

There was found to be a way to access buckets the user was given access to as well using <bucket.namespace.baseURL>. This will show you that bucket and it's contents as long as the user has been granted access to the bucket.