AWS Glue Elastic Views Preview

Fill out the form below to apply for access

If you are interested in learning more about AWS Glue Elastic Views, please provide your information below. You will need an AWS Account Number to request access. We will contact you with instructions if you are accepted.

AWS Glue Elastic Views makes it easy to combine and replicate data across multiple data stores without you having to write custom code. With AWS Glue Elastic Views, you can use familiar Structured Query Language (SQL) to quickly create a virtual table—called a view—from source data stores. Based on this view, AWS Glue Elastic Views copies data from the source data store and creates a replica—called a materialized view—in a target data store.

AWS Glue Elastic Views currently supports Amazon DynamoDB as a source data store and Amazon S3, Amazon Redshift, and Amazon OpenSearch Service (successor to Amazon Elasticsearch Service) as target data stores.

Website Referral Code:

Z-[OP]-Form Validation Bot Verification:

Last Web Form Update:

_mkto_trk

Suppress SFDC Auto-Response Email:

Z-[OP]-URL Tracking TRK Campaign:

Z-[OP]-URL Tracking SiteCatalyst Campaign:

Z-[OP]-URL Tracking SiteCatalyst Segment:

Z-[OP]-URL Tracking SiteCatalyst Channel:

Z-[OP]-URL Tracking SiteCatalyst Geo:

Z-[OP]-URL Tracking SiteCatalyst Content:

Z-[OP]-URL Tracking SiteCatalyst Medium:

Z-[OP]-URL Tracking SiteCatalyst Outcome:

Z-[OP]-URL Tracking SiteCatalyst Publisher:

Z-[OP]-URL Tracking SiteCatalyst S_FID:

Z-[OP]-Form Terms and Conditions Copy:

Z-[OP]-Email Validation Hygiene:

Z-[OP]-URL Tracking Lead ID:

Z-[OP]-DB-Annual Revenue:

Z-[OP]-DB-City:

Z-[OP]-DB-Company Size:

Z-[OP]-DB-Company:

Z-[OP]-DB-Country:

Z-[OP]-DB-Employee Range:

Z-[OP]-DB-IP Address:

Z-[OP]-DB-Industry:

Z-[OP]-DB-Internet Service Provider:

Z-[OP]-DB-Lead ID:

Z-[OP]-DB-PostalCode:

Z-[OP]-DB-StateProv:

Z-[OP]-DB-Website Domain:

Z-[OP]-Form Unique ID:

Business Email Address:

First Name:

Last Name:

Phone Number:

Company Name:

Please provide a high level description of the business problem you would like to solve with AWS Glue Elastic Views (e.g., Our application uses Amazon DynamoDB as the operational database. We want to facilitate a full text search capability on this data by copying it over to Amazon OpenSearch Service).

How are you solving this business problem today? (e.g., Do you have an existing data pipeline to move data from Amazon DynamoDB to Amazon OpenSearch Service, Amazon S3, or Amazon Redshift?)

What works well and what are some of the challenges with your current solution?

What sources do you require to use with Elastic Views? [Select up to 3]

What targets do you require to use with Elastic Views? [Select up to 3]

Does your business problem require Elastic Views to join data across multiple data stores? (e.g., Our application requires to join data from an Orders table in Amazon DynamoDB with data from a Customer table in Amazon Aurora MySQL to create a real time dashboard of orders per customer.)

Does your business problem require Elastic Views to aggregate data? (e.g., Our web application stores clickstream data in DynamoDB. Our BI application requires to aggregate the number of clicks by product per hour.)

AWS Account ID:

Country / Region:

State/Province:

Postal Code:

Industry:

Job Role:

Job Title:

Level of AWS Usage:

Use Case:

I am completing this form in connection with my: