El adaptador CTI de Amazon Connect para Salesforce ahora ofrece configuración guiada

El adaptador de integración de telefonía informática (CTI) de Amazon Connect para Salesforce ahora brinda una configuración guiada mejorada tras instalar el paquete de AppExchange del adaptador CTI. Los clientes que se beneficien de la configuración guiada acelerarán el tiempo de implementación y realizarán la primera llamada en cuestión de minutos. Además, cada paso de la guía contará con enlaces de documentación contextual para obtener información adicional sobre la configuración. La configuración guiada validará los ajustes de configuración para reducir el riesgo de errores de configuración al instalar el adaptador CTI en Salesforce Lightning o Classic.

AWS App2Container ahora es compatible con la inclusión en contenedores de aplicaciones de Windows multicapa complejas

AWS App2Container (A2C) ahora es compatible con la inclusión en contenedores y la implementación de aplicaciones de Windows multicapa complejas. Esto se suma a la compatibilidad de A2C con aplicaciones ASP.NET. Gracias a esta publicación, los clientes pueden a partir de ahora incluir en contenedores los siguientes tipos de aplicaciones de Windows: a) Aplicaciones de Windows multicapa (aplicaciones IIS o servicios de Windows que se ejecutan en arquitectura multicapa en contenedores por separado, implementadas en clústeres ECS o EKS, y crear recursos de red para la comunicación entre aplicaciones implementadas); b) Aplicaciones que colaboran en el mismo anfitrión (varias aplicaciones que se ejecutan en el mismo anfitrión en contenedores en un único contenedor). Además, esta publicación también permite a los clientes incluir en contenedores un servicio de Windows en un contenedor independiente. Los clientes pueden seguir implementando estas aplicaciones multicapa incluidas en contenedores en sus plataformas de contenedores preferidas, ECS o EKS, mediante A2C.

Los alias de puntos de acceso de Amazon S3 permiten a cualquier aplicación que requiera un nombre de bucket de S3 utilizar con facilidad un punto de acceso

Los alias de puntos de acceso de Amazon S3 permiten a cualquier aplicación que requiera un nombre de bucket de S3 utilizar con facilidad un punto de acceso. Gracias a los puntos de acceso de S3, puede crear cientos de políticas únicas para controlar fácilmente el acceso a conjuntos de datos compartidos. Ahora, puede utilizar alias de puntos de acceso de S3 en cualquier lugar en el que utilice nombres de bucket de S3 para acceder a datos en S3. Gracias a esta actualización, puede utilizar alias de puntos de acceso de S3 con servicios de AWS, incluidos Amazon EMR, Amazon Storage Gateway y Amazon Athena, paquetes de código abierto, como Apache Spark y Apache Hive, y soluciones de la red de socios de Amazon (APN) sin realizar cambios en el código y sin costo adicional.

Amazon Kendra lanza el conector para WorkDocs

Amazon Kendra es un servicio de búsqueda inteligente con tecnología de machine learning que permite a las organizaciones proporcionar información relevante a los clientes y empleados cuando la necesitan. A partir de hoy, los clientes de AWS podrán indexar y buscar documentos en Amazon WorkDocs, un servicio completamente administrado que permite crear, almacenar y compartir contenido de forma segura.

Amazon QLDB ya admite claves de KMS administradas por el cliente

Amazon Quantum Ledger Database (QLDB) ya admite claves de AWS Key Management Service (AWS KMS) para cifrar datos en reposo. A partir de hoy, los clientes podrán cifrar libros mayores de QLDB mediante claves que hayan creado ellos mismos y que controlen exclusivamente desde su cuenta, con políticas para claves, auditorías y ciclos de vida de las claves que pueden administrar de forma autónoma. Gracias a esta característica, los clientes de QLDB pueden cumplir con los estándares de seguridad de datos que requieran que el cifrado utilice claves administradas de forma autónoma. Los nuevos libros mayores compatibles con claves de KMS administradas por el cliente se pueden crear de forma sencilla con un solo clic en la consola de administración de AWS, en AWS Command Line Interface (AWS CLI) o mediante una llamada a la API en AWS CloudFormation. 

AWS Glue DataBrew agrega la capacidad de especificar las estadísticas relativas a la calidad de los datos que se generan para sus conjuntos de datos

