#AWS

Hey folks,

I am new to IRIS and cloud platforms. I've done the InterSystems IRIS Experience on the learning site and read a lot of the online documentation. What I am unable to figure out is which type of package or option you will use on the cloud provider.

AWS for example, has AWS EC2, Elastic Beanstalk and some other products geared towards Docker containers.
Azure has Kubernetes and some other options.

Table of Contents

1. Hello Newman
   • Situation
   • Task
   • Action
   • Result
2. Built With
3. Getting Started

Being interoperable is more and more important nowadays. InterSystems IRIS 2022.1 comes with a new messaging API to communicate with event streaming platforms like Kafka, AWS SQS/SNS, JMS and RabbitMQ.

This article shows how you can connect to Kafka and AWS SQS easily.
We start with a brief discussion of the basic concepts and terms of event streaming platforms.

Breaking news!

InterSystems just announced the availability of the InterSystems IRIS for Health™ Data Platform across the Amazon Web Services, Google Cloud, and Microsoft Azure marketplaces.

With access to InterSystems unified data platform on all three major cloud providers, developers and customers have flexibility to rapidly build and scale the digital applications driving the future of care on the platform of their choice.

To learn more please follow this link.

Hey Developers,

We're pleased to invite you to join the next InterSystems IRIS 2020.1 Tech Talk: Using InterSystems Managed FHIR Service in the AWS Cloud on June 30 at 10:00 AM EDT!

In this InterSystems IRIS 2020.1 Tech Talk, we’ll focus on using InterSystems Managed FHIR Service in the AWS Cloud. We’ll start with an overview of FHIR, which stands for Fast Healthcare Interoperability Resources, and is a next generation standards framework for working with healthcare data.

You'll learn how to:

• provision the InterSystems IRIS FHIR server in the cloud;
• integrate your own data with the FHIR server;
• use SMART on FHIR applications and enterprise identity, such as Active Directory, with the FHIR server.

We will discuss an API-first development approach using the InterSystems IRIS FHIR server. Plus, we’ll cover the scalability, availability, security, regulatory, and compliance requirements that using InterSystems FHIR as a managed service in the AWS Cloud can help you address.

Hi colleagues!

Often when we collaborate to someone's repo in GitHub we do the following cycle:

Fork-Clone-Change-Commit-Push-Pull-Request-Merge to the original repo.

This is all great and works fine!

And if we want to make a second collaboration right after the merge you need to perform "Fetch upstream" to your forked repo first to "ingest" your own Pull-request in the original repo.

Geeky git-professionals do it with ease but this was always a headache for me so I usually simply deleted the fork and created a new one.

And today I figured that Github added a new UI feature that I can easily fetch-upstream for my fork with the original one and make it up to date and capable for pull-requests.

Here is where the button is:

This is a relief! )

Wanted to share this relief and productivity tip with you!

Bring more collaborations to Github repos!

And speaking of PR - I just made a PR with docker to Google Cloud Run deployment for the FHIRaaS demo made by @Anton Umnikov for the current FHIR Contest! Looking for more of your contributions!

Hi, someone have connected Iris to a Bucket ? like aws, huawei, etc.

I try to use private Bucket as storage for files, and Iris as database & API interface to manage this files, but al SDKs are in another languages, no one have founded on COS.

I have tested some examples, but with bad results

Hi Community,

New video is already on InterSystems Developers YouTube:

⏯ Embedded Python with Interoperability

https://www.youtube.com/embed/b6Fbg0JDmPA
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

I installed a community version of Intersystems IRIS in a Large AWS EC2 instance to do some testing. I installed SAM and when I try to "Add a new cluster" I receive the following: "ERROR #5005: Cannot open file '/config/prometheus/isc_tmp_yml_file.yml'"

Screen shot included here: https://share.getcloudapp.com/RBu4K5yv

Folks,

I am looking to migrate a few legacy debt collection applications built using InterSystems Cache to AWS. Does anyone here have any experience, ideas and best practices on migrating Cache products to the public cloud?

Regards

Sudarshan

+1-917-685-3551

Hi Community,

The new video from Global Summit 2019 is already on InterSystems Developers YouTube:

⏯ Automated InterSystems IRIS Cloud Scaling

https://www.youtube.com/embed/4O2Nr5f_0vo
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

Hi everyone, I'll be honest with you I don't have much idea how to do this, but I was asked to install IRIS for Health on an AWS ubuntu machine(ssh -i "teleker-net.pem" ubuntu@xx.xxx.xx.xxx(no I will put the real number)). My boss has sent me the .key and .pem files that I am supposed to need for the installation.

Hi Community,

We'll look at moving InterSystems workload to the public cloud, then take a deep dive into the current architectures on the InterSystems cloud platform:

⏯ InterSystems Solutions in AWS

https://www.youtube.com/embed/N8MfDLngcSc
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

This is a remote position for a US Citizen who has significant MUMPS background AND has experience at a deep level with Java, and AWS Services.

The location is in Kirkland Washington, however, obviously during the COVID we will be doing remote work. Our hope is some is willing to relocated to the Seattle Region after we open up again.