Yearly Archives: 2024

AWS Weekly Roundup—Amazon Route53, Amazon EventBridge, Amazon SageMaker, and more – January 15, 2024

Post Syndicated from Marcia Villalba original https://aws.amazon.com/blogs/aws/aws-weekly-roundup-amazon-route53-amazon-eventbridge-amazon-sagemaker-and-more-january-15-2024/

We are in January, the start of a new year, and I imagine many of you have made a new year resolution to learn something new. If you want to learn something new and get a free Amazon Web Services (AWS) Learning Badge, check out the new Events and Workflows Learning Path. This learning path will teach you everything you need to know about AWS Step Functions, Amazon EventBridge, event-driven architectures, and serverless, and when you finish the learning path, you can take an assessment. If you pass the assessment, you get an AWS Learning Badge, credited by Credly, that you can share in your résumé and social media profiles.

Events and workflows learning path badge

Last Week’s Launches
Here are some launches that got my attention during the previous week.

Amazon Route 53 – Now you can enable Route 53 Resolver DNS Firewall to filter DNS traffic based on the query type contained in the question section of the DNS query format. In addition, Route 53 now supports geoproximity routing as an additional routing policy for DNS records. Expand and reduce the geographic area from which traffic is routed to a resource by changing the record’s bias value. This is really helpful for industries that need to deliver highly responsive digital experiences.

Amazon CloudWatch Logs – CloudWatch Logs now support creating account-level subscription filters. This capability allows you to forward all the logs groups from an account to other services like Amazon OpenSearch Service or Amazon Kinesis Data Firehose.

Amazon Elastic Container Service (Amazon ECS) – Amazon ECS now integrates with Amazon Elastic Block Store (Amazon EBS), allowing you to provision and attach EBS volumes to Amazon ECS tasks running on both AWS Fargate and Amazon Elastic Cloud Compute (Amazon EC2). Read the blog post Channy wrote where he shows this feature in action.

Amazon EventBridge – EventBridge now supports AWS AppSync as a target of EventBridge buses. This enables you to stream real-time updates from your backend applications to your front-end clients. For example, you can get notifications in your mobile application from an order you did when the order status changes on the backend.

Amazon SageMaker – SageMaker now supports M7i, C7i, and R7i instances for machine learning (ML) inference. These instances are powered by custom 4th generation Intel Xeon scalable processors and deliver up to 15 percent better price performance than their previous generations.

For a full list of AWS announcements, be sure to keep an eye on the What’s New at AWS page.

Other AWS News
Some other updates and news that you may have missed:

If you are a serverless enthusiast, this week, the AWS Compute Blog published the Serverless ICYMI (in case you missed it) quarterly recap for the last quarter of 2023. This post compiles the announcements made during the months of October, November, and December, with all the relevant content that was produced by AWS Developer Advocates during that time. In addition to that blog post, you can learn about ServerlessVideo, a new demo application that we launched at AWS re:Invent 2023.

ServerlessVideo

This week there were also a couple of really interesting blog posts that explain how to solve very common challenges that customers face. The first one is the blog post in the AWS Security Blog that explains how to customize access tokens in Amazon Cognito user pools. And the second one is from the AWS Database Blog, which explains how to effectively sort data with Amazon DynamoDB.

The Official AWS Podcast – Listen each week for updates on the latest AWS news and deep dives into exciting use cases. There are also official AWS podcasts in several languages. Check out the ones in French, German, Italian, and Spanish.

AWS open source newsletter – This is a newsletter curated by my colleague Ricardo to bring you the latest open source projects, posts, events, and more.

For our customers in Turkey, on January 1, 2024, AWS Turkey Pazarlama Teknoloji ve Danışmanlık Hizmetleri Limited Şirketi (AWS Turkey) replaced AWS EMEA SARL (AWS Europe) as the contracting party and service provider to customers in Türkiye. This enables AWS customers in Türkiye to transact in their local currency (Turkish Lira) and with a local bank. For more information on AWS Turkey, visit the FAQ page.