Ahora, AWS Glue DataBrew permite que los clientes especifiquen cuáles son las estadísticas relativas a la calidad de los datos que se generarán de forma automática para los conjuntos de datos cuando se ejecute un trabajo del perfil. De este modo, los usuarios podrán personalizar algunas estadísticas del perfil de datos, como por ejemplo, para determinar valores duplicados, correlaciones y valores atípicos en función de la naturaleza y el tamaño de los conjuntos de datos; asimismo, podrán crear resúmenes personalizados para los perfiles de datos usando únicamente las estadísticas que cumplen con sus requisitos.

Amazon Aurora PostgreSQL admite la extensión pg_bigm para una búsqueda más rápida de texto completo en las regiones de AWS GovCloud (EE. UU.)

La edición de Amazon Aurora compatible con PostgreSQL incorpora compatibilidad con la extensión pg_bigm en las regiones de AWS GovCloud (EE. UU.). Dicha extensión agrega capacidad de búsqueda de texto completo en PostgreSQL. Esta extensión permite al usuario crear un índice de *dos gramos* (bigrama) para realizar búsquedas de texto completo más rápidas.

Amazon Aurora es compatible con las versiones 12.6, 11.11, 10.16 y 9.6.21 de PostgreSQL en las regiones AWS GovCloud (EE. UU.)

Tras el anuncio de las actualizaciones de la base de datos PostgreSQL por parte de la comunidad de código abierto, hemos actualizado la edición compatible con PostgreSQL de Amazon Aurora para que admita las versiones de 12.6, 11.11, 10.16 y 9.6.21 de PostgreSQL en las regiones AWS GovCloud (EE. UU.). Estas versiones contienen correcciones de errores y mejoras de la comunidad de PostgreSQL. Como recordatorio, Amazon Aurora PostgreSQL 9.6 llegará al final de su ciclo de vida el 31 de enero de 2022.

Simplifique la configuración de CI/CD para aplicaciones sin servidor y su sistema CI/CD favorito – Versión preliminar pública

Ahora puede crear canalizaciones seguras de integración e implementación continuas (CI/CD) que sigan las prácticas recomendadas de su organización con una nueva capacidad de configuración de canalizaciones para aplicaciones sin servidor. AWS Serverless Application Model Pipelines (AWS SAM Pipelines) es una nueva característica de la CLI de AWS SAM que permite obtener beneficios de CI/CD en cuestión de minutos, como acelerar la frecuencia de las implementaciones, reducir el plazo de entrega de los cambios y disminuir los errores de implementación. AWS SAM Pipelines incluye un conjunto de plantillas de canalización predeterminadas para sistemas CI/CD populares, como CloudBees CI/Jenkins, GitLab CI/CD, GitHubActions y AWS CodeBuild/CodePipeline, que siguen las prácticas recomendadas de implementación de AWS. La CLI de AWS SAM es una herramienta para desarrolladores que facilita la creación, la realización de pruebas locales, el empaquetado y la implementación de aplicaciones sin servidor.

#IamaGDE: Evgeny Kot

Welcome to #IamaGDE – a series of spotlights presenting Google Developer Experts (GDEs) from across the globe. Discover their stories, passions, and highlights of their community work.

His first computer was a black market device created from parts of a Nintendo gaming system. When he was 15 he got his first real computer but with no tech support available he had to learn everything himself. Soon after he earned his first 100 bucks by helping update an interactive map on his friend’s website. Today, he is an extremely active developer in Russia and internationally, an organizer of one of biggest conferences in Russia, such as DartUp (for Dart and Flutter), HolyJS (for Web), a YouTube podcaster producing Pyjamatalks series and a fierce DEI and women in tech advocate, supporting a number of initiatives including the Russian edition of Google’s Women Developer Academy.

Meet Evgeny Kot, Google Developer Expert in Web, Dart and Flutter.

GDE Evgeny Kot

GDE Evgeny Kot

THE EARLY DAYS

During his school days, Evgeny had two big passions – love for music and love for computers. He enjoyed playing music a lot but has eventually made a decision to do programming full time. The beginnings weren’t always easy. In his first job, he had plenty of ideas for optimization and process improvement. He asked his boss for permission to rewrite the company’s entire software from C to C++. Granted an approval he attempted this challenge but things didn’t go as planned and the project failed completely. As he admitted himself, sometimes learning from mistakes can be a more valuable experience than succeeding at something the first time. Fortunately his boss was also of a similar opinion!

“My first manager became a true mentor for me. He taught me a lot.”

THE RUSSIAN DEV MARKET

