5 out of 5.0, Reviewed Oct 17, 2016
Agile in nature. 3rd party company sometimes limited ability to work directly with AWS, so meeting our expectations were difficult at times.
invest in culture training.
Nothing at this time.
Nothing at this time.
Work directly with vendor and hire internal staff to support.
Support was above expectations. Risk and security measures were another area the vendor meet expecatoins.
5 out of 5.0, Reviewed Sep 28, 2016
This insight is related to the AWS Storage Gateway and our deployment. We learned as we built out. We are successfully utilizing for a subset of our file shares (25TB). The AWS Storage Gateway is viable for suitable workloads. We have had a very good experience working with AWS. Utilizing AWS IaaS and building out new solutions and offerings has allowed us to be more agile. AWS continuously improves product offerings. Adoption required some training and in some cases a more opened minded approach(internal people not AWS). We have now embraced AWS as our primary cloud provider and look to continue our expansion into the cloud.
Know the data, invest in tools to determine data type, age, usage. Utilize this data to ask folks to purge unnecessary files, understand workload needs, prompt conversation with file share owners. The AWS storage gateway works well when the above info is know. We use it for lower use file shares including archive data, document imaging, and standard files shares
Ability to place large chunks of data in a resilient location without having to expand our Backup or on Prem storage.
The performance is slightly slower than on prem. Not huge for basic office docs such as spreadsheets or word docs. For architectural drawings, some image intense and other dense docs you will notice slower speeds when downloading from S3.
Amazon updated the network driver offered summer 2015. This improved our performance from our previous POC (2013/14). Improving this offering continuously will help adoption.
We should have evaluated all files and use cases on shares migrated. We surveyed the marketplace and also invested in appliance based cloud storage gateways. The Amazon Storage gateway when first adopted could not support some workloads due to latency. examples are multi-user DB or spreadsheet type apps that lived on a file share. The poor architecture was an underlying topic but prior to the emigration, the apps worked on the on-premise file servers w/o problems.
Not as fast as on-prem file share solutions. Some limitations based on workload. Users wishing to deploy the AWS storage gateway or appliance based devices need to do some homework. Know your data, usage, size and types and determine how well they fit into the solution being considered. Prior to any migration, it is advisable to clean out obsolete and unnecessary files.
AWS was very responsive as it related to our needs, concerns and questions surrounding the Storage Gateway. We had several technical conversations both on-prem and via WebEx/phone. AWS has always been responsive and helpful.
The integration was a little more complex and included VSS. We spent more time than expected working the details out.
5 out of 5.0, Reviewed Sep 22, 2016
Great service, easy to use, great value.
Nothing to say here.
Maybe just have done it sooner.
Very responsive, easy to work with
3 out of 5.0, Reviewed Sep 20, 2016
Technically everything went very well but ones we came to the data security/privacy and more specific in a global setup , AWS was not willing to comply or make an effort to comply.
look very carefully into data privacy and IP
flexibility and ease of implementation
did not find really something that I really did not like
be more service orientated and try to find tailor-made solutions for potential bigger deals
when data privacy comes into play in a multi-regional environment a one size fits all approach is not viable
perfect and as a pure IaaS but tricky on the privacy part in a global environment
the few issues we had were solved adequately
First of implemenations were very fast and to the point
4 out of 5.0, Reviewed Sep 9, 2016
Strong, mature IaaS services, that we find reliable and predictable.
train internal teams. create clear messaging on AWS strategy
not enough cost savings up front.
train internal teams earlier.
Conduct internal staff training earlier and educate internal constituates
not as professional as other support organizations we have dealt with
5 out of 5.0, Reviewed Sep 6, 2016
For breadth of offering, nothing beats AWS. The experience was everything we expected.
The third party community for AWS is pretty uneven. The vetting of partners is not at the level I was used to in working with Microsoft technologies.
Just about everything you can think of is under one roof.
AWS could do more to make adoption of their solutions easier through partners that are better vetted or - even better - a more comprehensive professional services offering out of AWS itself.
AWS is working on its partner ecosystem, but it needs to do more.
If we started over, we might spend more time in training infrastructure staff and more explicitly organize teams around the effort from dev through I&O.
AWS has the broadest set of capabilities. I'm continually impressed by the rollout of new features and capabilities.
We have had limited cause to use service and support.
Depending on your project, getting up and running is very fast. Having a team focused on the activity that is sufficiently knowledgeable to work through roadblocks is the key ingredient.
4 out of 5.0, Reviewed Aug 25, 2016
The key positive outcome was the speed of delivery. The key negative performance has been that the capacity is occasionally not available.
Great support from account rep and technical support.
2 of 2 peer(s) found this review helpful.
4 out of 5.0, Reviewed Aug 18, 2016
Service management is more complex than it probably needs to be. While I understand that AWS is deploying new and updated services every other week and that they have a need to differentiate their offerings from other vendors, it really should be easier to identify and map AWS services against my requirements. Otherthan that (and getting a bit tired of cute/geeky service names), we're very happy with AWS for the use cases where it fits.
Spend the money for some consulting hours and training up-front. Just do it, you can thank me later.
Reliability, services, rapid deployment, overall ease of use.
Connectivity - to establish carrier-class circuits to AWS from our HQ costs enough (over $1M/yr) to immediately eliminate any Cost benefit from using AWS. They need to esablish POPs in a larger number of locations
Work with the Federal Government to provide TIC-equivalent functionality at a subset of their network border crossings.
We would start with bringing in an AWS consultant to guide us through the initial architecture planning. That would have saved us months of dead-ends and backtracking as we developed our architecture and implementation roadmap
AWS is constantly adding new services to their mix, including some service types that remain unique
They are on-the-spot any time we have a question or issue.
Once we got through the architecture and design phase (which took us longer than it should have, as we didn't make use of some of the consulting services available to us), the actual deployment was remarkably simple and trouble-free.
5 out of 5.0, Reviewed Aug 18, 2016
The experience with AWS was just amazing in terms of flexibility and capabilities to implement the desired architecture we promote at the business case
First understand the architecture that your are planning to deploy as Cloud Native and not try to lift and deploy as on-premise because there are many things that just doesn't work the same
Flexibility, scalability, ease of use
3rd Party integrator expertise
Improve the ELB capabilities by adding more layer 7 features
3rd party integrator we choose didn't have any security expertise making things harder internally with our security standards
AWS for me have everything we need, we have a two cloud providers strategy but for IaaS definetly AWS is the right solution
Great response for the AWS Team and the 3rd party vendors of the AWS MarketPlace in this case Fortinet
Integration with all of our systems was just great, we have like 15 integrations with 3rd party vendors all over the world and the AWS platform was just amazing
4 out of 5.0, Reviewed Aug 17, 2016
Support still needs to be improved
Please do a Sandbox deployment first and irone out all of the issues before production deployment
Cost and potential vendor lock-in
AWS does not have enterprise support experience, they should hire more professionals so they can support the enterprise customers better
TAGging and Financial Management is big part of success. We will make sure all of the processes and tools are in place before implementation
Support needs to be improved and more enterprise support is required