Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

InvalidSignatureException: Credential should be scoped to correct service: 'application-autoscaling'. #163

Closed
ConradKurth opened this issue Apr 9, 2018 · 2 comments
Labels
bug This issue is a bug. duplicate This issue is a duplicate.

Comments

@ConradKurth
Copy link

ConradKurth commented Apr 9, 2018

Please fill out the sections below to help us address your issue.

2.0.0-preview.3

Version of Go (go version)?

go version go1.10 darwin/amd64

What issue did you see?

InvalidSignatureException: Credential should be scoped to correct service: 'application-autoscaling'.

Steps to reproduce

If you have have an runnable example, please include it.

	cfg, err := external.LoadDefaultAWSConfig()
	if err != nil {
		panic(err)
	}
	cfg.Region = endpoints.UsWest2RegionID

	scale := applicationautoscaling.New(cfg)
	req := scale.RegisterScalableTargetRequest(&applicationautoscaling.RegisterScalableTargetInput{
		MaxCapacity:       aws.Int64(200),
		MinCapacity:       aws.Int64(90),
		ResourceId:        aws.String("service/foo/bar"),
		ScalableDimension: applicationautoscaling.ScalableDimensionEcsServiceDesiredCount,
		ServiceNamespace:  applicationautoscaling.ServiceNamespaceEcs,
	})
	_, err = req.Send()
	if err != nil {
		panic(err)
	}
@jasdel
Copy link
Contributor

jasdel commented May 25, 2018

I think this issue is related to v1 SDK's aws/aws-sdk-go#1009 and aws/aws-sdk-go#1850. And issue with this was fixed a while ago for application-autoscaling and I would of expected this to of been included in the V2 SDK. We'll take a look at this issue to see if implementing #153 can resolve this issue.

@jasdel jasdel added duplicate This issue is a duplicate. bug This issue is a bug. labels May 25, 2018
jasdel added a commit to jasdel/aws-sdk-go-v2 that referenced this issue May 25, 2018
Fixes how the SDK derives service signing names. If the signing name is
not modeled in the endpoints package the service will fallback to the
signing name modeled in the service model.

Fix aws#163
Fix aws#153
V2 Port of aws/aws-sdk-go#1854
jasdel added a commit that referenced this issue May 25, 2018
Fixes how the SDK derives service signing names. If the signing name is
not modeled in the endpoints package the service will fallback to the
signing name modeled in the service model.

Fix #163
Fix #153
V2 Port of aws/aws-sdk-go#1854
@jasdel
Copy link
Contributor

jasdel commented May 25, 2018

@ConradKurth thanks for reaching out to us with this issue. I've merged in #181 which corrects how the SDK resolves services signing names. it will be tagged in the SDK's next release. Let us know if you have any additional questions or feedback about the SDK.

jasdel added a commit to jasdel/aws-sdk-go-v2 that referenced this issue May 25, 2018
Services
---
* Synced the V2 SDK with latests AWS service API definitions.

SDK Bugs
---
* `private/protocol/xml/xmlutil`: Fix XML unmarshaler not correctly unmarshaling list of timestamp values ([aws#166](aws#166))
	* Fixes a bug in the XML unmarshaler that would incorrectly try to unmarshal "time.Time" parameters that did not have the struct tag type on them.
	* Related to [aws/aws-sdk-go#1894](aws/aws-sdk-go#1894)
* `service/s3`: Fix typos for migrated S3 specific config options ([aws#173](aws#173))
	* Updates the S3 specific config error messages to the correct fields.
* `aws/endpoints`: Fix SDK endpoint signing name resolution ([aws#181](aws#181))
	* Fixes how the SDK derives service signing names. If the signing name is not modeled in the endpoints package the service will fallback to the signing name modeled in the service model.
	* Fix [aws#163](aws#163)
	* Fix [aws#153](aws#153)
	* Related to [aws/aws-sdk-go#1854](aws/aws-sdk-go#1854)
* `service/s3`: remove SelectContent until EventStream supported ([aws#175](aws#175])
	* S3's SelectContent API is not functional in the SDK yet, and was not supposed to be generated until EventStream support is available.
	* Related to [aws/aws-sdk-go#1941](aws/aws-sdk-go#1941)

SDK Enhancements
---
* `service/s3/s3manager/s3manageriface`: Add WithIterator to mock interface ([aws#156](aws#156))
	* Updates the `DownloaderAPI` and `UploaderAPI` mocking interfaces to have parity with the concrete types.
	* Fixes [aws#155](aws#155)
jasdel added a commit that referenced this issue May 26, 2018
Services
---
* Synced the V2 SDK with latests AWS service API definitions.

SDK Bugs
---
* `private/protocol/xml/xmlutil`: Fix XML unmarshaler not correctly unmarshaling list of timestamp values ([#166](#166))
	* Fixes a bug in the XML unmarshaler that would incorrectly try to unmarshal "time.Time" parameters that did not have the struct tag type on them.
	* Related to [aws/aws-sdk-go#1894](aws/aws-sdk-go#1894)
* `service/s3`: Fix typos for migrated S3 specific config options ([#173](#173))
	* Updates the S3 specific config error messages to the correct fields.
* `aws/endpoints`: Fix SDK endpoint signing name resolution ([#181](#181))
	* Fixes how the SDK derives service signing names. If the signing name is not modeled in the endpoints package the service will fallback to the signing name modeled in the service model.
	* Fix [#163](#163)
	* Fix [#153](#153)
	* Related to [aws/aws-sdk-go#1854](aws/aws-sdk-go#1854)
* `service/s3`: remove SelectContent until EventStream supported ([#175](#175])
	* S3's SelectContent API is not functional in the SDK yet, and was not supposed to be generated until EventStream support is available.
	* Related to [aws/aws-sdk-go#1941](aws/aws-sdk-go#1941)

SDK Enhancements
---
* `service/s3/s3manager/s3manageriface`: Add WithIterator to mock interface ([#156](#156))
	* Updates the `DownloaderAPI` and `UploaderAPI` mocking interfaces to have parity with the concrete types.
	* Fixes [#155](#155)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. duplicate This issue is a duplicate.
Projects
None yet
Development

No branches or pull requests

2 participants