I am using fargate with elastic container service.
I see there are pricing of both x86 and arm for fargate so I assume that I would be able to choose between x86 and arm when I am creating a service with launch type fargate.
But I couldn't find an option to choose between x86 / arm when I am creating a service with launch type fargate. What I can see from the console is ability to select operating system (Linux, Window Sever 2019 Full and Window Server 2019 core)
How can I choose between launching fargate with x86 or arm?
There are screenshots of the ECS console on the official blog.
Announcing AWS Graviton2 Support for AWS Fargate – Get up to 40% Better Price-Performance for Your Serverless Containers | AWS News Blog
Related
Trying to figure out whether enabling FIPS 140-2 mode (crypto.fips_enabled = 1) on ECS Fargate Task in AWS GovCloud is at all possible?
The AWS ECS service shows up as a FedRAMP High compliant, so it would be easy to assume that all Fargate host machines are running in FIPS mode by default. However, when I ran a Fargate task and check for fips availability, it comes out as 0 (disabled).
Given that FIPS mode is a kernel feature, I am guessing is there still a way to turn it on? Or maybe there is a task config option that would let me run my container on a FIPS-enabled host?
Please advise.
From this long-languishing enhancement request, it does not appear possible now.
[ECS] [request]: FIPS support for containers running in Fargate #659
For multiple high-volume .NET web applications running on Windows and IIS, is there any advantage to changing to CloudFormation and ECS or even EKS instead of just using an AMI of an instance that already has auto-run scripts to update the codebase and configuration on launch, tied into an auto-scaling group behind an ELB?
Our usage is to scale web application servers based on load. Unless I have missed information or grossly misunderstood what has been read, it seems we might not gain anything by moving away from the pure AMI and auto-scaling group.
#sivart Are you using containers? ECS and EKS are container orchestrators. These will benefit you if you package your web applications as docker containers.
CloudFormation helps stand up/down your infrastructure stack using IaC (infrastructure as code) and will help you spin up new infrastructures within minutes without clicking through the AWS console. This will help, for example, when you want to produce production comparable stack for you performance/load/QA before going live. You can create a stack, perform tests and destroy it once happy. You can integrate CloudFormation with your CI/CD pipelines.
I have my docker image for microservice-x build on rpi
My dockerfile looks as below
FROM raspbian/stretch
....
This image runs on RPi .However if I wish to launch the docker image on AWS instance which Amazon Machine Image (AMI) type should I use ?
For AMI I will recommend using AWS ECS docker optimized AMI (AMR).
Amazon ECS-Optimized Amazon Linux 2 AMI (ARM)
Amazon EC2 Container Service makes it easy to manage containers at
scale by providing a centralized service that includes programmatic
access to the complete state of the containers and Amazon EC2
instances in the cluster, schedules containers in the proper location,
and uses familiar Amazon EC2 features like security groups, Amazon EBS
volumes, and IAM roles.
Amazon ECS-Optimized Amazon Linux 2 AMI (ARM)
For instance You can use Amazon EC2 A1 instances.
Amazon EC2 A1 instances deliver significant cost savings for scale-out
and Arm-based applications such as web servers, containerized
microservices, caching fleets, and distributed data stores that are
supported by the extensive Arm ecosystem. A1 instances are the first
EC2 instances powered by AWS Graviton Processors that feature 64-bit
Arm Neoverse cores and custom silicon designed by AWS.
You can find more in this article
Docker & ARM demonstrated the integration of ARM capabilities into
Docker Desktop Community for the first time. Docker & ARM unveiled
go-to-market strategy to accelerate Cloud, Edge & IoT Development.
These two companies have planned to streamline the app development
tools for cloud, edge, and internet of things environments built on
ARM platform. The tools include AWS EC2 A1 instances based on AWS’
Graviton Processors (which feature 64-bit Arm Neoverse cores). Docker
in collaboration with ARM will make new Docker-based solutions
available to the Arm ecosystem as an extension of Arm’s
server-tailored Neoverse platform, which they say will let developers
more easily leverage containers — both remote and on-premises which is
going to be pretty cool.
building-arm-based-docker-images-on-docker-desktop-made-possible-using-buildx
amazon-ec2-systems-manager-adds-raspbian-os-and-raspberry-pi-support
Forgot to notice that Ubuntu server 16.04 AMI type supports both X86 and ARM architectures
We've been toying with switching to cloud based desktops, specifically AWS Workspace. Is there support for Ubuntu desktops though? To this point I've only been able to generate Windows environments.
UPDATE: Amazon Workspaces now supports Amazon Linux 2, an offshoot of CentOS.
Update: Workspaces now have a linux option, in case anyone finds this.
AWS Workspaces only supports Windows at the moment.
From the product description:
Amazon WorkSpaces is a managed, secure cloud desktop service. You can use Amazon WorkSpaces to provision either Windows or Linux desktops
Amazon Workspaces now allows the use of Windows 7 and Windows 10, as well as Amazon Linux 2. There are options that are eligible for the Free Tier.
Descriptions of what software you can install are available here.
Can IBM Integration Bus((and /or Websphere message Broker) be implemeted on AWS ? Can my on-premise ESB be migrated to AWS Cloud ?
Thanks in Advance
AWS EC2 allows importing VMs into an AMI then you can start an EC2 instance using that image. If you are new to AWS you can check the link below
https://aws.amazon.com/ec2/vm-import/
However, you should be careful about IIB license and how many machines you can install it on before regesting the AMI in a launch configuration and create an autoscaling group and set a scaling policy that can start instances more that what you purchased.
That's very much possible. There are several possible approaches.
1. IIB on EC2
Installing and configuring IIB on an EC2 instance is very much similar to doing the same in on-premise servers. Only difference is that the physical server is in AWS Cloud. While this approach gives you maximum flexibility to design your architecture any way, it does not take advantage of the basic features of the cloud.
2. Quick Start
IIB is available for deployment under AWS Quick Start. You can read more about this here. This helps you get started quickly by setting up the entire environment in a few clicks. But, if you're planning to migrate your existing architecture to AWS, this may not suit you as the architecture is pre-defined with limited options for customization.
3. IIB on Containers
ACE 11 provides better support for containerization. You can read more about running IIB 10 on containers here and ACE 11 on containers here. After this, the containers can be deployed into fully managed containers such as AWS Elastic Container Service or your own container configuration such as Docker on EC2.
Yes of course, AWS provides the IAAS and you just install whatever you want inside. Make sure you open ports, use specific credentials for the instalation (dont use admin) and everything should work.
IBM also provides docker images of integration bus v10 and APP Connect Enterprise v11. This is true for all their integration tools, MQ, API Management and more.
Not restricted to AWS.