Upcoming AWS Events
The beginning of the year is the season of AWS re:Invent recaps, which are happening all around the globe during the next two months. You can check the recaps page to find the one closest to you.

You can browse all upcoming AWS led in-person and virtual events, as well as developer-focused events such as AWS DevDay.

That’s all for this week. Check back next Monday for another Week in Review!

— Marcia

This post is part of our Weekly Roundup series. Check back each week for a quick roundup of interesting news and announcements from AWS!

OpenSUSE Leap 16 is coming

Post Syndicated from corbet original https://lwn.net/Articles/958319/

The openSUSE project has confirmed
that there will be a successor to openSUSE Leap 15, but is not sharing
a lot of details at this point.

The transition to Leap 16 is not just a numerical step-up but
symbolizes a significant path forward in technology and user
experiences. The future of openSUSE Leap is based on the innovative
concept of SUSE’s Adaptable Linux Platform.

The Adaptable Linux Platform powers the next-generation openSUSE
Leap, Leap Micro, and SUSE solutions. It makes distributions more
adaptable and suitable for cloud-native workloads while also being
capable of handling a rapid pace of innovation.

Stawinski: How We Executed a Critical Supply Chain Attack on PyTorch

Post Syndicated from corbet original https://lwn.net/Articles/958318/

John Stawinski IV describes,
in detail, how he and a partner were able to compromise the security of the
heavily used PyTorch project.

Our exploit path resulted in the ability to upload malicious
PyTorch releases to GitHub, upload releases to AWS, potentially add
code to the main repository branch, backdoor PyTorch dependencies –
the list goes on. In short, it was bad. Quite bad.

As we’ve seen before with SolarWinds, Ledger, and others, supply
chain attacks like this are killer from an attacker’s
perspective. With this level of access, any respectable
nation-state would have several paths to a PyTorch supply chain
compromise.

[$] Rust and C filesystem APIs

Post Syndicated from corbet original https://lwn.net/Articles/958072/

As the Rust-for-Linux project
advances, the kernel is gradually
accumulating abstraction layers that enable Rust code to interface with the
existing C code. As the discussion around the set of filesystem
abstractions posted by Wedson Almeida Filho in December shows, though,
there is some tension between two approaches to the design of those
abstractions. The approach favored by most of the kernel’s C programmers
looks set to win out, but this is a discussion that is likely to return as
the use of Rust in the kernel grows.

Security updates for Monday

Post Syndicated from jake original https://lwn.net/Articles/958315/

Security updates have been issued by CentOS (bind, cups, curl, firefox, ipa, iperf3, java-1.8.0-openjdk, java-11-openjdk, kernel, libssh2, linux-firmware, open-vm-tools, openssh, postgresql, python, python3, squid, thunderbird, tigervnc, and xorg-x11-server), Fedora (chromium, python-flask-security-too, and tkimg), Gentoo (libgit2, Opera, QPDF, and zlib), Mageia (chromium-browser-stable, gnutls, openssh, packages, and vlc), Oracle (.NET 6.0, fence-agents, frr, ipa, kernel, nss, pixman, and tomcat), and SUSE (gstreamer-plugins-bad).

Седмицата (8–13 януари)

Post Syndicated from Светла Енчева original https://www.toest.bg/sedmitsata-8-13-yanuari/

Седмицата (8–13 януари)

За много години! Това е втората седмица за годината, но през първата „Тоест“ беше в заслужена почивка. Така че сега е времето да пожелаем на прекрасните си, критични и ангажирани читатели новата година да е по-добра от старата. Макар в политически план номинацията на Десислава Атанасова от ГЕРБ за конституционен съдия да пречупва в зародиш надеждата, че лелеяната правосъдна реформа, заради която ПП и ДБ „ручат жабетата“, ще има някакъв смислен ефект. Защото ако в най-висшето съдилище се назначи лице с дълъг стаж в политиката и с професионален опит, включващ основно работа като юрисконсулт в психодиспансер и в русенската болница, не може да се очаква, че на новия си пост това лице ще върши друго, освен да изпълнява политически поръчки.

