Deep dive on Microservices and ECS - AWS Summit Tel Aviv 2017
•
6 likes•1,530 views
The document provides an overview of a deep dive session on microservices and Amazon EC2 Container Service (ECS). It begins with definitions of microservices and comparisons to monolithic architectures. It then covers key aspects of ECS like orchestration, integration with AWS services, task placement strategies and constraints. The document discusses using the AWS CLI to manage the container lifecycle from cluster creation to task deployment. It ends with a customer use case presentation from Cloudlock on running their microservices on ECS.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Deep dive on Microservices and ECS - AWS Summit Tel Aviv 2017
Similar to Deep dive on Microservices and ECS - AWS Summit Tel Aviv 2017 (20)
More from Amazon Web Services
More from Amazon Web Services (20)
Deep dive on Microservices and ECS - AWS Summit Tel Aviv 2017
- 2. Agenda • What are microservices? • Lightning ECS overview • Let’s get feature specific • Flexible orchestration and ECS • Container lifecycle with aws-cli • Customer use case: Cloudlock
- 12. Why ECS? • Fully managed • Shared state optimistic scheduling • Native Cloudwatch integration for monitoring and logging • Native integration with Code* services for CI/CD
- 13. Choose your own Scheduler Batch Jobs • ECS task scheduler • Run tasks once • Batch jobs • RunTask (random) StartTask (placed) Long-Running Apps ECS service scheduler Health management Scale-up and scale-down AZ aware Grouped containers
- 15. Amazon ECS Task Placement • A task placement strategy is an algorithm for selecting instances for task placement, or tasks for termination • A task placement constraint is a rule taken into consideration during task placement • Strategies and constraints can be used together
- 16. How can strategies and policies be used? Name Example AMI ID attribute:ecs.ami-id == ami-eca289fb Availability Zone attribute:ecs.availability-zone == us-east-1a Instance Type attribute:ecs.instance-type == t2.small Distinct Instances type=“distinctInstances” Custom attribute:stack == prod
- 23. Spoiler alert: I like the console Why the console? • JSON • Quicker to test and get started • Visual feedback • JSON
- 24. But the console is not for everyone If you’re customizing or automating, the CLI might be a better choice. Enter ecs-cli: • Open source • Takes Docker compose files • Used to manage container lifecycles from start to finish on ECS I <3 CLIs
- 26. First stop: creating a cluster $ aws ecs create-cluster --cluster-name ”summit" Should return something like: { "cluster": { "status": "ACTIVE", "clusterName": ”summit", "registeredContainerInstancesCount": 0, "pendingTasksCount": 0, "runningTasksCount": 0, "activeServicesCount": 0, } }
- 27. Then, create a task $ aws ecs register-task-definition --cli-input-json file://path/summit.json You can also use a JSON string: $ aws ecs register-task-definition --family summit -- container-definitions "[{"name":”summit","image":”alpine","cpu":10, "command":["sleep","360"],"memory":10,"essential ":true}]"
- 28. Next, use our task to create a service $ aws ecs create-service --service-name summit--task- definition summit --desired-count 2 You can add more parameters here, such as placement strategy. You can also register your new service with an ELB/ALB.
- 29. Summits are pretty popular. Let’s scale up. $ aws ecs update-service --service summit --desired- count 4 We could use this same command to scale down (which we’ll look at next), but also to update the task definition. Effectively, deploy a new version!
- 30. We don’t want to waste resources though, so let’s scale back down $ aws ecs update-service --service my-http-service -- desired-count 2 In a production environment, this is something we might want to handle in response to other events: autoscaling!
- 31. We can also query state $ aws ecs describe-services --service summit This returns A TON of information about our service: most importantly, it shows us our current deployment, and what events are happening in our cluster: "events": [ { "message": "(service summit) has reached a steady state."
- 32. Bye Tel Aviv! $ aws ecs delete-cluster --cluster summit Important to note that we have to scale our service down to 0, and remove the service before running this: just in case! $ aws ecs update-service --service summit --desired- count 0 $ aws ecs delete-service --service summit
- 37. 37© 2016 Cisco and/or its affiliates. All rights reserved. Cisco Confidential By 2018, Gartner estimates: 25% of corporate data traffic will bypass perimeter security.
- 38. Protect the usage of business apps in the cloud SaaS Protect the usage of critical infrastructure in the cloud IaaS/ PaaS
- 41. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Confidential /cyber run=RunAssessment org_name=cloudlock.com API Gateway Lambda EMR Model Detection Model Training Generate Worksheet #assessments https://xxx.cloudlock.com/<customer>/assessment.xls EMR step EMR step EMR step Cyber analyst workflow
- 45. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 3. Ability to run long-running recurring tasks CloudWatch event CloudWatch rule ES curation Restore DB dump RunTas k Lambda Lambda ECSES
- 53. Sr. Devops engineer Big data engineer Sr. front end engineer Cybersecurity analyst Data scientist Sr. software engineer For more information about the positions: jobs.cisco.com To apply: sapir@cloudlock.com
- 54. Questions and answers www.cloudlock.com | info@cloudlock.com | 781.998.4332
- 55. Thank you!