Akamai Connected Cloud (formerly Linode) accelerates innovation with scalable and accessible Linux cloud solutions and services. These products, services, and people give developers and enterprises the flexibility and support to build, deploy, secure, and scale applications more easily from cloud to edge on Akamai's distributed network.
N/A
AWS CloudFormation
Score 8.7 out of 10
N/A
AWS CloudFormation gives developers and systems administrators a way to create and manage a collection of related AWS resources, provisioning and updating them in a predictable fashion. Use AWS CloudFormation’s sample templates or create templates to describe the AWS resources, and any associated dependencies or runtime parameters, required to run an application. Users don’t need to figure out the order for provisioning AWS services or the subtleties of making those dependencies work.…
$0
Pricing
Akamai Connected Cloud
AWS CloudFormation
Editions & Modules
No answers on this topic
Free Tier - 1,000 Handler Operations per Month per Account
$0.00
Handler Operation
$0.0009
per handler operation
Offerings
Pricing Offerings
Akamai Connected Cloud
AWS CloudFormation
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
Yes
Yes
Entry-level Setup Fee
Optional
No setup fee
Additional Details
CPU, transfer, storage, and RAM are bundled into one price. Storage capacity can be increased with additional Block Storage or S3-compatible Object Storage. Instant Backups can be added with complete independence to the stack. Linode NodeBalancers ensure applications are available.
There is no additional charge for using AWS CloudFormation with resource providers in the following namespaces: AWS::*, Alexa::*, and Custom::*. In this case you pay for AWS resources (such as Amazon EC2 instances, Elastic Load Balancing load balancers, etc.) created using AWS CloudFormation as if you created them manually. You only pay for what you use, as you use it; there are no minimum fees and no required upfront commitments.
When you use resource providers with AWS CloudFormation outside the namespaces mentioned above, you incur charges per handler operation. Handler operations are create, update, delete, read, or list actions on a resource.
Information Technology Specialist, Digital Strategist
Chose Akamai Connected Cloud
There are a lot of very good cloud operations. Linode, for us represents a good offering. It offers a simple way to control infrastructure, without being overly simplified. For us, it was a good median giving us the flexibility to explore, experiment and still build for scale. …
Linode does a super job if you want to run a custom application or install your own Linux software. We installed WordPress and a radio station. They both ran smoothly. It is easy to upgrade the CPU and RAM without destroying your server. Hard drive space could have more options. We could also monitor the speed and storage.
AWS CloudFormation is well suited for scenarios where all of your resources need to be provisioned on AWS but it is not suited for hybrid cloud deployments. It's very easy for someone new to learn. The level of customization offered as part of the template specifically for AWS services is great. There is also a UI tool where we can drag and drop the services we want and it generates an yaml file which is very easy to use. The visibility of stacks and its resources and one place where we can track and identify the issues in deployment is great.
I've been with them a long time. They provide me with the capabilities I need coupled with knowledgeable support that's not pay-for-extra. However, if I move to a non-Linux OS, the level of support by necessity will drop off. I can still ask questions about the infrastructure but I my ability to ask about OS features will decrease.
It's pretty easy for me, but I preferred their old interface before it was called 'cloud' (not a computer science term.) The new interface looks easier but I had to ask for help for things I used to be able to find myself. If someone was new to it--without having used their old interface--it might be easier for them than it originally was for me.
There is very little planned downtime. Whenever planned downtime is necessary I'm always given lots of advanced notice and an explanation that I can pass along to my users that they'll understand. I really appreciate that Linode appreciates my commitment to reliable service to my users. It shows that they believe they've been successful when I'm successful.
Linode is an infrastructure provider issues related to performance are really on me. Linode provides a capable infrastructure and allows me to tailor performance of the services I provide to my customers to my specific situation. Linode allows me to implement "tweaks" that, from experience, I know will do the job with little risk without a whole bunch of static from idiot support 'droids who just get in the way ("this isn't supported at the present time").
I've asked many levels of questions. From noob how-to-setup-my-server questions to ask for more IP addresses and help in getting them set up. They always respond swiftly and relevantly. Compared to other providers, you have to bounce a couple of times with different levels of support actually to land on someone who _understands_ your problem. Other providers, even if they are actively having downtime, their support will respond hours later. Not Linode/Akamai. They are always there for you. They promise this, and they do deliver.
We got kick started with an initial walkthrough along with some free credits. The initial walkthrough helped us to understand Linode's ecosystem and start our hands on with Linode. We tried out some apps from Marketplace initially with the free credits, which not only helped us understand Linode better, but also those apps. We had implemented many such apps to our customers with Linode
We're a small organization. The implementation of our Linode solution was trivial. Once I justified a cloud server to my bosses over a co-location -- the co-lo wasn't as fast as our linode server in load tests -- it was a matter of moving one Linux implementation to another. Trivial.
We switched to Linode from Namecheap due to poor uptime, and never had any issues with stability ever again after switching. We also cut our costs in half by switching. We compared Linode to DigitalOcean and Vultr, with the primary factor that caused us to go with Linode initially being their documentation. After using Linode for 3 years, their amazing support is another reason why we wouldn't consider anyone else at this point.
We didn't look into anything else as Cloudformation was "built-in" for AWS, it just kind of made sense to go with that. Terraform was something that we briefly looked into Terraform but decides to stick with Cloudformation because our task was relatively "simple". Apparently if it's a bit more complex, Terraform might be the way to go.
Although I use only a fraction of their product offerings, the total set makes scalability an easy goal to shoot for. As I said, I have a few customers that use the services my Linode provides...and I like it that way. However, should I need to scale up, I can...without incurring any more cost than I need to.