Добрата новина е, че понякога съдебната ни система все пак проявява някакви признаци на живот. На първа инстанция „Лев Инс“ загуби знаковото SLAPP дело срещу Mediapool за 1 млн. лв. То е заради статията на Цветелина Соколова от 2022 г. „България пак е заплашена да бъде изключена от системата „Зелена карта“. SLAPP делата, или т.нар. дела шамари, са срещу журналисти и граждани заради това, че са осветлили една или друга нередност. Последното такова дело е на АЕЦ „Козлодуй“, която съди за 500 000 лв. медицинска сестра и майка ѝ, изисквали информация за незаконна поликлиника в атомната централа.

Затова пък ротацията на правителството ще се състои, освен ако някой черен лебед не ѝ попречи, убедена е Емилия Милчева в тазседмичния си политически анализ „Джентълмените с късмет. Ротацията продължава“. Ала черните лебеди като че ли са само за отвличане на вниманието от задкулисните договорки за нови членове на регулаторите. Налага се да преглъщаме и ДПС, което уж не е във властта, но в лицето на Пеевски се държи, сякаш е. А всичко можеше да е по-честно и приемливо за обществото, ако имаше коалиционно споразумение, както му е редът, в което да фигурира механизмът на ротацията.

Междувременно Румен Радев използва дори Нова година, за да провежда собствена политика в противоречие с тази на правителството и парламента. В статията си „Румен Радев и неговите семейства“ разсъждавам върху новогодишното изявление в защита на семейството, подписано от президентите на Унгария, България и Сърбия. Заставайки отново на страната на пропутинските диктатури и не зачитайки семейните специфики на българското население, Радев за пореден път не олицетворява единството на нацията. Но какво ли се учудваме – с лицемерната си позиция той не олицетворява дори себе си.

Александър Нуцов обръща поглед от върховете на държавата към невидимата децентрализация в България. Най-голям властови ресурс е съсредоточен в националната държава, но процеси на децентрализация текат навсякъде по света още от времето на Студената война. С падането на желязната завеса децентрализацията включва все повече и частния сектор в публичните дела. Впоследствие роля във вземането на политически решения започват да играят гражданите и техните организации. За разлика от други страни обаче, в България все още липсват стратегия и целенасочена държавна политика за децентрализация на властта.

Новата тема на Атанас Шиников в неговото „Ориент кафе“ звучи на пръв поглед чудато – „Изкуственият интелект на Аллах“. Авторът се интересува от въпроса дали изкуственият интелект може да бъде мюсюлманският андроид, който сънува шериатски пасбища за електрически правоверни овце. С други думи, може ли ислямът да се предаде с нули и единици? Затова Шиников влиза в ролята на любопитен мюсюлманин и задава въпрос на ChatGPT, постъпвайки като много други мюсюлмани, които задават въпроси в интернет дали едно или друго действие е съвместимо с шериата.

Докато още сме на тази вълна, статията на Анастасия Орманджиева отново е посветена на ролята на изкуствения интелект, но този път – в медицината. Той може да се учи и да стига до определени изводи, които са от полза на лекарите при вземане на решения. В момента изкуственият интелект намира приложение в медицинските среди основно за анализ на изображения от изследвания. Но той може да се използва и за наблюдение на жизнените показатели на пациенти, за откриване на симптоми на заболявания като рак или за намаляване на разходите при синтезирането на нови лекарства. Стандартите за употребата му в медицината тепърва се изработват, защото са налице куп етични въпроси.

Връщаме се към естествения интелект, по точно – към отказа от употребата му. Като всичко, което Анета Василева пише, статията ѝ „Каузата на кучето. Архитектурната критика днес“ не е просто за архитектура. Защото дефицит на качествена критика има в много други области. И не само в България – кризата на архитектурната критика е глобална. Причините са много: променена медийна среда, комерсиални пресгрупи, финансови проблеми, опасения за професионалното бъдеще на ресорните автори, привикването към бързата информация в интернет… Безкритичността обаче води до упадък в самата архитектура. Като се замислим, всъщност всяка безкритичност води до упадък.

Знаете си, че няма да ви оставя без лични препоръки. На 18 януари на основната сцена на театър „Сфумато“ ще се състои представянето на едно ново издателство – „Кота 0“. Зад издателството стоят петима автори: Иван Димитров, Светослав Тодоров, Стефан Иванов, Стефан Икога и Захари Захариев. Те ще разкажат повече за идеята на начинанието си, ще прочетат свои неща, а модератор ще бъде не кой да е, а Николай Колев.

На 18 юни пък вокалистът на Radiohead Том Йорк ще пее в София със супергрупата The Smile. Направо не е за вярване, но е истина. Може отсега да започнете да подгрявате с The Smile. Аз обаче не мога да се въздържа да не ви поздравя с едно рейдиохедско парче. По-точно, с онзи на пръв поглед безумен, но всъщност гениален танц на Том Йорк от клипа на Lotus Flower, който съм гледала може би стотици пъти:

Приятно четене, слушане и гледане!

How to Migrate Your SMS Program to Amazon Pinpoint

Post Syndicated from Tyler Holmes original https://aws.amazon.com/blogs/messaging-and-targeting/how-to-migrate-your-sms-program-to-amazon-pinpoint/

How to Migrate Your SMS Program to Amazon Pinpoint

In the fast-paced realm of communication, where every second counts and attention spans are shorter than ever, the choice of channels that you use to deliver your message to your recipients is critical. While we often find ourselves swept away by the allure of flashy social media platforms and sleek email interfaces, it’s the unassuming text message, or SMS, that continually proves to be one of the most effective options. According to Statista, there over 5 billion mobile internet users globally, amounting to over 60% of the earth’s population of ~8 billion. SMS obviously provides an expansive reach that can help businesses connect with a diverse audience but in order to do that at scale, you need to use a service like Amazon Pinpoint that facilitates the ability to send SMS to over 240 countries and/or regions around the world. If you have a current SMS provider and are considering Pinpoint SMS for its global reach, scalability, cost effective pricing, and demonstrably high deliverability, this guide will walk you through how to migrate from your current provider.

There are several common reasons our customers give us when considering a migration. Don’t worry if your situation doesn’t fit into a neat box, we help customers navigate the dynamic landscape of SMS that is constantly evolving. Let’s dive deep into each of the below to highlight some common things we hear from our customers.

  • My current provider doesn’t deliver to countries I want to send to
  • My current provider is more expensive than Pinpoint pricing
    • Our pricing is available on the public pricing page here. Each country has it’s own cost associated with it so enter in the countries you would like to see pricing for. These prices are per message sent so if you are planning on sending to multiple countries factor in the types of messages that you will want to send as well as the countries. If your use case includes 2 way communication make sure to factor the number of inbound messages you expect into your calculations.
      • NOTE: Depending on the language the available characters per message varies, which can affect your calculations on cost. See here for an explanation
  • My current provider doesn’t have features that Pinpoint has
    • Among many other features Pinpoint has the ability to send over multiple channels, including: SMS, Email, Push/In-App, Voice, Over the Top (OTT) services such as WhatsApp, as well as interact with third-party APIs giving you the flexibility to send to many other channels.
  • My current provider is not native to AWS
    • Pinpoint, being native to the AWS Cloud, boasts the capability to seamlessly integrate with a wide array of services, including AI/ML offerings such as Amazon Personalize, Amazon Bedrock, and Amazon SageMaker, among others. This means you can leverage various AWS services to create innovative solutions that enhance and optimize the communications sent through Pinpoint.
  • My current provider does not have good deliverability
    • Price is not the only factor to consider when looking at SMS providers. If you find another provider with lower pricing make sure to ask about their deliverability to the countries you are wanting to send to. There is a big difference between sending an SMS at a low price, and actually delivering that SMS. We are happy to discuss deliverability with you, just reach out to your Account Manager if you have one or contact us to start a conversation about your migration.
  • I’m not happy with the customer support of my current provider
    • The SMS landscape is constantly changing and our SMS experts are here to help guide you through the process. Whether it’s regulatory changes, pricing changes, or creating complex architectures to support your needs. Reach out to your Account Manager if you have one or contact us to start a conversation about your migration and get your questions answered.

