When we opened a ticket for AWS Storage Gateway, the support team was responsive but could not resolve the issue. When we sent a file from MOVEit to AWS Storage Gateway, it sent the file twice. We were not able to figure out why it was doing it. In the AWS S3 bucket, you will find an option called versioning. If a file is sent multiple times, the versioning feature will increase the version one by one. For example, if I send the same file thrice, it will have version one, version two, and the original file. Likewise, they have the versioning. Whenever we send file one, the files are getting duplicated. When we opened a ticket, even the AWS team could not figure it out. They just told us the configuration might be wrong on the AWS Storage Gateway side, and we need to look at it. After that, we also did not follow up because the destination team changed the architecture on their end. Instead of running the Lambda function immediately when the file arrived, they added a sleep time of four to five minutes and then started processing the file.
The solution's interface could be easier to use. Presently, it is challenging to understand identity access management features. Also, its support team could respond faster.
Since the configuration and maintenance is done by the client most of the time, it's hard to know if there are any issues with the solution. I haven't heard of any. We've had issues with bandwidth in the past, and we don't know where the bottlenecks are. We're not sure if it's on the AWS side or with the clients or the configuration in between. There's no visibility. The solution should also be more clear on the pricing. It can be misleading because it looks so low at first but then can get to be quite expensive. It might be better if they charged upfront.
AWS Storage Gateway provides hybrid cloud storage services that give users access to unlimited cloud storage. As a part of the Amazon Web Services, one of the leading on-demand cloud computing platforms, the AWS Storage Gateway allows you to use the AWS storage without the need to rewrite your applications. It does this by providing protocols like iSCSI, NFS, and SMB. It works by caching frequently accessed data on premises and simultaneously storing data on AWS, as well as optimizing data...
When we opened a ticket for AWS Storage Gateway, the support team was responsive but could not resolve the issue. When we sent a file from MOVEit to AWS Storage Gateway, it sent the file twice. We were not able to figure out why it was doing it. In the AWS S3 bucket, you will find an option called versioning. If a file is sent multiple times, the versioning feature will increase the version one by one. For example, if I send the same file thrice, it will have version one, version two, and the original file. Likewise, they have the versioning. Whenever we send file one, the files are getting duplicated. When we opened a ticket, even the AWS team could not figure it out. They just told us the configuration might be wrong on the AWS Storage Gateway side, and we need to look at it. After that, we also did not follow up because the destination team changed the architecture on their end. Instead of running the Lambda function immediately when the file arrived, they added a sleep time of four to five minutes and then started processing the file.
A data pipeline tool would be more beneficial for data authentication and DataOps.
The solution's setup is not easy and takes time to complete.
The solution's interface could be easier to use. Presently, it is challenging to understand identity access management features. Also, its support team could respond faster.
It would be better for us if they improved their integration capability.
The security could improve in the solution.
Since the configuration and maintenance is done by the client most of the time, it's hard to know if there are any issues with the solution. I haven't heard of any. We've had issues with bandwidth in the past, and we don't know where the bottlenecks are. We're not sure if it's on the AWS side or with the clients or the configuration in between. There's no visibility. The solution should also be more clear on the pricing. It can be misleading because it looks so low at first but then can get to be quite expensive. It might be better if they charged upfront.
The product could be improved by making the setup process simpler.
Although we have not used this application long, I am not sure, in its current configuration, that we could scale this solution to meet our needs.