Ready to get started?

Learn more about the CData ADO.NET Provider for AWS Management or download a free trial:

Download Now

Access AWS Management Data with Entity Framework 6

This article shows how to access AWS Management data using an Entity Framework code-first approach. Entity Framework 6 is available in .NET 4.5 and above.

Entity Framework is an object-relational mapping framework that can be used to work with data as objects. While you can run the ADO.NET Entity Data Model wizard in Visual Studio to handle generating the Entity Model, this approach, the model-first approach, can put you at a disadvantage if there are changes in your data source or if you want more control over how the entities operate. In this article you will complete the code-first approach to accessing AWS Management data using the CData ADO.NET Provider.

  1. Open Visual Studio and create a new Windows Form Application. This article uses a C# project with .NET 4.5.
  2. Run the command 'Install-Package EntityFramework' in the Package Manger Console in Visual Studio to install the latest release of Entity Framework.
  3. Modify the App.config file in the project to add a reference to the AWS Management Entity Framework 6 assembly and the connection string.

    To authorize AWSDataManagement requests, provide the credentials for an administrator account or for an IAM user with custom permissions:

    1. Set AccessKey to the access key Id.
    2. Set SecretKey to the secret access key.
    3. Set Region to the region where your AWSDataManagement data is hosted.

    Note: Though you can connect as the AWS account administrator, it is recommended to use IAM user credentials to access AWS services.

    <configuration> ... <connectionStrings> <add name="AWSDataManagementContext" connectionString="Offline=False;AccessKey=myAccessKey;Account=myAccountName;Region=us-east-1;" providerName="System.Data.CData.AWSDataManagement" /> </connectionStrings> <entityFramework> <providers> ... <provider invariantName="System.Data.CData.AWSDataManagement" type="System.Data.CData.AWSDataManagement.AWSDataManagementProviderServices, System.Data.CData.AWSDataManagement.Entities.EF6" /> </providers> <entityFramework> </configuration> </code>
  4. Add a reference to System.Data.CData.AWSDataManagement.Entities.EF6.dll, located in the lib -> 4.0 subfolder in the installation directory.
  5. Build the project at this point to ensure everything is working correctly. Once that's done, you can start coding using Entity Framework.
  6. Add a new .cs file to the project and add a class to it. This will be your database context, and it will extend the DbContext class. In the example, this class is named AWSDataManagementContext. The following code example overrides the OnModelCreating method to make the following changes:
    • Remove PluralizingTableNameConvention from the ModelBuilder Conventions.
    • Remove requests to the MigrationHistory table.
    using System.Data.Entity; using System.Data.Entity.Infrastructure; using System.Data.Entity.ModelConfiguration.Conventions; class AWSDataManagementContext : DbContext { public AWSDataManagementContext() { } protected override void OnModelCreating(DbModelBuilder modelBuilder) { // To remove the requests to the Migration History table Database.SetInitializer<AWSDataManagementContext>(null); // To remove the plural names modelBuilder.Conventions.Remove<PluralizingTableNameConvention>(); } }
  7. Create another .cs file and name it after the AWS Management entity you are retrieving, for example, NorthwingProducts. In this file, define both the Entity and the Entity Configuration, which will resemble the example below: using System.Data.Entity.ModelConfiguration; using System.ComponentModel.DataAnnotations.Schema; [System.ComponentModel.DataAnnotations.Schema.Table("NorthwingProducts")] public class NorthwingProducts { [System.ComponentModel.DataAnnotations.Key] public System.String PartitionKey { get; set; } public System.String Name { get; set; } }
  8. Now that you have created an entity, add the entity to your context class: public DbSet<NorthwingProducts> NorthwingProducts { set; get; }
  9. With the context and entity finished, you are now ready to query the data in a separate class. For example: AWSDataManagementContext context = new AWSDataManagementContext(); context.Configuration.UseDatabaseNullSemantics = true; var query = from line in context.NorthwingProducts select line;