🍔

🇺🇸 AWS re:Invent 2022 Report🇺🇸

2022/12/20に公開約13,700字

This article is of Mapbox Japan Advent Calendar 2022 and translated from 🇺🇸 AWS re:Invent 2022 体験記 🇺🇸
I'm an infrastructure and data engineer working for Mapbox ads platform. I usually build infrastructure on AWS with CDK and create data APIs on EKS.

Summary

I attended AWS re:Invent 2022 held in Las Vegas on 11/29/2022~12/2/2022. It was 4 nights and 6 days trip. I'd like to report an the event!

In a separate article, I summarized the Mapboxer's presentations at re:Invent (in Japanese). Please take a look it.
https://zenn.dev/yukinakanaka/articles/f3719f2749d348

Before Departure

Date Action
2022/05/02 Tell Boss I'd like to attend re:Invent
2022/06/02 Registration opens (recieved email from AWS)
2022/08 Boss got a budget. Thank you so much!🙇
2022/09/22 I registered for re:Invent
2022/09/30 Book hotel through AWS website 🏢 Book flight by myself 🛩
2022/10/12 Reservations for sessions and workshops begin (received an email from AWS)
2022/10/14 Reserve a session or workshop. Popular workshops are already fully booked and cannot be reserved 😭
2022/10/14 Registerd my photo and other information on the re:Invent website.
2022/11 Finish my tasks before going to re:Invent
2022/11/28 Departure from Haneda Airport🛩🇯🇵

On the way to re:Invent

Flight

11/28(Mon) 13:00(JST) Departure→11/28(Mon) 12:00(PST) Arrival.
I traveled so as to arrive on the day the event started. It took about 16 hours total from Haneda Airport (Haneda→LA=10 hours, waiting=5 hours, LA→LAS=1 hour) to arrive in Las Vegas. However, since there is a 17-hour time gap, the time was set back one hour.

From the plane I could see the desert and rugged mountains, I was impressed that Las Vegas is really in the desert.

Badge pickup

I picked up my badge at the airport. I used the QR code issued by AWS to get my badge. Note that you can also pick up your Badge at the conference venue.

Airport to Hotel

I was going to take a bus, but I couldn't figure out how to get in. I ended up taking an Uber 🚕.

Re:Invent

The conference ran from 8:00 am until about 6:00 pm. I had to get up early every day and was preoccupied with the conference all through the evening.

Conference venue


The first thing that surprised me when I attended re:Invent was the size of the venue.

The Venetian & The Palazzo Wynn Mandalay Bay

All of the hotels looked gorgeous, and I thought it was indeed Las Vegas!
The buses provided by AWS were used for transportation between hotels. It took about 40 minutes to go from the northernmost hotel to the southernest hotel. (The distance is not so long, but it got slower due to traffic jams.)

Keynote & Session

Every day I attended one or two keynote or session, some lasting one hour, some lasting two and a half hours. Here is a brief introduction of the most interesting topic for me.

Zero-ETL (Keynote)

In Keynote, AWS CEO Adam Selipsky announced that AWS is investing in 'Zero-ETL futre', where Pipelines do not have to be created manually. This was Good News for me, because I has been struggling with ETL architecture lately.



As a specific Zero-ETL feature, Amazon Aurora zero-ETL integration with Amazon Redshift has been announced. This feature allows Aurora data to be replicated to Redshift without a pipeline.

Enabling operational analytics with Amazon Aurora and Amazon Redshift (Session)

Two days after the presentation, another session was held to explain this feature in detail. By the way, this session was a new Session released after the announcement. You can check the AWS application to see if a new Session has been released.

Integration is done in the Storage Layer, where CDC Streaming reflects changes from Aurora's Storage to Redshift's Storatge. In fact now, it is possible to query Aurora from Redshift using Federated Query, but each time a query is made, a query is executed in Aurora. With this new feature, Aurora's data will be replicated to Redshift, so that queries will not be made to Aurora. I expect that performances of views using Aurora's data will be improved considerably.

This feature is still in the Preview phase. Only Amazon Aurora MySQL 3 is supported, and only us-east-1 region is supported. For more details, please refer to the AWS documentation
(AWS Releases Zero-ETL Integration of Amazon Aurora and Amazon Redshift).

Workshop

At re:Invent, there were Workshops where you can learn something in practical way. I personally believe, it is important to attend as many workshops as possible at re:Invent. (Keynote and Sessions are not so important because you can look up videos and blogs after the event.)
As I mentioned at the beginning, reservations for the Workshop filled up quickly, but it was possible to attend without a reservation if you got in line for the Walk-Up. However, the early bird gets the worm, so even if you get in line, you can't be sure of getting in. I was not able to join some workshops even though I got in line 40 minutes before😭.

Microservice Observability with Amazon OpenSearch Service Workshop