Regardless of your reason for considering migrating there are four scenarios that most of our customers find themselves in when beginning to plan for an SMS migration.

I have not sent SMS before but I would like to start sending through Pinpoint
Skip ahead to the section on “Checklist for Planning an SMS Migration” to start planning for sending SMS

I have number(s) (Also known as Originators, Origination Identities (OIDs), Toll-Free, 10DLC, Long Code, Short Code, and/or SenderID) with a different provider and I would like to move those to Pinpoint
The ability to “port” numbers from other providers is dependent on the type of originator, the vendor you procured them from, and the country that they support. You may need to get new originators so factor that into your timeline and reach out to your Account Manager to determine whether your originators are able to be ported over. Once you have done that, pull the reports for how much volume you are sending to each country with your current provider and then skip ahead to the section on “Checklist for Planning an SMS Migration” to start planning for sending SMS

I have a current provider but I would like to procure new numbers from Pinpoint
Pull the reports for how much volume you are sending to each country with your current provider and then skip ahead to the section on “Checklist for Planning an SMS Migration” to start planning for sending SMS

I have a current provider but would like to split traffic between them and Pinpoint
Pull the reports for how much volume you are sending to the countries you plan on migrating to AWS and then skip ahead to the section on “Checklist for Planning an SMS Migration” to start planning for sending SMS. Make sure that you consider how you will be managing opt-outs across two providers. Pinpoint offers centrally managed opt-outs but self-management is also an option. All Delivery Receipts/Reporting (DLRs) and inbound/outbound events can be streamed through Amazon Kinesis, Amazon CloudWatch, and/or Amazon Simple Notification Service (SNS) if you need to send those events to another location inside or outside of the AWS Cloud.

Checklist for Planning an SMS Migration

  • Setup a spreadsheet similar to the one outlined in this post
  • Identify your use case(s)
    • Note whether your use case is one-way or two-way
      • NOTE: Not all countries support 2-way communications, which is the ability to have the recipient send a message back to the OID.
      • NOTE: Sender ID also does not support 2-way communication so if you are planning on using Sender ID you will need to account for how to opt recipients out of future communications.
  • Identify your countries
  • Identify your volume per country
    • If you are already sending SMS with another provider pull a report over a representative time period.
  • Identify your throughput needs (Also referred to as Messages per Second, MPS, Transactions per Second, or TPS) for each country
    • Most origination identities are chosen for their ability to support a certain level of MPS, not volume, so if you have seasonality make sure to account for burst rates. There are quotas for the APIs that govern sending as well as quotas for the different types of originators.
  • Identify which origination identities you will need for each country using this guide
    • Make note of any countries/OIDs that require registration
    • Reach out to your Account Manager if you have one or contact us to start a conversation about your migration.
    • If you have OIDs you would like to migrate make sure you determine whether that is possible ASAP since your timelines could be affected by the outcome.

Make sure you give ample time for your migration. There are many entities involved in delivering SMS, from governments, to mobile carriers, to third-party registrars, and more, which means that timelines are not always within your control. Ask questions, take advantage of the expert resources we have at AWS, and the content we have produced around these topics.

Content to read

  • Review the countries and regions we support here
  • Use the format for aggregating information on your use cases outlined in this post here
  • Decide what origination IDs you will need here
  • Review the documentation for the V2 SMS and Voice API here
  • Review the Pinpoint API and SendMessage here
  • Check out the support tiers comparison here