The Russian dev market is enormous and extremely saturated. There are many Russian developers who don’t see the need of working in English or another foreign language because the core of their work is with and for Russian companies. Evgeny didn’t want to do that – he wanted to get exposed to the international market, understand how things are getting done elsewhere, learn other things from developers from different backgrounds. His first international experience was working at Dell.

I enjoyed it a lot and learned a ton. I was lucky to step outside of the Russian bubble and see how other teams work internationally.

This experience has eventually brought him to a front end developer role at Wrike. In fact, he is still with the company, currently working as Director of Development in the Prague office.

The one thing that he enjoys most about it is the independence that it gives him. It was only during his time at Wrike, when Evgeny started working with Dart.

Image of Evgeny at Saint Teamlead Conference 2018

BEGINNINGS OF DART

When Evgeny joined Wrike, there were only eight people working in front end. The leadership was looking to expand the company and grow their product. At that time, they only used JavaScript. As much as Dart was their preferred language, the infrastructure wasn’t fully developed yet, which is where Evgeny stepped in. Together with the team, he rewrote their whole product from JavaScript to Dart.

Image of Evgeny giving a public talk about the benefits of shifting to Dart

Evgeny giving a public talk about the benefits of shifting to Dart

“Before Flutter’s success in 2015, Dart had a pretty bad reputation. There was no Dart dev community, and those rare enthusiasts who did use Dart did not share their knowledge in any way.”

Dart was launched in 2011 and went into stable release in 2013. But then the ecosystem wasn’t ready for a lot of attention, a lot of things still needed to be finalized. That’s why, in his view, many developers got discouraged by their first encounters with this technology.

“Nevertheless, it did attract a few guys, including me. We decided to create a channel for Dart-related discussions and with time, we invited more and more people to join, creating an actual community. There are now over 6,000 of us in this chat room!”

Despite a complicated history, Dart has taken its place in the tech world. Back then, it was a great choice for Web development and now it has shifted into the truly all-in-one “swiss army knife” language. Evgeny’s company, Wrike, relies on Web technology, with the main service being a high-load SAAS solution. Therefore performance, code size and ease of development were the main criteria for choosing a development language.

“Dart compiled to Javascript was the best choice. Nowadays, the Web world is highly diverse, so choosing the right technology is not a simple task!”

Based on strong connections with local web communities, they decided to build a community around Dart language (and Flutter in the future). They became Dart Up – a large international IT community. It’s not a surprise at all that Dart has been attracting so many developers over the past years. Without it, Wrike would truly not have been as successful as it currently is.

DART UP!

Dart Up started as a meetup.

“There were about 30 of us at the beginning, we would meet in my office and share ideas, discuss, brainstorm.”

Evgeny and a couple of other Dart enthusiasts wanted to create a space for a knowledge exchange, bringing together people who used the same language and putting them together into a social setting. The event got so popular that soon after they had to move it to a larger venue.

“We raised some money, rented a hall, and set up a projector. That’s how the first DartUP came about. We even brewed our own Dart beer!”

Image of home-brewed beer by Wrike and Dart

Special perk: home-brewed beer by Wrike & Dart

“But time passed and the community grew. And then we decided: “Since the big conferences don’t really want to talk about Dart, why don’t we do something like that ourselves?”

And so they did! They started to invite more and more speakers and they had a number of interesting talks and workshops. Eventually they even hosted Michael Thomsen, the manager of Dart from Google at one of their sessions! The meetup has currently over 700 regulars, including a number of international developers.

Becoming a GDE

With his achievements, engagements and a true evangelistic approach to Dart, his GDE badge was only a matter of time. It accelerated after he got invited to speak at an international Google Dart conference in Los Angeles, California. After the conference, a friend of his referred him to the program and he decided to apply. He admits that being a GDE is a big responsibility and being a community leader can be stressful at times. However, being on the program has also allowed him to share his ideas, get exposed to new opportunities and connect with a network of incredible developers.

Turns out that “spreading the word” is not only helpful for community development, but it’s fun too! So many new people! Without noticing it, I went to most of the major conferences in Russia, and I even gave some talks in English, which I thought I could never ever do.”

FINAL ADVISE FROM EVGENY TO FELLOW DEVELOPERS

“The journey begins with one step. Don’t over-focus on the end goal. “

Evgeny during the AmsterdamJS conference - his first non-Russian appearance

Evgeny during the AmsterdamJS conference – his first non-Russian appearance

Evgeny at a conference

Click here for more information on Web, Flutter and Dart.

For more information on Google Developer Experts, visit our website.

Watch more on Evgeny and his story here!