![]() ![]() So, when to use each service?Īs you can see from the above, Lightsail is the hold-you-by-hand platform for simple applications. But down the line, EC2 combined with either EKS, ECS or possibly Fargate will offer more versatility. Lightsail is the better option if you want to test out containers for the first time. When it comes to pricing, although Lightsail containers are more expensive per resource, there is an additional cost to EC2 container instances that comes ‘prepaid’ on Lightsail. When deploying containers with EC2, you would ordinarily need to use either ECS or EKS to manage those containers – which, again, offers more control for an expertise cost. True to trend, Docker images can be uploaded to Lightsail without too much input, making it relatively easy to deploy containers. ![]() ConclusionĪs we said to begin with, Lightsail comes with simpler, restricted versions of these capabilities baked in, EC2 doesn’t, but it can be configured to work with a greater variety of services. However, it won’t be able to access the throughputs of more powerful DBs that EC2 can be paired with. Lightsail can also work with multiple other AWS managed databases: RDS, Aurora and Dynamo DB. It automatically maintains a seven-day rolling back-up which can be further configured. Managed databaseĪgain, Lightsail comes with a limited managed database built in. The plus side of this is that the CDN can be configured to other AWS resources. When implementing a content delivery network with EC2, you’d need to use CloudFront or a similar CDN. Lightsail CDNs are in-built and cost-effective but limited to interacting with Lightsail instances.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |