ArgumentError: AWS EMR API Error (ValidationException): Invalid InstanceProfile: EMR_EC2_DefaultRole

I am using this zip of emr snowplow_emr_r102_afontova_gora.zip

I’m not sure what I might be doing wrong, any help would be greatly appreciated.

I did skip Use EBS-backed instances and set the HD size & Enable connection draining for your Elastic Beanstalk instance & Configure autoscaling settings because my data is so small and this is just for testing for now. If that will make a difference I will configure those tho. But the way it was worded seems like the step I am at should work.

I am getting the following error

D, [2020-01-11T01:31:17.776000 #31639] DEBUG -- : Initializing EMR jobflow
ArgumentError: AWS EMR API Error (ValidationException): Invalid InstanceProfile: EMR_EC2_DefaultRole.
                    submit at uri:classloader:/gems/elasticity-6.0.12/lib/elasticity/aws_session.rb:33
              run_job_flow at uri:classloader:/gems/elasticity-6.0.12/lib/elasticity/emr.rb:302                       run at uri:classloader:/gems/elasticity-6.0.12/lib/elasticity/job_flow.rb:173
                       run at uri:classloader:/emr-etl-runner/lib/snowplow-emr-etl-runner/emr_job.rb:621
                   send_to at uri:classloader:/gems/contracts-0.11.0/lib/contracts/method_reference.rb:43
                 call_with at uri:classloader:/gems/contracts-0.11.0/lib/contracts/call_with.rb:76
  block in redefine_method at uri:classloader:/gems/contracts-0.11.0/lib/contracts/method_handler.rb:138
                       run at uri:classloader:/emr-etl-runner/lib/snowplow-emr-etl-runner/runner.rb:109
                   send_to at uri:classloader:/gems/contracts-0.11.0/lib/contracts/method_reference.rb:43
                 call_with at uri:classloader:/gems/contracts-0.11.0/lib/contracts/call_with.rb:76
  block in redefine_method at uri:classloader:/gems/contracts-0.11.0/lib/contracts/method_handler.rb:138
                    <main> at uri:classloader:/emr-etl-runner/bin/snowplow-emr-etl-runner:41   
                      load at org/jruby/RubyKernel.java:979
                    <main> at uri:classloader:/META-INF/main.rb:1
                   require at org/jruby/RubyKernel.java:961
                    (root) at uri:classloader:/META-INF/main.rb:1
                    <main> at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1
ERROR: org.jruby.embed.EvalFailedException: (ArgumentError) AWS EMR API Error (ValidationException): Invalid InstanceProfile: EMR_EC2_DefaultRole.

This is my config.yml

aws:

  # Credentials can be hardcoded or set in environment variables

  access_key_id: 'gfdgs'

  secret_access_key: 'gfds+gfds'

  s3:

    region: 'us-east-2'

    buckets:

      assets: s3://snowplow-hosted-assets # DO NOT CHANGE unless you are hosting the jarfiles etc yourself in your own bucket

      jsonpath_assets: # If you have defined your own JSON Schemas, add the s3:// path to your own JSON Path files in your own bucket here

      log: s3://enrich-logs-riel-design

      raw:

        in:

          - s3://elasticbeanstalk-us-east-2-410131593755/resources/environments/logs/publish/e-dpcpvtxxpi

        processing: s3://enrich-processing

        archive: s3://enrich-archive    # e.g. s3://my-archive-bucket/in

      enriched:

        good: s3://enrich-good       # e.g. s3://my-out-bucket/enriched/good

        bad: s3://enrich-bad        # e.g. s3://my-out-bucket/enriched/bad

        errors: s3://enrich-errors     # Leave blank unless continue_on_unexpected_error: set to true below

        archive: s3://enrich-archive-enriched    # Where to archive enriched events to, e.g. s3://my-archive-bucket/enriched

      shredded:

        good: s3://enrich-shredded/good       # e.g. s3://my-out-bucket/shredded/good

        bad: s3://enrich-shredded/bad        # e.g. s3://my-out-bucket/shredded/bad

        errors: s3://enrich-shredded/errors     # Leave blank unless continue_on_unexpected_error: set to true below

        archive: s3://enrich-shredded/archive   # Where to archive shredded events to, e.g. s3://my-archive-bucket/shredded

  emr:

    ami_version: 5.9.0      # Don't change this

    region: 'us-east-2'      # Always set this

    jobflow_role: EMR_EC2_DefaultRole # Created using $ aws emr create-default-roles

    service_role: EMR_DefaultRole     # Created using $ aws emr create-default-roles

    placement:      # Set this if not running in VPC. Leave blank otherwise

    ec2_subnet_id: subnet-a92da0e5 # Set this if running in VPC. Leave blank otherwise

    ec2_key_name: snowplow-ec2

    bootstrap: []           # Set this to specify custom boostrap actions. Leave empty otherwise

    software:

      hbase:                # Optional. To launch on cluster, provide version, "0.92.0", keep quotes. Leave empty otherwise.

      lingual:              # Optional. To launch on cluster, provide version, "1.1", keep quotes. Leave empty otherwise.

    # Adjust your Spark cluster below

    jobflow:

      job_name: 'Snowplow'

      master_instance_type: m1.medium

      core_instance_count: 2

      core_instance_type: m1.medium

      core_instance_ebs:    # Optional. Attach an EBS volume to each core instance.

        volume_size: 100    # Gigabytes

        volume_type: "gp2"

        volume_iops: 400    # Optional. Will only be used if volume_type is "io1"

        ebs_optimized: false # Optional. Will default to true

      task_instance_count: 0 # Increase to use spot instances

      task_instance_type: m1.medium

      task_instance_bid: 0.015 # In USD. Adjust bid, or leave blank for non-spot-priced (i.e. on-demand) task instances

    bootstrap_failure_tries: 3 # Number of times to attempt the job in the event of bootstrap failures

    configuration:

      yarn-site:

        yarn.resourcemanager.am.max-attempts: "1"

      spark:

        maximizeResourceAllocation: "true"

    additional_info:        # Optional JSON string for selecting additional features

collectors:

  format: 'clj-tomcat' # Or 'clj-tomcat' for the Clojure Collector, or 'thrift' for Thrift records, or 'tsv/com.amazon.aws.cloudfront/wd_access_log' for Cloudfront access logs

enrich:

  versions:

    spark_enrich: 1.18.0 # Version of the Spark Enrichment process

  continue_on_unexpected_error: false # Set to 'true' (and set out_errors: above) if you don't want any exceptions thrown from ETL

  output_compression: NONE # Compression only supported with Redshift, set to NONE if you have Postgres targets. Allowed formats: NONE, GZIP

storage:

  versions:

    rdb_shredder: 0.13.0        # Version of the Relational Database Shredding process

    rdb_loader: 0.14.0          # Version of the Relational Database Loader app

    hadoop_elasticsearch: 0.1.0 # Version of the Hadoop to Elasticsearch copying process

monitoring:

  tags: {} # Name-value pairs describing this job

  logging:

    level: DEBUG # You can optionally switch to INFO for production

  snowplow:

    method: get

    app_id: e-dpcpvtxxpi # e.g. snowplow

    collector: riel-design-email-open.us-east-2.elasticbeanstalk.com # e.g. d3rkrsqld9gmqf.cloudfront.net

https://aws.amazon.com/premiumsupport/knowledge-center/emr-default-role-invalid/

Im confused, I had followed these instructions to setup the EC2 Instance https://github.com/snowplow/snowplow/wiki/Setting-up-EC2-instance-for-EmrEtlRunner-and-StorageLoader
Now that link you posted has me delete the default role I setup, but the next steps are about setting up a cluster in aws console, do I need to do this, or do I just need to run through the steps again and delete my EC2 Instance all together?