The following is a brief introduction to the Observability workshop, which was the most informative of all the workshops I attended.

In this Workshop, I learned how to improve the Observability of Microservices running on EKS. AWS Distro for OpenTelemetry, FluentBit and Data Prepper were deployed on EKS to collect data and send to AWS OpenSearch Service.

OpenSearch is a Project forked from ElasticSearch. AWS OpenSearch Service is its managed service. It provides real-time application monitoring and log analysis.

Since the version OpenSearch2.4, Prometheus data can be visualized on OpenSearch as well. I thought OpenSearch was just a tool for 'text search engine', but I realized that it was a tool for a 'observerbility' as well, and its development speed is so fast.

I would definitely like to introduce OpenSearch in our products in 2023 to increase Observability of our applications.

Expo

At the Expo, there were booths of all kinds of Tech companies, from StatUp to Enterprise.


I was very excited to see so many logos that I knew. When I was talking to the person in charge at the booth, he said, 'You came all the way from Japan? That's amazing!','What company do you work for?' etc. I was able to have a conversation with them and it helped to distract me from my loneliness. At the same time, I realized that I need to learn to speak English better.


It was a heaven for engineers as I got free T-shirts, socks and stickers😇 The ones we got were given to our teammates as souvenirs 🙇🏻.

Meals

Breakfast and lunch were provided by the conference. Those were served in buffet style in a fairly large venue.

Personally, I liked the nachos I had at Mandalay Bay!

For dinner, I ate a log of burgers at a restaurant around the hotel🍔 Gordon Ramsay Burger's burgers were very tasty and impressive😋. Just be careful about the price. It cost me about 8,000 yen.

Also, companies attending re:Invent were having private parties. I was able to attend a party that AWS hosted for companies of West Cost of US.

Sightseeing

There was little time for sightseeing as the conference ran from early in the morning to late in the evening. If I could get away, I would have been able to go to the Grand Canyon, but I didn't have time for that at all, so I did some sightseeing in Las Vegas.

Bellagio Fountain Water Show
Bellagio Fountain Water Show.
The Bellagio fountains are about a 15 minute walk from the conference venue. You can see it for free. It was a great spectacle!

Cirque du Soleil 'The Beatles Love'
Cirque du Soleil 'The Beatles Love'
Cirque du Soleil 'The Beatles Love' is held at the hotel next to the conference venue. I bought a ticket the day before the show, which cost about 20,000 yen. It was very impressive!

On the way back to Japan

12/2(Fri) 08:30(PST) Departure→12/3(Sat) 16:30(JST) Arrival.
I had my friend's wedding party on Sunday, so I traveled to arrive in Japan on Saturday. It took about 15 hours total from Las Vegas airport (Haneda→SFC=2 hours, waiting=2 hours, SFC→Narita=11 hours) to arrive at Narita airport. However, there is a 17-hour time difference, so the clocks go forward about 1.5 days.

On the way back, I saw Mt. Fuji and the sunset. It was the most beautiful Mt. Fuji I have ever seen!

Summary

I will end with Good points and areas of improvement.

Good points

  • I was able to get a ticket to re:Invent after consulting with Boss many times.
  • I was able to attend the presentation of the latest features of Aurora and Redshift's zero-ETL and listen to the technical details.
  • I was motivated to learn more about AWS because I experienced the huge scale of AWS (many services, engineers from all over the world).
  • I was able to meet mapboxers.
  • I understood the time difference between the US and the West Coast. Before I went there, I thought the time difference was 17 hours, which was troublesome to calculate, but I realized that West Cost was 7 hours ahead of Japan but one day befind. This will be useful when I work with US members in the future.
    PST = JST + 7 hours - 1 day

Areas of improvement

  • I could not make reservations for the sessions and workshops I wanted to attend. I should make reservations as soon as they become available! I received the reservation start e-mail around 2:00 am (JST), so if you live in Japan, you would not notice it until the morning, which is a disadvantage.
  • I suffered from jet lag from start to finish. I was sleepy and had a headache during the day and could not sleep at night. If I can go to the next conference, I would like to be there a few days before the conference so that the jet lag would be lessened.
  • I was in a hurry to get from Venetian to Mandalin on the second day of the conference because I did not know where to catch the bus. I thought it was a good idea to check the bus stop the day before. Also, there were many information staffs dressed in green in the venue, so it would have been better to ask them proactively.
  • I should have done more research beforehand on transportation from the airport. In US, Uber and Lyft, sharing ride services, were the main transportation. I managed to install the app at the airport and was able to get a ride, but I should have done more research and simulation beforehand.
  • I could not expand my network of engineers. I would like to improve my English and be able to expand my network next year.

Tips

If you Google 're:Invent Tips', then you will find many videos and blogs. If you are going to re:Invent in the future, please check them out!

Thank you for reading to the end.

Discussion

ログインするとコメントできます